Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow ssl_certs_dir to be unset. #787

Merged
merged 1 commit into from
Jul 3, 2014

Conversation

tdb
Copy link
Contributor

@tdb tdb commented Jul 2, 2014

In some cases we don't want SSLCACertificatePath to be set at all. If we're using SSLCACertificateFile instead to verify clients we might want that to be the only CA used. Most other options in this template are optional, so I don't see why this one can't be too.

In some cases we don't want SSLCACertificatePath to be set at all.
If we're using SSLCACertificateFile instead to verify clients we
might want that to be the only CA used. Most other options in this
template are optional, so I don't see why this one can't be too.
apenney pushed a commit that referenced this pull request Jul 3, 2014
Allow ssl_certs_dir to be unset.
@apenney apenney merged commit 04b74e4 into puppetlabs:master Jul 3, 2014
underscorgan pushed a commit to underscorgan/puppetlabs-apache that referenced this pull request Nov 7, 2014
The SSLCACertificatePath is always set. The check for @ssl_certs_dir only
covers "undef". As there is a default value in ::apache::params for
ssl_certs_dir it needs to be overriden with an empty string.

Right now the _ssl.erb template outputs 'SSLCACertificatePath ""' for an empty
string, which triggers a failing reload of httpd.

This patch just adds a "&& @ssl_certs_dir != ''" to the condition.

On a Puppet master passenger vhost it's probably  security relevant setting,
as it enables all system CA signed certificates access.

Related patch: puppetlabs#787
traylenator pushed a commit to traylenator/puppetlabs-apache that referenced this pull request Jun 7, 2022
Fix missing comma in docker::image example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants