Next | Query returned 38 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   2019-05-17 08:46:31 by Adam Ciarcinski | Files touched by this commit (20) | Package updated
Log message:
py-acme py-certbot*: updated to 0.34.2

0.34.2:

Fixed
certbot-auto no longer writes a check_permissions.py script at the root of the \ 
filesystem.
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 \ 
changes in this release were to certbot-auto.
   2019-05-07 10:50:37 by Adam Ciarcinski | Files touched by this commit (22) | Package updated
Log message:
py-acme,py-cerbot*: updated to 0.34.1

0.34.1:
Fixed

certbot-auto no longer prints a blank line when there are no permissions problems.
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 \ 
changes in this release were to certbot-auto.

More details about these changes can be found on our GitHub repo.

0.34.0:
Changed
Apache plugin now tries to restart httpd on Fedora using systemctl if a \ 
configuration test error is detected. This has to be done due to the way Fedora \ 
now generates the self signed certificate files upon first restart.
Updated Certbot and its plugins to improve the handling of file system \ 
permissions on Windows as a step towards adding proper Windows support to \ 
Certbot.
Updated urllib3 to 1.24.2 in certbot-auto.
Removed the fallback introduced with 0.32.0 in acme to retry a challenge \ 
response with a keyAuthorization if sending the response without this field \ 
caused a malformed error to be received from the ACME server.
Linode DNS plugin now supports api keys created from their new panel at \ 
cloud.linode.com
Adding a warning noting that future versions of Certbot will automatically \ 
configure the webserver so that all requests redirect to secure HTTPS access. \ 
You can control this behavior and disable this warning with the --redirect and \ 
--no-redirect flags.
certbot-auto now prints warnings when run as root with insecure file system \ 
permissions. If you see these messages, you should fix the problem by following \ 
the instructions at \ 
https://community.letsencrypt.org/t/cer … es/91979/, \ 
however, these warnings can be disabled as necessary with the flag \ 
--no-permissions-check.
acme module uses now a POST-as-GET request to retrieve the registration from an \ 
ACME v2 server
Convert the tsig algorithm specified in the certbot_dns_rfc2136 configuration \ 
file to all uppercase letters before validating. This makes the value in the \ 
config case insensitive.
   2019-04-08 17:48:31 by Adam Ciarcinski | Files touched by this commit (23) | Package updated
Log message:
py-acme,py-certbot*: updated to 0.33.1

0.33.1:

Fixed
A bug causing certbot-auto to print warnings or crash on some RHEL based systems \ 
has been resolved.
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 \ 
changes in this release were to certbot-auto.

0.33.0:

Added
Fedora 29+ is now supported by certbot-auto. Since Python 2.x is on a \ 
deprecation path in Fedora, certbot-auto will install and use Python 3.x on \ 
Fedora 29+.
CLI flag --https-port has been added for Nginx plugin exclusively, and replaces \ 
--tls-sni-01-port. It defines the HTTPS port the Nginx plugin will use while \ 
setting up a new SSL vhost. By default the HTTPS port is 443.

Changed
Support for TLS-SNI-01 has been removed from all official Certbot plugins.
Attributes related to the TLS-SNI-01 challenge in acme.challenges and \ 
acme.standalone modules are deprecated and will be removed soon.
CLI flags --tls-sni-01-port and --tls-sni-01-address are now no-op, will \ 
generate a deprecation warning if used, and will be removed soon.
Options tls-sni and tls-sni-01 in --preferred-challenges flag are now no-op, \ 
will generate a deprecation warning if used, and will be removed soon.
CLI flag --standalone-supported-challenges has been removed.

Fixed
Certbot uses the Python library cryptography for OCSP when cryptography>=2.5 \ 
is installed. We fixed a bug in Certbot causing it to interpret timestamps in \ 
the OCSP response as being in the local timezone rather than UTC.
Issue causing the default CentOS 6 TLS configuration to ignore some of the HTTPS \ 
VirtualHosts created by Certbot. mod_ssl loading is now moved to main http.conf \ 
for this environment where possible.
   2019-03-10 16:23:51 by Adam Ciarcinski | Files touched by this commit (21) | Package updated
Log message:
py-certbot: updated to 0.32.0

Added
If possible, Certbot uses built-in support for OCSP from recent cryptography \ 
versions instead of the OpenSSL binary: as a consequence Certbot does not need \ 
the OpenSSL binary to be installed anymore if cryptography>=2.5 is installed.

Changed
Certbot and its acme module now depend on josepy>=1.1.0 to avoid printing the \ 
warnings described at https://github.com/certbot/josepy/issues/13.
Apache plugin now respects CERTBOT_DOCS environment variable when adding command \ 
line defaults.
The running of manual plugin hooks is now always included in Certbot's log output.
Tests execution for certbot, certbot-apache and certbot-nginx packages now \ 
relies on pytest.
An ACME CA server may return a "Retry-After" HTTP header on \ 
authorization polling, as specified in the ACME protocol, to indicate when the \ 
next polling should occur. Certbot now reads this header if set and respect its \ 
value.
The acme module avoids sending the keyAuthorization field in the JWS payload \ 
when responding to a challenge as the field is not included in the current ACME \ 
protocol. To ease the migration path for ACME CA servers, Certbot and its acme \ 
module will first try the request without the keyAuthorization field but will \ 
temporarily retry the request with the field included if a malformed error is \ 
received. This fallback will be removed in version 0.34.0.
   2019-02-12 13:56:32 by Adam Ciarcinski | Files touched by this commit (17) | Package updated
Log message:
py-acme,py-certbot*: updated to 0.31.0

0.31.0:

Added
Avoid reprocessing challenges that are already validated when a certificate is \ 
issued.
Support for initiating (but not solving end-to-end) TLS-ALPN-01 challenges with \ 
the acme module.

Changed
Certbot's official Docker images are now based on Alpine Linux 3.9 rather than \ 
3.7. The new version comes with OpenSSL 1.1.1.
Lexicon-based DNS plugins are now fully compatible with Lexicon 3.x (support on \ 
2.x branch is maintained).
Apache plugin now attempts to configure all VirtualHosts matching requested \ 
domain name instead of only a single one when answering the HTTP-01 challenge.

Fixed
Fixed accessing josepy contents through acme.jose when the full acme.jose path \ 
is used.
Clarify behavior for deleting certs as part of revocation.
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 \ 
package with changes other than its version number was:

acme
certbot
certbot-apache
certbot-dns-cloudxns
certbot-dns-dnsimple
certbot-dns-dnsmadeeasy
certbot-dns-gehirn
certbot-dns-linode
certbot-dns-luadns
certbot-dns-nsone
certbot-dns-ovh
certbot-dns-sakuracloud
More details about these changes can be found on our GitHub repo.
   2019-01-15 13:07:25 by =?UTF-8?B?RnLDqWTDqXJpYyBGYXViZXJ0ZWF1?= | Files touched by this commit (1)
Log message:
py-certbot: add ovh, sakura cloud and nginx plugins
   2019-01-15 10:32:11 by =?UTF-8?B?RnLDqWTDqXJpYyBGYXViZXJ0ZWF1?= | Files touched by this commit (3) | Package updated
Log message:
py-certbot: update to 0.30.0

Upstream changes:
================================================================================
## 0.30.0 - 2019-01-02

### Added

* Added the `update_account` subcommand for account management commands.

### Changed

* Copied account management functionality from the `register` subcommand
  to the `update_account` subcommand.
* Marked usage `register --update-registration` for deprecation and
  removal in a future release.

### Fixed

* Older modules in the josepy library can now be accessed through acme.jose
  like it could in previous versions of acme. This is only done to preserve
  backwards compatibility and support for doing this with new modules in josepy
  will not be added. Users of the acme library should switch to using josepy
  directly if they haven't done so already.

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
package with changes other than its version number was:

* acme

More details about these changes can be found on our GitHub repo.

## 0.29.1 - 2018-12-05

### Added

*

### Changed

*

### Fixed

* The default work and log directories have been changed back to
  /var/lib/letsencrypt and /var/log/letsencrypt respectively.

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
package with changes other than its version number was:

* certbot

More details about these changes can be found on our GitHub repo.

## 0.29.0 - 2018-12-05

### Added

* Noninteractive renewals with `certbot renew` (those not started from a
  terminal) now randomly sleep 1-480 seconds before beginning work in
  order to spread out load spikes on the server side.
* Added External Account Binding support in cli and acme library.
  Command line arguments --eab-kid and --eab-hmac-key added.

### Changed

* Private key permissioning changes: Renewal preserves existing group mode
  & gid of previous private key material. Private keys for new
  lineages (i.e. new certs, not renewed) default to 0o600.

### Fixed

* Update code and dependencies to clean up Resource and Deprecation Warnings.
* Only depend on imgconverter extension for Sphinx >= 1.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
package with changes other than its version number was:

* acme
* certbot
* certbot-apache
* certbot-dns-cloudflare
* certbot-dns-digitalocean
* certbot-dns-google
* certbot-nginx

More details about these changes can be found on our GitHub repo:
https://github.com/certbot/certbot/mile … 2?closed=1

## 0.28.0 - 2018-11-7

### Added

* `revoke` accepts `--cert-name`, and doesn't accept both `--cert-name` and \ 
`--cert-path`.
* Use the ACMEv2 newNonce endpoint when a new nonce is needed, and newNonce is \ 
available in the directory.

### Changed

* Removed documentation mentions of `#letsencrypt` IRC on Freenode.
* Write README to the base of (config-dir)/live directory
* `--manual` will explicitly warn users that earlier challenges should remain in \ 
place when setting up subsequent challenges.
* Warn when using deprecated acme.challenges.TLSSNI01
* Log warning about TLS-SNI deprecation in Certbot
* Stop preferring TLS-SNI in the Apache, Nginx, and standalone plugins
* OVH DNS plugin now relies on Lexicon>=2.7.14 to support HTTP proxies
* Default time the Linode plugin waits for DNS changes to propogate is now 1200 \ 
seconds.

### Fixed

* Match Nginx parser update in allowing variable names to start with `${`.
* Fix ranking of vhosts in Nginx so that all port-matching vhosts come first
* Correct OVH integration tests on machines without internet access.
* Stop caching the results of ipv6_info in http01.py
* Test fix for Route53 plugin to prevent boto3 making outgoing connections.
* The grammar used by Augeas parser in Apache plugin was updated to fix various \ 
parsing errors.
* The CloudXNS, DNSimple, DNS Made Easy, Gehirn, Linode, LuaDNS, NS1, OVH, and
  Sakura Cloud DNS plugins are now compatible with Lexicon 3.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
package with changes other than its version number was:

* acme
* certbot
* certbot-apache
* certbot-dns-cloudxns
* certbot-dns-dnsimple
* certbot-dns-dnsmadeeasy
* certbot-dns-gehirn
* certbot-dns-linode
* certbot-dns-luadns
* certbot-dns-nsone
* certbot-dns-ovh
* certbot-dns-route53
* certbot-dns-sakuracloud
* certbot-nginx

More details about these changes can be found on our GitHub repo:
https://github.com/certbot/certbot/mile … 9?closed=1

## 0.27.1 - 2018-09-06

### Fixed

* Fixed parameter name in OpenSUSE overrides for default parameters in the
  Apache plugin. Certbot on OpenSUSE works again.

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
package with changes other than its version number was:

* certbot-apache

More details about these changes can be found on our GitHub repo:
https://github.com/certbot/certbot/mile … 0?closed=1
   2018-12-15 22:12:25 by Thomas Klausner | Files touched by this commit (67) | Package updated
Log message:
*: update email for fhajny
   2018-09-06 14:25:26 by Filip Hajny | Files touched by this commit (3) | Package updated
Log message:
py-{acme,certbot}: Update to 0.27.0.

## 0.27.0 - 2018-09-05

### Added

- The Apache plugin now accepts the parameter --apache-ctl which can
  be used to configure the path to the Apache control script.

### Changed

- When using `acme.client.ClientV2` (or
 `acme.client.BackwardsCompatibleClientV2` with an ACME server that
 supports a newer version of the ACME protocol), an
 `acme.errors.ConflictError` will be raised if you try to create
 an ACME account with a key that has already been used. Previously,
 a JSON parsing error was raised in this scenario when using the
 library with Let's Encrypt's ACMEv2 endpoint.

### Fixed

- When Apache is not installed, Certbot's Apache plugin no longer
  prints messages about being unable to find apachectl to the
  terminal when the plugin is not selected.
- If you're using the Apache plugin with the --apache-vhost-root flag
  set to a directory containing a disabled virtual host for the
  domain you're requesting a certificate for, the virtual host will
  now be temporarily enabled if necessary to pass the HTTP challenge.
- The documentation for the Certbot package can now be built using
  Sphinx 1.6+.
- You can now call `query_registration` without having to first call
  `new_account` on `acme.client.ClientV2` objects.
- The requirement of `setuptools>=1.0` has been removed from
  `certbot-dns-ovh`.
- Names in certbot-dns-sakuracloud's tests have been updated to refer
  to Sakura Cloud rather than NS1 whose plugin certbot-dns-sakuracloud
  was based on.

## 0.26.1 - 2018-07-17

### Fixed

- Fix a bug that was triggered when users who had previously manually
  set `--server` to get ACMEv2 certs tried to renew ACMEv1 certs.
   2018-07-24 11:24:11 by =?UTF-8?B?RnLDqWTDqXJpYyBGYXViZXJ0ZWF1?= | Files touched by this commit (1)
Log message:
Add used by comment for py-certbot-dns-rfc2136.

Next | Query returned 38 messages, browsing 1 to 10 | Previous