| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"
|
| |
|
|
|
| |
Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
|
|
|
|
|
| |
Using SecureRandom is slow if it is not initialized.
Random is good enough for this test.
|
|
|
|
|
| |
This test is causing the rspec tests in appveyor to exit
with 116
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rerunning ohai wastes a lot of time. This should
get us back to within our time limits in appveyor
even with the perf regression in Ohai.
Don't rerun ohai for unit/regsitry_helper_spec
Ohai is slow. We don't need to rerun this, it's
already run in our spec_helper.
Don't keep rerunning ohai for reboot_pending_spec
Running Ohai is slow. This should know almost 2
mins off the runtime of the tests.
Don't need to run ohai for registry_spec
crypto_spec does not need its own ohai
cmdlet_spec does not need its own ohai
functional registry_helper_spec does not need its own ohai
Use spec ohai system for knife configure_spec
Use OHAI_SYSTEM for dsc_script_spec
use OHAI_SYSTEM for dsc_resource_spec
|
|
|
|
| |
Running ohai is slow
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
tests won't run in isolation with it.
|
|\
| |
| | |
Fix inverted filter logic for not_fips rspec filter
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
1. Warn when default values are invalid.
2. Never validate nil (on set or get) if there is no default.
3. Emit "will be invalid in Chef 13" warning when setting an invalid nil value.
|
|\ \
| |/
|/| |
Lcg/suppress reporter failures
|
| |
| |
| |
| |
| |
| |
| | |
- doesn't turn off the utf8 validation in the rest of the rest API
- has to use a different rest object because we have to pass options
in the constructor
- the handling of Chef::Config in Chef::Client is just awful
|
|\ \
| | |
| | | |
adds EOFError message to handlers
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add an apt_update resource
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
Default Chef with FIPS OpenSSL to use sign v1.3
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We need to ask openssl for the pem whenever we have a private key
so that it returns the same format of key (PKCS#1 vs PKCS#8) that
openssl generates
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
aes-256-cbc does not seem to work when openssl is in fips mode.
The only other reference I could find to this was:
https://access.redhat.com/solutions/176633
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The AuthCredentials class does not do anything special
with regards to the key. We should only need to check
that the one we passed in, not that it's pem representation.
The reason for removing this extra (unneeded) check is
because it breaks when openssl is in fips mode. When in
that mode, openssl with generate a PKCS#8 pem representation, while
the thing that we checked against was a PKCS#1 pem representation.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some notes:
* Add module overrides for fips
We need to use the SHA1 module under OpenSSL because the openssl
functions called by Digest::SHA1 cause openssl to crash the process.
We use the Digest::MD5 over the OpenSSL::MD5 module because md5
is not allowed when in fips mode and causes the process to crash.
While we work through these issues, we're going to allow it to
pass by compiling the ruby md5 implementation.
* Use OpenSSL::Digest::SHA256 instead of Digest::SHA256
Digest::SHA256 is broken in fips mode because it uses
unapproved APIs. They cause the process to terminate.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
According to https://abcofaix.wordpress.com/tag/usermod/, the value
can be up to 200. We were seeing tests on our aix testers fail with
```
1) Chef::Provider::User::Useradd action :create when the user does not exist beforehand when a system user is specified ensures the user has the properties of a system user
Failure/Error: expect(pw_entry.uid.to_i).to be < uid_min.to_i
expected: < 100
got: 101
# ./spec/functional/resource/user/useradd_spec.rb:306:in `block (5 levels) in <top (required)>'
```
|
|\ \ \ \
| | | | |
| | | | | |
zypper multipackage patch
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | | |
See #3570
|
|\ \ \ \
| | | | |
| | | | | |
Seeing a useradd failuer in Nexus7 functional tests
|
| |/ / /
| | | |
| | | |
| | | | |
home directory is expected
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
unless using properties on the resource
|
| | | |
|