Hi Jim Jim Ford wrote: > In the Shorewall FAQs, there's and interesting writeup regarding using > Portsentry with Shorewall: > > (FAQ 4c) How do I use Shorewall with PortSentry? > Here's a writeup > <http://www.shorewall.net/pub/shorewall/contrib/PortsentryHOWTO.txt> on > a nice integration of Shorewall and PortSentry > > The problem is that it uses the 'at' command, which we don't have. > I guess that a work around could be devised using 'cron' (not sure how, > though), but does anyone have any other ideas, please?
I guess it would not be that difficult to implement at. I have no grasp of the possible security implications though. One way to achieve the same goal with cron might be to write a file, a poor man's database, which is read at regular intervals. This file would contain the blocking information and a timestamp when the block should be released. Pretty basic scripting I would guess. In case of a reboot all the blocks as well as the file would be gone anyway. cheers Erich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
