I'm a full stack engineer with 3+ years of experience founding a startup. I'm looking for similar (full-stack) roles, as well as either frontend or backend development. I am a US citizen.
I second Enpass. I'm surprised at how little press it gets given its user friendless, platform support, pricing, and multitude of supported sync platforms.
I've seen this happen to multiple sites and was wondering if there was a reason why some CAs don't let you issue a new cert until the day of the expiry. It doesn't seem like that would open up much of an attack surface.
Which CAs do that? I get alerts from our monitoring system 30d prior to expiration and have not had any problems generating new certs then (and they expire on the same day as the previous -- i.e., I don't "lose" three weeks if I renew three weeks early).
I'm using StartSSL for a personal site and it didn't let me generate a new one until it had almost expired. I'm using the free verification though, it might be different now or for their paid versions.
I've never heard of a CA doing that. By and large, the reason why this happens is human error - no one knows the cert is about to expire because it's not being monitored and/or the email from the CA (if they even send one) goes to a mailbox that's not being read.
But there's no reason why a rote task like renewing a certificate should be left to humans. It should be automated, which is what my startup, https://sslmate.com/, is doing.
If your CA doesn't let you renew your cert well in advance of expiry (which I find hard to believe), get a new cert on a different CA. You can have multiple certs valid for the same domain name, from different providers; the active cert is the one you serve.
Can we stop arguing? How about somebody sneaks a 3D scanner in (somehow) and shares the design for people to print themselves. Or just takes a picture. I think we get the point though.
I live on a farm in Texas. We pay $100/mo for 5mbps internet and rarely get one. (Our landline is bundled with it) Our whole internet has gone down for days multiple times.
Remote: Open to it, either yes or no.
Willing to relocate: Yes
Technologies: Node.JS, TypeScript, Java, Git, GCP, React, Svelte, Linux, SQL, NoSQL, Express, Socket.io, Docker, CI, Webpack, Gulp
Résumé: https://files.mauldin.me/2019/October/CV%20-%20Sam%20Mauldin...
Email: sam@mauldin.me
I'm a full stack engineer with 3+ years of experience founding a startup. I'm looking for similar (full-stack) roles, as well as either frontend or backend development. I am a US citizen.