Top all-time · #19557
netsekure rng
Personal blog · netsekure.orgprogrammingsecurityweb
netsekure rng is a personal blog at netsekure.org about programming, security and web. Since 2013, 4 different Hacker News readers have linked it 4 times. No feed was found, so read it on the site itself.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
Technical posts on TLS, certificate stores and browser settings, including a Windows and Firefox guide to disabling trusted root certificates and a piece on TLS overhead. HN commenters link them as instructions and as a source for figures.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
One of the main pieces of functionality in a browser is navigation. It is the process through which the user gets to load documents. Let us trace the …
What Hacker News says?
Instructions from parent are OSX only. Here's a post covering Windows and Firefox, which has its own certificate store: http://netsekure.org/2010/04/how-to-disable-trusted-root-cer...
Comment linking /2010/04/how-to-disable-trusted-root-certificates/
on “Symantec Issues Intermediate CA Certificate for Blue Coat Public Services”Submitted Chromium Internals – Lifetime of a navigation as a story · 1 points
HN discussionLet's do some math. First, the IOT devices reporting daily. In the absence of further context, I’m going to assume that it doesn’t matter when the devices report, so they can be configured to spread out their load. I’m also going to assume 1kb of data per device, but with an HTTPS API there’s roughly 7kb of overhead that we need to account for when calculating bandwidth. (Source: http://netsekure.org/2010/03/tls-ove…
Comment linking /2010/03/tls-overhead/
on “Ask HN: How much traffic do you serve and with which database engine?”For anyone wondering, Wikipedia has a nice table that show which browser support TLS 1.1/1.2, and which don't. https://en.wikipedia.org/wiki/Transport_Layer_Security#Web_b... Basically: - Chrome Stable support TLS 1.1, Chrome Beta/Canary support TLS 1.2 - Firefox Stable support TLS 1.0. You can enable TLS 1.1 by setting "security.tls.version.max" to "2" in about:config. Support is not considered stable, and you migh…
Comment linking /2009/10/tls-1-2-in-windiows-7/
on “The state of TLS ciphers”