You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Talk Idea, described briefly: ** SSL, certificates, keys and trusts are all scary as heck. A lot of people struggle to get HTTPS set up for their sites, and when it comes to using it for local development, they just give up and click the “Show me this unsafe site” button in Chrome.
But not anymore. I’m going to do a quick review of the weird words of SSL (certificates, signatures, trust stores, etc.) and talk about how you can easily secure your site for free with LetsEncrypt, and make some truly bonkers certs for local development with a little-known but super easy tool called mkcert. Say goodbye to the “Not Secure” URL Badge of Shame. You will never see it again.
However, I feel like it’s much easier to demystify this stuff if the audience has a background in very very basic cryptography. I’d love to present this in collaboration with someone else, who could write a talk about the basics of how private and public keys work, and how in the end all this stuff is just numbers being multiplied or factored into other numbers. Once the audience has a basic understanding of how something like a “public key” could even work, it’ll be much easier to swallow things like “self-signed certificates”.
**Your name: ** Chris Uehlinger
**CCJS Slack username: ** Uehreka
If you're not a member of CCJS slack, sign up here so we can communicate about your talk, if you don't mind:http://charmcityjs.herokuapp.com/
**Twitter username (optional): **
**Estimated Talk Length: (1-15 min please): ** 15 minutes
Availability: Please check off the dates in which you would be interested in presenting your talk:
**Talk Title: ** SSL: How to do the thing.
**Talk Idea, described briefly: ** SSL, certificates, keys and trusts are all scary as heck. A lot of people struggle to get HTTPS set up for their sites, and when it comes to using it for local development, they just give up and click the “Show me this unsafe site” button in Chrome.
But not anymore. I’m going to do a quick review of the weird words of SSL (certificates, signatures, trust stores, etc.) and talk about how you can easily secure your site for free with LetsEncrypt, and make some truly bonkers certs for local development with a little-known but super easy tool called mkcert. Say goodbye to the “Not Secure” URL Badge of Shame. You will never see it again.
However, I feel like it’s much easier to demystify this stuff if the audience has a background in very very basic cryptography. I’d love to present this in collaboration with someone else, who could write a talk about the basics of how private and public keys work, and how in the end all this stuff is just numbers being multiplied or factored into other numbers. Once the audience has a basic understanding of how something like a “public key” could even work, it’ll be much easier to swallow things like “self-signed certificates”.
**Your name: ** Chris Uehlinger
**CCJS Slack username: ** Uehreka
If you're not a member of CCJS slack, sign up here so we can communicate about your talk, if you don't mind: http://charmcityjs.herokuapp.com/
**Twitter username (optional): **
**Estimated Talk Length: (1-15 min please): ** 15 minutes
Availability:
Please check off the dates in which you would be interested in presenting your talk: