7;INPUT:filter:IPv4':
purge => true,
ignore => [ '-j fail2ban-ssh' ],
}
If you search the puppetlabs/firewall documentation for "fail2ban"
there's an example buried in there.
Tim.
--
Tim Bishop
http://www.bishnet.net/tim/
PGP Key: 0x6C226B37FDF38D55
--
> $ssh_config = '/etc/ssh/ssh_config'
> $ssh_known_hosts = '/etc/ssh/ssh_known_hosts'
> $service_name = 'sshd'
> }
> default: {
> fail("Unsupported platform:
> ${::osfamily}/${::operatingsystem}")
> }
> }
> My module runs fin
e the requests
from the puppet/ssl/ca/requests directory.
Tim.
On Fri, Dec 14, 2012 at 04:53:42PM -0800, Ellison Marks wrote:
> You might try puppet cert print to get more info about the thing, but
> out of curiosity, how did it get on your master in the first place?
>
> On Friday, Dece
number for fb311ff01c6f0130b650005056bc6664
Looks like it only cleans signed certificates, not requests.
Tim.
On Fri, Dec 14, 2012 at 10:33:30AM -0800, Ellison Marks wrote:
> Does puppet cert clean not do it?
>
> On Friday, December 14, 2012 9:43:12 AM UTC-8, Tim Bishop wrote:
> > I've
Hi,
I've got some certificate requests on my puppet master that I wish to
remove. It looks like the "puppet cert" tool doesn't have an option for
doing that? What's the best approach, just manually remove them from the
puppet/ssl/ca/requests directory?
Tim.
--
Tim Bish
meters each call of the definition. I'd like a for
loop really!
Any pointers? Am I looking at this completely the wrong way?
The only alternative I've come up with is to just manually create the
links with file resources where I call mymodule::site, but I ideally
wanted to encapsulate al
