3 ms·

Sure they are. They're a CA, the clients are just for users' convenience. Anyone who wants to can write their own client against the LE rest API.

blakeyrat 11y ago
I disagree. When you go to the webpage linked above and hit "getting started", there's not even a hint that their system works in OSes other than Linux. Possible there is support for Windows and IIS, but their own website strongly suggests otherwise. EDIT: if they consider their client and their CA as two different products, well, right now the website conflates the two badly. And there's absolutely nothing there to suggest it supports Windows/IIS.
- wtetzner 11y ago
  > here's not even a hint that their system works in OSes other than Linux. > And there's absolutely nothing there to suggest it supports Windows/IIS. Their "system" is an API for issuing certificates. There's nothing platform specific about that. > right now the website conflates the two badly. From https://letsencrypt.org/getting-started/ https://letsencrypt.org/getting-started/: You’re welcome to use any compatible client, but we only provide instructions for using the client that we provide. Edit: This is the protocol they use: https://github.com/letsencrypt/acme-spec https://github.com/letsencrypt/acme-spec I found the link here: https://letsencrypt.org/how-it-works/ https://letsencrypt.org/how-it-works/
  - blakeyrat 11y ago
    So what part of this is going out of beta? The protocol, the CA, or the client? Now I'm just confused. But I still say: if their mission is to make it as easy as possible to install a SSL cert on any website, as long as they don't have any (apparent) support for Windows/IIS, they're a long, long, long way away from fulfilling that mission and probably shouldn't be leaving beta.
    - cbr 11y ago
      Typically beta/stable is about stability, not about features or platform support.
OldSchoolJohnny 11y ago
Could not disagree more. They are a CA with a very short expiring time frame and without the proper client software to automate that it's not practical to use at all.

blakeyrat 11y ago

I disagree. When you go to the webpage linked above and hit "getting started", there's not even a hint that their system works in OSes other than Linux. Possible there is support for Windows and IIS, but their own website strongly suggests otherwise. EDIT: if they consider their client and their CA as two different products, well, right now the website conflates the two badly. And there's absolutely nothing there to suggest it supports Windows/IIS.

wtetzner 11y ago
> here's not even a hint that their system works in OSes other than Linux. > And there's absolutely nothing there to suggest it supports Windows/IIS. Their "system" is an API for issuing certificates. There's nothing platform specific about that. > right now the website conflates the two badly. From https://letsencrypt.org/getting-started/ https://letsencrypt.org/getting-started/: You’re welcome to use any compatible client, but we only provide instructions for using the client that we provide. Edit: This is the protocol they use: https://github.com/letsencrypt/acme-spec https://github.com/letsencrypt/acme-spec I found the link here: https://letsencrypt.org/how-it-works/ https://letsencrypt.org/how-it-works/
- blakeyrat 11y ago
  So what part of this is going out of beta? The protocol, the CA, or the client? Now I'm just confused. But I still say: if their mission is to make it as easy as possible to install a SSL cert on any website, as long as they don't have any (apparent) support for Windows/IIS, they're a long, long, long way away from fulfilling that mission and probably shouldn't be leaving beta.
  - cbr 11y ago
    Typically beta/stable is about stability, not about features or platform support.

OldSchoolJohnny 11y ago

Could not disagree more. They are a CA with a very short expiring time frame and without the proper client software to automate that it's not practical to use at all.