FYI this patch was created by Mark Ellzey Thomas, who has published it to GitHub. Ask him nicely and I'm sure he'd provide a new patch. :)<div><br></div><div><a href="https://github.com/ellzey/tac_plus_AFL">https://github.com/ellzey/tac_plus_AFL</a></div>
<div><br></div><div>jathan.<br><br><div class="gmail_quote">On Tue, Jan 10, 2012 at 1:52 PM, Joe Moore <span dir="ltr"><<a href="mailto:joe.moore@holidaycompanies.com">joe.moore@holidaycompanies.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have been happily running tac_plus F4.0.4.19 with the Auth Fail Lock patch for some time, on a pair of FreeBSD 7.x servers.<br>
<br>
Upon upgrading one of those servers to FreeBSD 8.x, tac_plus stopped recognizing the "auth-fail-lock 4 120 600" parameter in my config file and refused to start.<br>
<br>
Fresh builds of 4.0.4.19 (with the AFL patch) on a fresh FreeBSD 8.2 install also failed to start for the same reason.<br>
<br>
Is the AFL feature now implemented differently, or am I going to have to switch to Linux to make this work? Going without AFL is not an option since I have to prove to a security auditor that we don't allow unlimited login attempts to routers etc...<br>
<br>
...jgm<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.shrubbery.net/pipermail/tac_plus/attachments/20120110/793e15bd/attachment.html" target="_blank">http://www.shrubbery.net/pipermail/tac_plus/attachments/20120110/793e15bd/attachment.html</a>><br>
_______________________________________________<br>
tac_plus mailing list<br>
<a href="mailto:tac_plus@shrubbery.net">tac_plus@shrubbery.net</a><br>
<a href="http://www.shrubbery.net/mailman/listinfo.cgi/tac_plus" target="_blank">http://www.shrubbery.net/mailman/listinfo.cgi/tac_plus</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Jathan.<br>--<br>
</div>