summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Suppress values on converge when a property is marked sensitivesensitive_propertiesTim Smith2017-11-081-3/+3
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Update CHANGELOG.md to reflect the promotion of 13.6.4 to stableChef Expeditor2017-11-062-15/+12
|
* Merge pull request #6572 from chef/13_6_4_notesTim Smith2017-11-061-0/+11
|\ | | | | Add 13.6.4 release notes
| * Add 13.6.4 release notes13_6_4_notesTim Smith2017-11-061-0/+11
|/ | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 13.6.4 by Expeditorv13.6.4Chef Expeditor2017-11-065-11/+12
|
* Merge pull request #6568 from chef/openssl_bumpLamont Granquist2017-11-062-14/+14
|\ | | | | Bump openssl and rubygems to latest
| * Bump openssl and rubygems to latestTim Smith2017-11-062-14/+14
|/ | | | | | | | | | | | | | | | openssl: CVE-2017-3736 (OpenSSL advisory) [Moderate severity] 2nd November 2017: There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen. Reported by Google OSS-Fuzz. CVE-2017-3735 (OpenSSL advisory) [Low severity] 28th August 2017: While parsing an IPAdressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. Reported by Google OSS-Fuzz. rubygems: Whitelist classes and symbols that are in loaded YAML. See CVE-2017-0903 for full details. Fix by Aaron Patterson. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 13.6.3 by Expeditorv13.6.3Chef Expeditor2017-11-045-11/+12
|
* Bump version to 13.6.2 by Expeditorv13.6.2Chef Expeditor2017-11-045-11/+12
|
* Merge pull request #6558 from chef/fix_pkgsTim Smith2017-11-034-4/+66
|\ | | | | Fix the invalid version comparison in apt/dpkg providers
| * Avoid the need to parse nil versions in the package providerTim Smith2017-11-034-4/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we don't have a version installed yet we shouldn't go do a version comparison with nil. No matter what that's a waste of time and in dpkg/apt it's going to require shelling out now. Instead just do the install. This also adds the same version comparison method to the dpkg resource. At the moment it doesn't look like this is going to get called since our upgrade action there is a bit broken (doesn't actually compare versions), but that's going to get fixed next. This also cleans up the version comparison to make sure we're always dealing with strings Signed-off-by: Tim Smith <tsmith@chef.io>
| * Fix the invalid version comparison of apt packages.pr/6554Takuto Komazaki2017-11-021-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The strings of dpkg versions are more complex than the Gem::Version and not compatible with it. Using Gem::Version to compare versions of dpkg packages will cause mistakes or raise the exeption of 'Malformed version number..'. please see a simple example: https://gist.github.com/komazarari/c6b33b29a0e31e9c62bbc2f0b2091647 Prefer to use the dpkg cli. https://debian-handbook.info/browse/en-US/stable/sect.manipulating-packages-with-dpkg.html Signed-off-by: Takuto Komazaki <komazarari@gmail.com>
* | Merge pull request #6559 from chef/tsmith_mailmapTim Smith2017-11-031-0/+4
|\ \ | |/ |/| Add mailmap entries for Tim Smith
| * Add mailmap entries for Tim Smithtsmith_mailmapTim Smith2017-11-031-0/+4
|/ | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Update CHANGELOG.md to reflect the promotion of 13.6.0 to stableChef Expeditor2017-10-302-28/+32
|
* Merge pull request #6529 from chef/deprecation_notesTim Smith2017-10-301-0/+4
|\ | | | | Update the Ohai 13.6 release notes
| * Update the Ohai 13.6 release notesdeprecation_notesTim Smith2017-10-261-0/+4
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* | Bump version to 13.6.1 by Expeditorv13.6.1Chef Expeditor2017-10-275-11/+12
| |
* | Merge pull request #6425 from ↵Bryan McLellan2017-10-271-7/+33
|\ \ | | | | | | | | | | | | MsysTechnologiesllc/harry/add_missing_functional_tests [MSYS-492]Add missing functional tests for users
| * | add missing functional tests for usersMSys2017-10-271-7/+33
| | | | | | | | | | | | Signed-off-by: MSys <harikesh.kolekar@msystechnologies.com>
* | | Bump version to 13.6.0 by Expeditorv13.6.0Chef Expeditor2017-10-273-7/+7
| | |
* | | Merge pull request #6536 from chef/tm/13_6Thom May2017-10-272-1/+20
|\ \ \ | |/ / |/| | prep 13.6 for release
| * | prep 13.6 for releasetm/13_6Thom May2017-10-272-1/+20
|/ / | | | | | | Signed-off-by: Thom May <thom@chef.io>
* | Bump version to 13.5.28 by Expeditorv13.5.28Chef Expeditor2017-10-275-12/+13
| |
* | Merge pull request #6532 from chef/libiconvThom May2017-10-271-2/+2
|\ \ | | | | | | Pull in the latest libiconv and nokogiri
| * | Use nokogiri 1.8.1Tim Smith2017-10-261-1/+1
| | | | | | | | | | | | | | | | | | Minor bug fixes and updated vendored libs that we've already bumped to. Signed-off-by: Tim Smith <tsmith@chef.io>
| * | Update libiconv to 1.15Tim Smith2017-10-261-1/+1
| |/ | | | | | | | | | | | | It's 1.15 in Chef 12. I think when omnibus overrides were changed around this slipped through the cracks. Signed-off-by: Tim Smith <tsmith@chef.io>
* | Merge pull request #6530 from chef/release_notesTim Smith2017-10-261-5/+5
|\ \ | |/ |/| Remove msys ticket numbers from changelog
| * Remove msys ticket numbers from changelogTim Smith2017-10-261-5/+5
|/ | | | | | This doesn't mean anything to an external user Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 13.5.27 by Expeditorv13.5.27Chef Expeditor2017-10-265-12/+13
|
* Merge pull request #6520 from chef/update_depsTim Smith2017-10-262-22/+26
|\ | | | | Use the latest libxml2, libxslt, libyaml, and openssl
| * Use latest omnibus-softwareupdate_depsTim Smith2017-10-251-18/+22
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Use the latest libxml2, libxslt, libyaml, and opensslTim Smith2017-10-251-4/+4
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libxml2: A GIANT list of bugfixes and these CVEs: CVE-2017-9050 CVE-2017-9049 CVE-2017-9048 CVE-2017-9047 CVE-2017-8872 CVE-2016-9318 https://www.cvedetails.com/vulnerability-list/vendor_id-1962/product_id-3311/Xmlsoft-Libxml2.html libxslt: - Fixes bad memory handling and null derefs plus a GIANT list of bug libyaml: * Fixed segfault in yaml_string_write_handler. * Fixed invalid simple key assertion. * Fixed error handling in some examples (thank to Mathias Svensson). * Removed obsolete VS project files. openssl: CVE-2017-3731 (OpenSSL advisory) [Moderate severity] 26th January 2017: If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k Reported by Robert Święcki of Google. CVE-2017-3732 (OpenSSL advisory) [Moderate severity] 26th January 2017: There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem. Reported by OSS-Fuzz project. CVE-2016-7055 (OpenSSL advisory) [Low severity] 10th November 2016: There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected.ctures using a callback which do not handle NULL value are affected. Reported by Publicly reported. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 13.5.26 by Expeditorv13.5.26Chef Expeditor2017-10-255-11/+12
|
* Merge pull request #6521 from chef/btm/ohai_13_6Tim Smith2017-10-252-1/+23
|\ | | | | Include Ohai 13.6
| * Include Ohai 13.6btm/ohai_13_6Bryan McLellan2017-10-252-1/+23
|/ | | | | | | | | | | | | | | | | | | | | | | | | Ohai Release Notes 13.6 - Critical Plugins Users can now specify a list of plugins which are `critical`. Critical plugins will cause Ohai to fail if they do not run successfully (and thus cause a Chef run using Ohai to fail). The syntax for this is: ``` ohai.critical_plugins << :Filesystem ``` - Filesystem now has a `allow_partial_data` configuration option The Filesystem plugin now has a `allow_partial_data` configuration option. If set, the filesystem will return whatever data it can even if some commands it ran failed. - Rackspace detection on Windows Windows nodes running on Rackspace will now properly detect themselves as running on Rackspace without a hint file. - Package data on Amazon Linux The Packages plugin now supports gathering packages data on Amazon Linux Signed-off-by: Bryan McLellan <btm@loftninjas.org>
* Bump version to 13.5.25 by Expeditorv13.5.25Chef Expeditor2017-10-205-11/+12
|
* Merge pull request #6468 from coderanger/deprecate-deployNoah Kantrowitz2017-10-193-1/+28
|\ | | | | Deprecate the deploy resource and family
| * Add some release notes. Noah Kantrowitz2017-10-191-1/+12
| | | | | | Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
| * Deprecate the deploy resource and family.Noah Kantrowitz2017-10-032-0/+16
| | | | | | | | Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
* | Bump version to 13.5.24 by Expeditorv13.5.24Chef Expeditor2017-10-195-11/+12
| |
* | Merge pull request #6510 from chef/nodes_not_hereAdam Leff2017-10-193-4/+3
|\ \ | | | | | | Fix remote_file with UNC paths failing
| * | Fix remote_file with UNC paths failingnodes_not_hereTim Smith2017-10-193-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our check here to see if we're on Windows uses node data that's not available in this context. Use the same Chef::Platform.windows? check we use above. Without this you get the following error: [2017-10-02T21:40:42+00:00] DEBUG: Re-raising exception: NameError - remote_file[c:/foo/bar] (foo::default line 14) had an error: NameError: undefined local variable or method `node' for #<Chef::Provider::RemoteFile::NetworkFile:0x00000000064c0148> Signed-off-by: Tim Smith <tsmith@chef.io>
* | | Bump version to 13.5.23 by Expeditorv13.5.23Chef Expeditor2017-10-195-11/+12
| | |
* | | Merge pull request #6511 from chef/adamleff/bump-inspecTim Smith2017-10-191-19/+19
|\ \ \ | |/ / |/| | Bump dependencies to pull in new InSpec
| * | Bump dependencies to pull in new InSpecAdam Leff2017-10-191-19/+19
|/ / | | | | | | Signed-off-by: Adam Leff <adam@leff.co>
* | Bump version to 13.5.22 by Chef Expeditorv13.5.22Chef Expeditor2017-10-175-11/+12
| |
* | Merge pull request #6437 from MsysTechnologiesllc/dh/array_choco_pkg_artifactoryBryan McLellan2017-10-162-9/+16
|\ \ | | | | | | [MSYS-647] array support for choco pkg from artifactory
| * | update code to fix appveyor issuesAdministrator2017-10-051-10/+3
| | | | | | | | | | | | Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
| * | Fix travis failuresdheerajd-msys2017-09-291-1/+3
| | | | | | | | | | | | Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
View Lorry Controller Status