You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/facter/3.11/release_notes.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,17 @@ title: "Facter release notes"
6
6
These are the new features, resolved issues, and deprecations in this version of Facter.
7
7
8
8
9
+
## Facter 3.11.10
10
+
11
+
Released 15 October 2019 with Puppet 5.5.17.
12
+
13
+
### Resolved issues
14
+
15
+
- Google Compute Engine's internal metadata service is deprecating the v1beta1 endpoint sometime before the end of 2019. To prepare for this, Facter now uses the v1 endpoint instead. [FACT-2018](https://tickets.puppetlabs.com/browse/FACT-2018)
16
+
17
+
- When Facter starts a mountpoint to get the size and available space, it automatically mounts type `autofs` mountpoints, which is not the intended behavior. Automounts are now skipped by Facter when resolving mountpoints. [FACT-1992](https://tickets.puppetlabs.com/browse/FACT-1992)
Copy file name to clipboardExpand all lines: source/puppet/5.5/release_notes.markdown
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,52 @@ Read the [Puppet 5.1](https://github.com/puppetlabs/docs-archive/blob/master/pup
20
20
21
21
Also of interest: the [Puppet 4.10 release notes](../4.10/release_notes.html) and [Puppet 4.9 release notes](https://github.com/puppetlabs/docs-archive/blob/master/puppet/4.9/release_notes.markdown).
22
22
23
+
## Puppet 5.5.17
24
+
25
+
Released 15 October 2019
26
+
27
+
This is a bug-fix and new feature release.
28
+
29
+
### New features
30
+
31
+
- The `exec` type's `onlyif` and `unless` checks now return redacted output if it is marked sensitive. [PUP-9956](https://tickets.puppetlabs.com/browse/PUP-9956)
32
+
33
+
- You can now specify `no_proxy` as a Puppet setting, consistent with other `http_proxy_*` Puppet settings. The `NO_PROXY` environment variable takes precedence over the `no_proxy` Puppet setting. [PUP-9316](https://tickets.puppetlabs.com/browse/PUP-9316)
34
+
35
+
- Installation time on larger modules has been improved. Previously, on platforms that had the minitar gem installed, mintar would fsync every directory and file, causing long extraction times during module installation. Puppet now uses minitar 0.9, with this fsync option turned off by default. [PUP-10013](https://tickets.puppetlabs.com/browse/PUP-10013)
36
+
37
+
- Puppet can now set Windows service startup type to Auto-Start (Delayed). To set a service to use this setting, set the `enable` parameter of the `service` resource to "delayed". [PUP-6382](https://tickets.puppetlabs.com/browse/PUP-6382)
38
+
39
+
- When running in daemon mode, Puppet logs the configuration used on agent startup at the debug level. The log is sent to the output specified by the `--logdest` option. Configuration is reloaded and also logged on SIGHUP. [PUP-9754](https://tickets.puppetlabs.com/browse/PUP-9754)
40
+
41
+
### Resolved issues
42
+
43
+
- This version upgrades the Ruby version to 2.5.7 to address the following security issues:
44
+
*[CVE-2019-16255](https://www.ruby-lang.org/en/news/2019/10/01/code-injection-shell-test-cve-2019-16255/): A code injection vulnerability of Shell#[] and Shell#test
45
+
*[CVE-2019-16201](https://www.ruby-lang.org/en/news/2019/10/01/webrick-regexp-digestauth-dos-cve-2019-16201/): Regular Expression Denial of Service vulnerability of WEBrick's Digest access authentication
46
+
*[CVE-2019-16254](https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254/): HTTP response splitting in WEBrick (Additional fix)
47
+
*[CVE-2019-15845](https://www.ruby-lang.org/en/news/2019/10/01/nul-injection-file-fnmatch-cve-2019-15845/): A NUL injection vulnerability of File.fnmatch and File.fnmatch?
- This version upgrades OpenSSL to 1.0.2t to address CVE-2019-1547, CVE-2019-1549 and CVE-2019-1563. For more details, see the [OpenSSL Security Advisory](https://www.openssl.org/news/secadv/20190910.txt).
51
+
52
+
- This version includes a security update to curl 7.66.0 to address [CVE-2019-5481](https://curl.haxx.se/docs/CVE-2019-5481.html) and [CVE-2019-5482](https://curl.haxx.se/docs/CVE-2019-5482.html).
53
+
54
+
- Previously, the `puppet resource --to_yaml` and `puppet device --to_yaml` commands did not generate valid YAML if the output contained special characters such as a single quote. [PUP-7808](https://tickets.puppetlabs.com/browse/PUP-7808)
55
+
56
+
- Prior to this release, Puppet silently ignored truncated file downloads, such as when using a file resource whose source parameter contained a `puppet://`, `http://`, or `https://` URL. This issue was caused by a Ruby issue and is fixed in this release. [PA-2849](https://tickets.puppetlabs.com/browse/PA-2849)
57
+
58
+
- The `puppet plugin download` command now reuses HTTPS connections. This significantly speeds up the download process. [PUP-8662](https://tickets.puppetlabs.com/browse/PUP-8662)
59
+
60
+
- If the agent is configured to use an HTTP proxy, and it attempts to connect to a host that matches an entry in the `NO_PROXY` environment variable, then Puppet connects directly to the host instead of using the proxy. This feature was originally introduced in Puppet 4.2, but it did not work. [PUP-9942](https://tickets.puppetlabs.com/browse/PUP-9942)
61
+
62
+
- Agents could not connect through an authenticating HTTP proxy when making REST requests to Puppet infrastructure, such as when requesting a catalog. Now agents will observe the `http_proxy_user` and `http_proxy_password` settings or `HTTP_PROXY_USER/PASSWORD` environment variables when making those requests. [PUP-4470](https://tickets.puppetlabs.com/browse/PUP-4470)
63
+
64
+
- If an HTTP proxy is configured either in Puppet settings or the `HTTP_PROXY_*` environment variables, then Puppet does not use the proxy when connecting to localhost or 127.0.0.1. This behavior can be modified by changing the `no_proxy` setting in puppet.conf or the `NO_PROXY` environment variable. [PUP-2172](https://tickets.puppetlabs.com/browse/PUP-2172)
0 commit comments