[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2019-03-05 Thread Mathew Hodson
*** This bug is a duplicate of bug 1640978 *** https://bugs.launchpad.net/bugs/1640978 ** This bug has been marked a duplicate of bug 1640978 [SRU] Backport letsencrypt from bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2019-01-29 Thread Marc Deslauriers
The python-letsencrypt binary package is being replaced by the new python-certbot SRU that is currently in xenial-proposed and is being tracked in bug #1640978. There is no actionable item to do in this bug, and it can be closed once the python-certbot SRU has completed. -- You received this

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2019-01-29 Thread Yo
It looks like it may not be fixed in time. There is a workaround that has worked nicely for me. The announcement for Let's Encrypt mentions this: https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811 They suggest "If you use the certbot or

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2019-01-26 Thread AlpineCarver
My domains are part of the 30,000 whose renewals will begin failing on March 13th, 2019. Can this be fixed before then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745126 Title: Let's Encrypt

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2018-11-03 Thread Mathew Hodson
** Tags removed: letsencrypt ssl tls-sni ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745126 Title: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2018-10-22 Thread Brad Warren
I work at EFF and am an upstream developer of Certbot. This issue has jumped in priority now that TLS-SNI support will be dropped on February 13th, 2019. See https://community.letsencrypt.org/t/february-13-2019-end-of-life-for- all-tls-sni-01-validation-support/74209. While the TLS-SNI challenge

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2018-03-08 Thread Ame Nomade
So, yes the package is broken right now, as its first purpose is to obtain a certificate. And as explained here: https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811 "Renewals will continue to work with TLS-SNI", and yes it's still working.

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2018-03-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-letsencrypt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745126

[Bug 1745126] Re: Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE

2018-01-24 Thread Roope Lehmuslehto
** Summary changed: - Let's Encrypt has permanently disabled TLS-SNI challenge. + Let's Encrypt has permanently disabled TLS-SNI challenge. Package not compatible any more with LE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.