Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Fast-Nop already use lets encrypt on my self-hosted sites and services, using a paid one on my main website just because 1. it's already setup, and 2. it's a yearly reminder to look at my site to update it and/or improve it
-
@Fast-Nop I personally don't like let's encrypt for everything.
It's great for startups and some low profile sites.
I would never use it on a corporate site or app though.
There's a certain level of comfortability internal secops gets from buying the certs from a known and established vendor.
I also prefer to get my certs from ACM since 90% of my public infra is in Amazon. -
@sariel It's also great for most other public sites. The only exception is if you want EV/OV, then LE is not suited, but everything else is FUD.
I'm pretty sure Shakespeare didn't say that.
Me: Let's grab something for dinner!
GF: Sure, but let's go somewhere safe
Me:
EVERYTIME!!
A year ago it took me hours to get SSL working on my Digital Ocean droplet I was using to host my website. I had no idea what I was doing and even though I 'knew' how to use the terminal and do most things, I wasn't confident or competent to only rely on the CLI.
About a year later (today) I get an email that my SSL is about to expire and needs renewed. Done and taken care of within 20 minutes, (with a 2 hour gap due to waiting for the cert authority to send me the zip of files)
All that time using i3 and moving to Linux is paying off. Maybe by the time I can afford to build my next desktop I can make my main OS linux
random
i'm getting better
terminal
ssl