3 ms·
No analytics No comment section. No JavaScript. But I use CSS intensively. No AES in TLSv1.3, just Cha-Cha (breaks older Chrome) The way it supposed to be.
by egberts1 4y ago
No analytics
No comment section.
No JavaScript. But I use CSS intensively.
No AES in TLSv1.3, just Cha-Cha (breaks older Chrome)
The way it supposed to be.
https://Egbert.net https://Egbert.net
- gcau 4y agoI'm using the latest chrome version on android, and your site does not load. (ERR_SSL_VERSION_OR_CIPHER_MISMATCH)
- egberts1 4y agoPrecisely. Your Chrome must be broken and arguably intentionally so. You will find that my web server does not offer any AES algorithm option in which for a Chrome web client to currently get twisted into a knot over. Oppositely, you will find nearly all other web clients able to handle these non-AES algorithm of TLSv1.3 server option quite well. Web clients like Aloha, Brave, curl, DuckDuckGo, Edge, Firefox (any), Firefox Focus (iOS), LibreFox, links (CLI), Lynx, OnionBrowser (iOS), Opera, Orion (iOS), Safari, SeaMonkey, TorBrowser, Vivaldi, and wget all work well without any AES algorithm in TLS v1.3. This is my website’s way of doing things that the TLS v1.3 spec allows us to do. And I play with maximum cyber security.