johnp_
Joined 10 years ago
Karma
217
Submissions
76
Member since
Apr 19
Recent submissions
Comment · 1 year ago
Comment · 2 years ago
Looks like Mozilla is currently working on implementing `sendmmsg` and `recvmmsg` use in neqo (Mozilla's QUIC implementation) [1].
Comment · 2 years ago
Here's the code, for those interested in finding the bug: https://github.com/mozilla-mobile/firefox-ios/tree/main/Brow...
Comment · 2 years ago
It says in the article
> Seabed 2030 is a long-term mapping project attempting to fully chart the seafloor and reveal all features 100 meters or larger by 2030.
There is an area of interest, "Area 3: Indian Ocean: Ninetyeast Ridge" around 30S 87E, which specifically mentions MH370:
https://seabed2030.org/wp-content/uploads/2023/06/AtlanticIn...
Though that is quite a bit (~830 km / ~1250 km from the center of the square around 30S 87E) off to the (north)west of the most recent search proposal from mh370search.com:
https://www.mh370search.com/2024/03/16/mh370-a-new-hope/
edit: Got the distance wrong. Corrected.
Comment · 2 years ago
Oh, indeed, that's quite surprising. A TLSv1.3 Client Hello always contains the supported_versions extension, which should allow wireshark to label it correctly, regardless of whether or not the handshake actually finishes. Though, tbf, it does say TLSv1 and not TLSv1.0. I wonder how it would look had TLSv1.3 been named TLSv2.0 after all...
edit: Ah, that GitLab link lead me to https://gitlab.com/wireshark/wireshark/-/issues/19515 which is a recent discussion around this topic and https://gitlab.com/wireshark/wireshark/-/merge_requests/1377... already dealt with it :)
Comment · 2 years ago
Certainly weird that wireshark shows TLSv1 while curl shows TLSv1.3. That shouldn't happen unless something interfered with the Client Hello. (or the wireshark version is outdated)
Comment · 3 years ago
linux-firmware does not carry any microcode update for Renoir (yet). Or what do you mean by "TFA"?
The fixed Renoir microcode should have revision >= 0x0860010b as per the kernel: https://github.com/torvalds/linux/commit/522b1d69219d8f08317...
Comment · 6 years ago
> and if
Do you mean the obvious `sudo snap set system refresh.hold="$(date --date=+100years +%Y-%m-%dT%H:%M:%S%:z)"`? (no error)
edit: Ah, that silently stops working after 60 days, nvm.
Comment · 6 years ago
That's why there's OCSP stapling and OCSP must staple. Ever seen an nginx server fail HTTPS connection exactly once after rotating the certificate? That's nginx lazily fetching the OCSP response from upstream for stapling purposes.
Comment · 6 years ago
Here's the spec:
https://html.spec.whatwg.org/multipage/input.html#attr-input...
> Authors are encouraged to specify both any MIME types and any corresponding extensions when looking for data in a specific format.
> User agents should prevent the user from selecting files that are not accepted by one (or more) of these tokens.
Comment · 6 years ago
Besides all the points other people already made, the money saved by being able to switch to deploying the Starlink constellation via SuperHeavy/Starship (very likely to be cheaper in $ per satellite-to-orbit) instead of F9 earlier makes taking risks and iterating faster even more appealing.
Comment · 6 years ago
It even seems to break inline links, like in the "split-horizon" section:
> System administrators can find relevant documentation here.
I'm pretty sure "here" should be a link, but of course that doesn't work when the marketing department uses a PNG instead of HTML.
I'm also surprised that Mozilla / the CDN don't optimize the PNG. `zopflipng` reduces the size from 285K to 153K.
And of course it's named "Final-DNS-over-HTTPS-05-1.png".
And make sure to specify what exactly you mean by that. base64url-encoding is incompatible with base64+urlencoding in ~3% of cases, which is easily missed during development, but will surely happen in production.