#Wireshark 4.6.10 has been released. Cheers! These releases are brought to you by the Wireshark Foundation. If you or your employer can donate, it would help us out immensely.
https://www.wireshark.org/docs/relnotes/wireshark-4.6.10.html
#Wireshark 4.6.10 has been released. Cheers! These releases are brought to you by the Wireshark Foundation. If you or your employer can donate, it would help us out immensely.
https://www.wireshark.org/docs/relnotes/wireshark-4.6.10.html
Should we have a second domain for the #curl website and related services that uses another TLD and another registrar? As a backup.
"2shell" is so old. "2root" is much cooler!
#curl on OSS-Scanner
"36 of the 45 findings we consider just bugs, three of them were not even bugs while one of the findings was completely wrong"
Following #Codeberg issue, it is time to remember that, if you manage an important service, you must have two domain names, in different TLDs and different registrars, and have them pre-configured and pre-announced so you can switch rapidly.
codeberg.org is unfortunately down right now due to a yet undefined issue with our domain. It was not expired and not transferred, the domain is completely gone from our account and we did not receive any email notifications, and it is currently in the status clientHold. We are currently trying to contact our registrar to get more information right now & trying to resolve this issue, but this is probably going to take some time.
We are sorry for the inconveniences & are working on a solution.
At exactly "2034-06-16 09:06:49 UTC", there's a 10 digit prefix match for that single second, if we assume the hour follows the day: 2034061609
RE: https://mastodon.scot/@Struang/117633736859043202
I was doing some date parser debugging that output the epoch time when I suddenly realized the number's prefix looked almost like a date - which prompted to take the natural next step and figure out when the date and the epoch's first 8 digits would actually match.
35 days since the previous #curl release, we have merged 311 bugfixes authored by 64 unique individuals...
hey, I thought we agreed on "2shell" for all the RCE names and now they call this new one "java4shell" ? Outrageous. https://calif.io/java4shell/
In less than eight years; on 2034-06-16 the epoch number will start with 20340616 - matching the current date. Starting at 09:06:40 UTC, lasting 100 seconds.
For those who celebrate.
The next time that happens is 850 years later.
I bet you're all wondering: how fast does #curl download 100 files in 100 parallel transfers over FTPS on localhost on a decently modern Linux machine? About 3.67 gigabytes per second. https://curl.se/perf/#ftps-parallel-speed
We'll do the #curl rewrite once rust, zig, go, java, erlang and lean have agreed which of them is the best.🍿
The rust rewritten curl has 4832 occurrences of "unsafe" in its *.rs files with 430k lines of rust code.
I am not smart enough to understand what this is for.💁🏻♂️
I trimmed off like maybe almost a percent in the #curl URL parser performance test! 😀 (specifically in the IPv6 address + zone id parsing function)
Here’s @bagder on LLM-powered rewrites.
During the time these agents converted 185,000 lines of C code into 340,000 lines of Rust code (I counted), we merged over 300 commits in the actual curl project. We actually improved curl during these a little more than three weeks. A little over 200 bugfixes actually. 200 bugfixes that none of those rust rewrites have. We also fixed a few vulnerabilities. In another month we have done another 200 and maybe fixed a few more vulnerabilities. Will these clones keep up?
As always, bagder makes the point with data. Curl is valuable because of the maintenance effort that goes into it every day.
https://daniel.haxx.se/blog/2026/11/17/actual-curl-rewrites-in-rust/
Actual #curl rewrites in #rust (not by me)
https://daniel.haxx.se/blog/2026/11/17/actual-curl-rewrites-in-rust/
Out of the 81 vulnerabilities we have confirmed in #curl so far during 2026, 14 were the result of mistakes that most likely would have been avoided had we used a memory-safe language such as rust. That's 17.3%