Changelog for python-certbot-dns-rfc2136-0.26.1-lp150.57.2.noarch.rpm :

* Wed Jul 25 2018 ecsosAATTopensuse.org- update to 0.26.1 - No changelog from upstream More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/58?closed=1
* Mon Jul 16 2018 ecsosAATTopensuse.org- update to 0.26.0
* Added - A new security enhancement which we\'re calling AutoHSTS has been added to Certbot\'s Apache plugin. This enhancement configures your webserver to send a HTTP Strict Transport Security header with a low max-age value that is slowly increased over time. The max-age value is not increased to a large value until you\'ve successfully managed to renew your certificate. This enhancement can be requested with the --auto-hsts flag. - New official DNS plugins have been created for Gehirn Infrastracture Service, Linode, OVH, and Sakura Cloud. These plugins can be found on our Docker Hub page at https://hub.docker.com/u/certbot and on PyPI. - The ability to reuse ACME accounts from Let\'s Encrypt\'s ACMEv1 endpoint on Let\'s Encrypt\'s ACMEv2 endpoint has been added. - Certbot and its components now support Python 3.7. - Certbot\'s install subcommand now allows you to interactively choose which certificate to install from the list of certificates managed by Certbot. - Certbot now accepts the flag --no-autorenew which causes any obtained certificates to not be automatically renewed when it approaches expiration. - Support for parsing the TLS-ALPN-01 challenge has been added back to the acme library.
* Changed - Certbot\'s default ACME server has been changed to Let\'s Encrypt\'s ACMEv2 endpoint. By default, this server will now be used for both new certificate lineages and renewals. - The Nginx plugin is no longer marked labeled as an \"Alpha\" version. - The prepare method of Certbot\'s plugins is no longer called before running \"Updater\" enhancements that are run on every invocation of certbot renew. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with functional changes were: - acme - certbot - certbot-apache - certbot-dns-gehirn - certbot-dns-linode - certbot-dns-ovh - certbot-dns-sakuracloud - certbot-nginx More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/55?closed=1- rebase certbot-fix_constants.patch
* Wed Jun 13 2018 ecsosAATTopensuse.org- update to 0.25.1
* Fixed - TLS-ALPN-01 support has been removed from our acme library. Using our current dependencies, we are unable to provide a correct implementation of this challenge so we decided to remove it from the library until we can provide proper support. - Issues causing test failures when running the tests in the acme package with pytest<3.0 has been resolved. - certbot-nginx now correctly depends on acme>=0.25.0. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with changes other than their version number were: - acme - certbot-nginx More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/56?closed=1- update to 0.25.0
* Added - Support for the ready status type was added to acme. Without this change, Certbot and acme users will begin encountering errors when using Let\'s Encrypt\'s ACMEv2 API starting on June 19th for the staging environment and July 5th for production. See https://community.letsencrypt.org/t/acmev2-order-ready-status/62866 for more information. - Certbot now accepts the flag --reuse-key which will cause the same key to be used in the certificate when the lineage is renewed rather than generating a new key. - You can now add multiple email addresses to your ACME account with Certbot by providing a comma separated list of emails to the --email flag. - Support for Let\'s Encrypt\'s upcoming TLS-ALPN-01 challenge was added to acme. For more information, see https://community.letsencrypt.org/t/tls-alpn-validation-method/63814/1. - acme now supports specifying the source address to bind to when sending outgoing connections. You still cannot specify this address using Certbot. - If you run Certbot against Let\'s Encrypt\'s ACMEv2 staging server but don\'t already have an account registered at that server URL, Certbot will automatically reuse your staging account from Let\'s Encrypt\'s ACMEv1 endpoint if it exists. - Interfaces were added to Certbot allowing plugins to be called at additional points. The GenericUpdater interface allows plugins to perform actions every time certbot renew is run, regardless of whether any certificates are due for renewal, and the RenewDeployer interface allows plugins to perform actions when a certificate is renewed. See certbot.interfaces for more information.
* Changed - When running Certbot with --dry-run and you don\'t already have a staging account, the created account does not contain an email address even if one was provided to avoid expiration emails from Let\'s Encrypt\'s staging server. - certbot-nginx does a better job of automatically detecting the location of Nginx\'s configuration files when run on BSD based systems. - acme now requires and uses pytest when running tests with setuptools with python setup.py test. - certbot config_changes no longer waits for user input before exiting.
* Fixed - Misleading log output that caused users to think that Certbot\'s standalone plugin failed to bind to a port when performing a challenge has been corrected. - An issue where certbot-nginx would fail to enable HSTS if the server block already had an add_header directive has been resolved. - certbot-nginx now does a better job detecting the server block to base the configuration for TLS-SNI challenges on. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with functional changes were: - acme - certbot - certbot-apache - certbot-nginx More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/54?closed=1
* Thu May 03 2018 ecsosAATTopensuse.org- update to 0.24.0
* Added - certbot now has an enhance subcommand which allows you to configure security enhancements like HTTP to HTTPS redirects, OCSP stapling, and HSTS - without reinstalling a certificate. - certbot-dns-rfc2136 now allows the user to specify the port to use to reach the DNS server in its credentials file. - acme now parses the wildcard field included in authorizations so it can be used by users of the library.
* Changed - certbot-dns-route53 used to wait for each DNS update to propagate before sending the next one, but now it sends all updates before waiting which speeds up issuance for multiple domains dramatically. - Certbot\'s official Docker images are now based on Alpine Linux 3.7 rather than 3.4 because 3.4 has reached its end-of-life. - We\'ve doubled the time Certbot will spend polling authorizations before timing out. - The level of the message logged when Certbot is being used with non-standard paths warning that crontabs for renewal included in Certbot packages from OS package managers may not work has been reduced. This stops the message from being written to stderr every time certbot renew runs.
* Fixed - certbot-auto now works with Python 3.6. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with changes other than their version number were: acme certbot certbot-apache certbot-dns-digitalocean (only style improvements to tests) certbot-dns-rfc2136
* Sat Apr 14 2018 ecsosAATTopensuse.org- update to 0.23.0
* Added - Support for OpenResty was added to the Nginx plugin.
* Changed - The timestamps in Certbot\'s logfiles now use the system\'s local time zone rather than UTC. - Certbot\'s DNS plugins that use Lexicon now rely on Lexicon>=2.2.1 to be able to create and delete multiple TXT records on a single domain. - certbot-dns-google\'s test suite now works without an internet connection.
* Fixed - Removed a small window that if during which an error occurred, Certbot wouldn\'t clean up performed challenges. - The parameters default and ipv6only are now removed from listen directives when creating a new server block in the Nginx plugin. - server_name directives enclosed in quotation marks in Nginx are now properly supported. - Resolved an issue preventing the Apache plugin from starting Apache when it\'s not currently running on RHEL and Gentoo based systems. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with changes other than their version number were: certbot certbot-apache certbot-dns-cloudxns certbot-dns-dnsimple certbot-dns-dnsmadeeasy certbot-dns-google certbot-dns-luadns certbot-dns-nsone certbot-dns-rfc2136 certbot-nginx More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/50?closed=1
* Thu Mar 22 2018 ecsosAATTopensuse.org- update to 0.22.2
* Fixed - A type error introduced in 0.22.1 that would occur during challenge cleanup when a Certbot plugin raises an exception while trying to complete the challenge was fixed. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the time being, however, the only packages with changes other than their version number were: certbot More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/53?closed=1- changes from 0.22.1
* Changed - The ACME server used with Certbot\'s --dry-run and --staging flags is now Let\'s Encrypt\'s ACMEv2 staging server which allows people to also test ACMEv2 features with these flags.
* Fixed - The HTTP Content-Type header is now set to the correct value during certificate revocation with new versions of the ACME protocol. - When using Certbot with Let\'s Encrypt\'s ACMEv2 server, it would add a blank line to the top of chain.pem and between the certificates in fullchain.pem for each lineage. These blank lines have been removed. - Resolved a bug that caused Certbot\'s --allow-subset-of-names flag not to work. - Fixed a regression in acme.client.Client that caused the class to not work when it was initialized without a ClientNetwork which is done by some of the other projects using our ACME library. Despite us having broken lockstep, we are continuing to release new versions of all Certbot components during releases for the t ime being, however, the only packages with changes other than their version number were: acme certbot More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/51?closed=1
* Wed Mar 14 2018 ecsosAATTopensuse.org- update to 0.22.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Sat Jan 27 2018 ecsosAATTopensuse.org- update to 0.21.1 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Mon Dec 11 2017 ecsosAATTopensuse.org- update to 0.20.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Sat Oct 07 2017 ecsosAATTopensuse.org- update to 0.19.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Mon Oct 02 2017 jengelhAATTinai.de- Trim filler wording from description. Replace U+2019 (quote) by apostrophe. Wrap long lines. Replace old RPM macros and commands.
* Sat Sep 23 2017 ecsosAATTopensuse.org- update to 0.18.2 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Wed Sep 20 2017 ecsosAATTopensuse.org- BuildRequires for python-pyOpenSSL set to 17.0 because of convert python-acme into singlespec
* Mon Sep 11 2017 ecsosAATTopensuse.org- update to 0.18.1 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Fri Aug 25 2017 ecsosAATTopensuse.org- On request from upstream switch server parameter in cli.ini from staging to production server.- Change description in README.SUSE.
* Fri Aug 11 2017 ecsosAATTopensuse.org- update to 0.17.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md- update patch certbot-cli.ini.patch - remove deprecated parameter --standalone-supported-challenges - change preferred-challenges = tls-sni-01 to preferred-challenges = tls-sni as in documentation
* Fri Jul 07 2017 ecsosAATTopensuse.org- update to 0.16.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md
* Sun Jun 11 2017 ecsosAATTopensuse.org- update to 0.15.0 See https://github.com/certbot/certbot/blob/master/CHANGELOG.md and https://github.com/certbot/certbot/milestone/37?closed=1
* Wed Jun 07 2017 ecsosAATTopensuse.org- add missing domain parameter in cli.ini
* Wed Jun 07 2017 ecsosAATTopensuse.org- add missing dependency to python-future- rework README.SUSE and certbot.cron
* Thu Jun 01 2017 ecsosAATTopensuse.org- update to 0.14.2 See https://github.com/certbot/certbot/milestone/40?closed=1
* Wed May 17 2017 ecsosAATTopensuse.org- update to 0.14.1 See https://github.com/certbot/certbot/milestone/39?closed=1
* Tue May 16 2017 ecsosAATTopensuse.org- fix build error in Tumbleweed
* Mon May 15 2017 ecsosAATTopensuse.org- update t 0.14.0 See https://github.com/certbot/certbot/milestone/35?closed=1
* Tue Apr 25 2017 ecsosAATTopensuse.org- update to 0.13.0 See https://github.com/certbot/certbot/milestone/34?closed=1
* Mon Mar 27 2017 ecsosAATTopensuse.org- insert BuildRequires: python-packaging to prevent build errors for Leap 42.1
* Mon Mar 06 2017 ecsosAATTopensuse.org- change require version to python-requests >= 2.10
* Fri Mar 03 2017 ecsosAATTopensuse.org- update to 0.12.0 See https://github.com/certbot/certbot/milestone/31?closed=1
* Wed Feb 08 2017 ecsosAATTopensuse.org- update to 0.11.1 See https://github.com/certbot/certbot/milestone/33?closed=1- update to 0.11.0 See https://github.com/certbot/certbot/milestone/28?closed=1
* Sat Jan 28 2017 ecsosAATTopensuse.org- update to 0.10.2 See https://github.com/certbot/certbot/milestone/32?closed=1
* Tue Jan 17 2017 ecsosAATTopensuse.org- update to 0.10.1 See https://github.com/certbot/certbot/milestone/29?closed=1
* Wed Jan 11 2017 ecsosAATTopensuse.org- update to 0.10.0 See https://github.com/certbot/certbot/milestone/24?closed=1
* Fri Jan 06 2017 ecsosAATTopensuse.org- rework README.SUSE- fix sporadic build errors in doc section
* Tue Nov 01 2016 ecsosAATTopensuse.org- change certbot-cli.ini.patch The flag standalone-supported-challenges is deprecated. It is now preferred-challenges instead.
* Thu Oct 20 2016 ecsosAATTopensuse.org- update to 0.9.3 See https://github.com/certbot/certbot/milestone/27?closed=1- update to 0.9.2 See https://github.com/certbot/certbot/milestone/26?closed=1- update to 0.9.1 See https://github.com/certbot/certbot/milestone/25?closed=1
* Wed Oct 05 2016 ecsosAATTopensuse.org- update to 0.9.0 See https://github.com/certbot/certbot/milestone/22?closed=1
* Mon Aug 01 2016 ecsosAATTopensuse.org- python-requests >= 2.0 is required by certbot
* Fri Jul 15 2016 matwey.kornilovAATTgmail.com- psutils >= 2.2.1 is required by certbot 0.8.1: File \"/usr/lib/python2.7/site-packages/pkg_resources.py\", line 639, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: psutil>=2.2.1
* Sat Jun 18 2016 ecsosAATTopensuse.org- update to 0.8.1
* Sun Jun 05 2016 ecsosAATTopensuse.org- update to 0.8.0
* Tue May 31 2016 ecsosAATTopensuse.org- update to 0.7.0
* Sat May 14 2016 ecsosAATTopensuse.org- rename packge letsencrypt to new name certbot- change letsencrypt to certbot in spec file- obsolete letsencrypt in spec- Add patch certbot-fix_constants.patch to fix path locations from letsencrypt to certbot- update to 0.6.0
* Fri Apr 08 2016 ecsosAATTopensuse.org- update to 0.5.0
* Wed Mar 09 2016 jweberhoferAATTweberhofer.at- The /etc/letsencrypt/keys directory must exclusively be readable by root
* Wed Mar 09 2016 jweberhoferAATTweberhofer.at- Fixed version dependency to python-setuptools
* Mon Mar 07 2016 ecsosAATTopensuse.org- update to 0.4.2
* Tue Mar 01 2016 ecsosAATTopensuse.org- update to 0.4.1
* Sun Feb 14 2016 ecsosAATTopensuse.org- clean spec- don\'t build python-acme anymore, use seperate package instead because of correct errors in man and to run test within package building- move cli.ini changes from spec to patch file- insert cron file
* Thu Feb 11 2016 ecsosAATTopensuse.org- update to 0.4.0
* Fri Jan 29 2016 ecsosAATTopensuse.org- update to 0.3.0
* Tue Jan 19 2016 ecsosAATTopensuse.org- update to 0.2.0- remove no more needed versionstag patch
* Fri Jan 01 2016 ecsosAATTopensuse.org- add patch for versionstag mismatch
* Fri Dec 18 2015 ecsosAATTopensuse.org- update to 0.1.1
* Sun Dec 13 2015 ecsosAATTopensuse.org- update cli.ini parameters
* Fri Dec 04 2015 ecsosAATTopensuse.org- change from nighly git version to latest beta version 0.1.0
* Sat Sep 05 2015 ecsosAATTopensuse.org- add man pages- add python-letsencrypt-apache and python-letsencrypt-nginx
* Fri Sep 04 2015 ecsosAATTopensuse.org- add missing requirements
* Fri Aug 07 2015 ecsosAATTopensuse.org- inititial version: developer preview