Explore >> Select a destination
|
You are here 
|
vninja.net | ||
| | | | |
blog.notmyhostna.me
|
|
| | | | | For my new side project I needed to build a browser extension. I was hesitant to build one as the development experience of doing everything in the ... | |
| | | | |
emilymstark.com
|
|
| | | | | Every once in a while, I encounter some variation of the following question: how can a TLS certificate go from perfectly acceptable one day to completely insecure the next? In other words, why does the browser show a scary full-page warning for a certificate that expired one day, or even one hour, ago - the same as a certificate that is self-signed, chains to an unknown root, or presents the wrong name? The premise behind these questions is that an expired certificate (especially one that is recently expired) is not as bad as a certificate with some other type of validation error, and thus the warning UX shouldn't be as severe. | |
| | | | |
tobert.github.io
|
|
| | | | | [AI summary] The author advises non-technical family members to switch from Internet Explorer to a more secure browser due to its vulnerability to zero-day exploits and malware. | |
| | | | |
www.matuzo.at
|
|
| | | I'm a frontend developer in Graz, specialized in HTML, accessibility, and CSS layout and architecture. | ||
