> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of pichi > Sent: Wednesday, 19 September 2007 12:52 AM > To: misc@openbsd.org > Subject: Re: Define hosts lookup for pf.conf > > The Socket module should also be there: > > $ perl -e 'use strict; use Socket; print("hello\n");' > hello
Please try to keep track of who said what.. The above came from a post by Richard Toohey [EMAIL PROTECTED] > but it looks like I dont have the socket module becuase when I do: > > $perl -e > > I get: > > $No code specified for -e. This is answered in another post.. Pedro, You probably won't get too much more hand-holding here. You really should have a good look at the tools available to you before you post to this list. "man" is your friend, google is your library index. > How can I add that module, and again, is it safe for a publically > accessable firewall? I'm a bit worried about this term "publicly accessible firewall", it's a contradiction in terms. Firewalls should be nearly invisible, certainly not public ally accessible. Perl and the enormous number of modules available for Perl are tools that can be used on firewalls for administration and although "bare bones" is a good way to build a firewall (from general principles), you do need certain tools to manage it. Perl is one tool that I would miss greatly if it were removed. Perl does not listen on the network so it cannot be attacked directly. Any risk is related to the ability of an attacker to use Perl to their advantage after they have already compromised your firewall. If they own your firewall, all bets are off and the lack of Perl is unlikely to even slow them down. Again, IMHO, there is no risk to installing Perl and any modules you require on a firewall. Having said that, it's good that you are cautious :-) ciao dave --- Dave Edwards
