gt; How about writing a login_* program for /usr/libexec/auth? It would be
> sufficient to check if there have been too many login attempts recently,
> and if not, call /usr/libexec/auth/login_passwd (or similar), and pass
> the response.
>
> There is quite a bit of information in login.conf(5). You'll also need
> to modify this file, so it's a good place to start.
>
> Joachim
>
>
--
Mark Maxey
Information Security Specialist - Masters of Tech
[EMAIL PROTECTED]
Phone: 859.948.5841
PGP ID: 0x0EA3D5A2
Does anyone have a sample ruleset for PF for a network that looks like this
A wired internal network that is nat'd to the outside world on one range
(192.168.4.10-20) and another range that is unrouteable and can only go
out through squid/dante (20-50).
A wireless network interface that actua
raid is fake its not actual redundancy its imposed by the man, you are
imagining redundancy because you believe in technology. RAID provides
nothing other than fake ass redundancy that is "enterprise" security
fake ass bullshit because you are all fake ass believers yeh quote that
fake ass shit
3 matches
Mail list logo