RE: vtun

I'm not entirely positive, but I'm pretty sure you need to add the 2nd connection under tap1, as only one connection can be on tap0 at a time (in the server vtund.conf). You can also search thru the vtun archives, or do a search on google (vtun tap0 multiple client). HTH, Steven exitus

RE: IPTABLES and WEB

Here is the page I got started at: (may wrap) http://people.unix-fu.org/andreasson/iptables-tutorial/iptables-tutorial .html But in any event, here's the skinny on it: iptables -t nat -A PREROUTING -p TCP -i $INET_IFACE -d $HTTP_IP --dport 80 \ -j DNAT --to-destination $DMZ_HTTP_IP iptables

RE: IPTABLES and WEB

Here is the page I got started at: (may wrap) http://people.unix-fu.org/andreasson/iptables-tutorial/iptables-tutorial .html But in any event, here's the skinny on it: iptables -t nat -A PREROUTING -p TCP -i $INET_IFACE -d $HTTP_IP --dport 80 \ -j DNAT --to-destination $DMZ_HTTP_IP iptables

RE: OpenSSH 3, DEBIAN 2.2 and PAM authentication

This sounds like something I had to help a friend out with this recently. Took me ~15sec to tell him his problem. Configure openssh3 like so: ./configure --with-pam If it whines about the pam headers, pop into dselect and grab 'em, then try it again, compile, install, restart ssh, give a

RE: OpenSSH 3, DEBIAN 2.2 and PAM authentication

This sounds like something I had to help a friend out with this recently. Took me ~15sec to tell him his problem. Configure openssh3 like so: ./configure --with-pam If it whines about the pam headers, pop into dselect and grab 'em, then try it again, compile, install, restart ssh, give a

RE: No local user authentication with openssh2.9

I ran into the same problem a while back. Make sure you 'cp openssh-source/contrib/sshd.pam.generic /etc/pam.d/ssh' (or it may need to be /etc/pam.d/sshd, I forget offhand). Restart sshd and it should work fine. Or if you'd rather use the debian ssh pam file, install openssh1, copy the

RE: No local user authentication with openssh2.9

I ran into the same problem a while back. Make sure you 'cp openssh-source/contrib/sshd.pam.generic /etc/pam.d/ssh' (or it may need to be /etc/pam.d/sshd, I forget offhand). Restart sshd and it should work fine. Or if you'd rather use the debian ssh pam file, install openssh1, copy the

RE: red worm amusement

-Original Message- From: CaT [mailto:[EMAIL PROTECTED] Sent: Sunday, July 22, 2001 1:11 AM To: Jacob Meuser Cc: debian-security@lists.debian.org Subject: Re: red worm amusement quoteNo machine is 100% secure, except those machines that do not exist. Anyone who thinks their box is 100%

RE: iptables install

Someone spammed this out a while back. I just used this a few days ago, worked just fine http://www.debian.org/News/2001/20010415 HTH, Steven Beverly IS Technician - PHX IS Operations EarthLink, Inc. Cell: 602.723.4485 Pager: [EMAIL PROTECTED] I am the Illustrious Postmaster and Grand

RE: Anti Virus for Debian

After ILOVEYOU first came out and AV vendors didn't have a fix for it, we had to figure out a way to quickly disable the virus. So I spent 5min finding the reg key and writing 2 scripts to make the default action Edit, instead of Open, and another in reverse, make the default action Open instead

Disabling Accounts

I have a question about /etc/passwd... I typically go thru and put a * in all accounts except for 'root' and change the shell to '/bin/false' when I first setup a box, to make sure the account cannot be logged into. Is there a specific reason why this is not done? Are there any implications I