How Big Will the Impact of Lets Encrypt Be?
-
@jospoortvliet said:
A big benefit of Letsencrypt is the automation. The automation on a server box was already mentioned, but it goes further than that: you can create a VM or a liveCD or a docker container etc to distribute your server application and use Letsencrypt. Unlike today, you won't have to use a self-signed certificate or let the receiver of the VM add one by hand, you can generate one with Letsencrypt on the fly! That is a game changer for ISV's who want to simplify deployment for small business customers, really.
We intend to use it in our official ownCloud VM's (for home users and SMB) and it is also super interesting for our collaboration with Western Digital on creating a self hosting device based on a Raspberry Pi 2. And I'm looking forward to getting it on my server - right now, openSUSE isn't supported, I hope they take care of that soon.
I understand your concept, but how will you decide on the DNS name to register? and then how will that get "known" to the world?
You setup device XYZ and it auto registers with Let's Encrypt with XYZSerial.productdomain.com
Do you also have the device connect to a DDNS so it can be accessible? What do you do about the local DNS? Pray the hairpin routing works?
-
i had that same question - but then I realized that WesternDigital's Personal Cloud devices already do this. When you run their software it does all of this for you, only with security.
-
@Dashrender said:
i had that same question - but then I realized that WesternDigital's Personal Cloud devices already do this. When you run their software it does all of this for you, only with security.
I do now t have any of this gear, nor have I ever seen it. So I still have no idea how they make it work.
-
Aww - the software has the user setup a dynamic DNS account that they get free with purchase. The software walks them through creating the account, then setups up the DNS name for the device and tells the user what it is.
Hey user - if you want to connect to your private WD cloud from anywhere in teh world, just type xyz.somedomain.com into a browser and then login with your username and password.
once that step is completed on the device, the software could take over setting up a Let's Encrypt cert itself.
-
@Dashrender said:
Aww - the software has the user setup a dynamic DNS account that they get free with purchase. The software walks them through creating the account, then setups up the DNS name for the device and tells the user what it is.
Hey user - if you want to connect to your private WD cloud from anywhere in teh world, just type xyz.somedomain.com into a browser and then login with your username and password.
once that step is completed on the device, the software could take over setting up a Let's Encrypt cert itself.
That will work great for the let's encrypt cert and outside world access. It will not work so well inside the network unless it also works right with the router.
-
Let's Encrypt requires that you register an account email and public key before issuing a certificate.
Any reason I shouldn't use the same one I already use for SSH?
-
@anonymous said:
Let's Encrypt requires that you register an account email and public key before issuing a certificate.
Any reason I shouldn't use the same one I already use for SSH?
That's fine.
-
using letsencrypt right now on my home server, btw. Have a cron job set up to update the cert every month or so, with an easy tool: ACME. Simpler than the 'standard' tool from Lets Encrypt, if you ask me. Go check it out at https://github.com/hlandau/acme
-
@jospoortvliet said:
using letsencrypt right now on my home server, btw. Have a cron job set up to update the cert every month or so, with an easy tool: ACME. Simpler than the 'standard' tool from Lets Encrypt, if you ask me. Go check it out at https://github.com/hlandau/acme
I will do that since my servers with LE certs are going to hit the 60 day point next week and should be renewed.
I had not yet gotten around to scripting the renew.
-
@jospoortvliet said:
using letsencrypt right now on my home server, btw. Have a cron job set up to update the cert every month or so, with an easy tool: ACME. Simpler than the 'standard' tool from Lets Encrypt, if you ask me. Go check it out at https://github.com/hlandau/acme
I had a good laugh when I spotted the ".travis Try to speed up travis" Apparently I'm slowing things down, tho I do agree that speeding me up would be a good thing
