by chton on 4/9/15, 9:37 AM with 67 comments
by thejosh on 4/9/15, 10:03 AM
by jng on 4/9/15, 10:00 AM
I updated some SSL certificates last week (which even required contortions such as moving to a new issuer since some legacy software requires old-style SHA-1 signed ones which our current one doesn't provide), and it didn't take more than one (long) day of work.
by billpg on 4/9/15, 10:02 AM
by ntoshev on 4/9/15, 12:34 PM
by seqizz on 4/9/15, 9:40 AM
by agarcia-deniz on 4/9/15, 10:12 AM
Enjoy the simplicity
by Karunamon on 4/9/15, 1:43 PM
If I understand right, getting a replacement cert doesn't result in a change of the private key anyways.
It's just magically, on the expiration date, your cert is somehow insecure and we must treat it as if YOU ARE IN DANGER!! - even though it's still better than then plain HTTP that everyone uses every single goddamned day. Hell, a self signed cert is better than plain HTTP, yet for some backwards-ass reason we treat it as worse, despite the fact it makes you immune from passive eavesdropping and any injection attacks, which the average person is a lot more likely to run into than a self-signed cert being used by an attacker to MITM you.
CA's are a scam and a racket. I can't wait for Mozilla's Let's Encrypt[1] to come along and put them all out of business, hopefully before the last decade or so of training users to ignore the wolf-crying cert warnings comes to fruition.
Yeah, this is irresponsible on Manjaro's part, they know the rules of the game, but the game is broken!
by abofh on 4/9/15, 12:56 PM
by bitJericho on 4/9/15, 9:54 AM
by lauriswtf on 4/9/15, 10:00 AM
by HendrikR on 4/9/15, 11:21 AM
by andygambles on 4/9/15, 10:55 AM