Age | Commit message (Collapse) | Author |
|
all stunnel client/servers will need handled (at least in debian and ubuntu)
|
|
This presents us with an interesting problem of deprecation. We need to manage
the removal of something that we previously installed in any released code. How
long we carry the puppet code that removes raises some interesting questions: do
we require that someone who deployed version 1 (where the apache ssl proxy was
deployed) of the platform upgrade first to version 2 (where we remove the apache
ssl proxy) before they upgrade to version 3 (where the apache ssl proxy removal
is no longer present) -- or do we allow people to skip versions?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
we need to find another way to disable futon, it won't work disabling
it here
|
|
|
|
directly
|
|
|
|
|
|
|
|
|
|
special client certificates with the FREE prefix in the common name.
|
|
configuration file, this addresses issue #1853
- [vpn1] err: /Stage[main]/Site_openvpn::Resolver/Line[add_tcp_resolver]/Exec[echo 'server: include: /etc/unbound/conf.d/vpn_tcp_resolver' >> '/etc/unbound/unbound.conf']/returns: change from notrun to 0 failed: echo 'server: include: /etc/unbound/conf.d/vpn_tcp_resolver' >> '/etc/unbound/unbound.conf' returned 2 instead of one of [0] at /srv/leap/puppet/modules/common/manifests/defines/line.pp:45
|
|
site_shorewall
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
slows things down and I don't see a need for it
|
|
site_shorewall
|
|
shorewall is installed first (#1741)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|