Re: [gentoo-user] Module philosophy: Compile-in or Load

2006-06-17 Thread Erik Westenbroek
I like compile-in, generally less work must be done (just a hair, but it is less) On 6/17/06, Mick <[EMAIL PROTECTED]> wrote: On 17/06/06, Anthony E. Caudel <[EMAIL PROTECTED]> wrote: > Mick wrote: > > On 13/06/06, Ryan Tandy <[EMAIL PROTECTED]> wrote: > >> Anthony E. Caudel wrote: > >> > > >> >

[gentoo-user] Re: Postfix Woes

2006-04-25 Thread Erik Westenbroek
NO!!! I HAVE SBC!!! AND IT HANGS! I guess I will just have to gateway through my isp. Thanks for the help. On 4/25/06, John Jolet <[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 8:47 PM, "Erik Westenbroek" <[EMAIL PROTECTED]> wrote: > > > no, I have a g

[gentoo-user] Re: Postfix Woes

2006-04-25 Thread Erik Westenbroek
<[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 8:28 PM, "Erik Westenbroek" <[EMAIL PROTECTED]> wrote: > > >> From both localhost and my SDF account I get the expected 220 > > casusbelli.homelinux.org ESMTP Postfix. I haven't emerged iptables

[gentoo-user] Re: Postfix Woes

2006-04-25 Thread Erik Westenbroek
<[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 7:48 PM, "Erik Westenbroek" <[EMAIL PROTECTED]> wrote: > > > Not at all. I wanted to actually get the server up before I got that set > up. > > > > On 4/25/06, John Jolet <[EMAIL PROTEC

Re: [gentoo-user] Postfix Woes

2006-04-25 Thread Erik Westenbroek
Not at all. I wanted to actually get the server up before I got that set up. On 4/25/06, John Jolet <[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 7:16 PM, "Erik Westenbroek" <[EMAIL PROTECTED]> wrote: > > > Yeah, I have syslog-ng running. > > H

Re: [gentoo-user] Postfix Woes

2006-04-25 Thread Erik Westenbroek
ferred (connect to smtp.freeshell.org[192.94.73.18]: Connection timed out) On 4/25/06, John Jolet <[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 6:40 PM, "Erik Westenbroek" <[EMAIL PROTECTED]> wrote: > > > #netstat -an|grep 25 > > tcp0 0

Re: [gentoo-user] Postfix Woes

2006-04-25 Thread Erik Westenbroek
#netstat -an|grep 25 tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN unix 3 [ ] STREAM CONNECTED 109125 On 4/25/06, John Jolet <[EMAIL PROTECTED]> wrote: > > > > On 4/25/06 6:22 PM, "Erik Westenbroek" <[EMAIL PR

[gentoo-user] Postfix Woes

2006-04-25 Thread Erik Westenbroek
I have a postfix mailserver setup on my system that uses pam for authentication. I can recieve email just fine, but whenever I try to send mail, my logs say that the connection to the server timed out on port 25. Does anyone have an idea as to what the problem is? -- Erik -- gentoo-user@gentoo.

Re: [gentoo-user] Install help

2006-04-20 Thread Erik Westenbroek
In /etc/rc.conf: Uncomment #DISPLAYMANAGER="xdm" (you do this by removing the # in case you didn't know) If you are using Gnome, change xdm to gdm, and to kdm if you are using kde. Then, do "rc-update add xdm default" and it should start up at boot. On 4/20/06, Farhan Ahmed <[EMAIL PROTECTED]> wro

Re: [gentoo-user] addusr (gentoo v. fedora)

2006-03-21 Thread Erik Westenbroek
or, we can just do it the easy way: useradd -d /home/user_name user_name. On 3/21/06, Nick Rout <[EMAIL PROTECTED]> wrote: > > On Tue, 21 Mar 2006 20:32:42 + > THUFIR HAWAT wrote: > > > On 3/21/06, John Jolet <[EMAIL PROTECTED]> wrote: > > .. > > > if you add the -m argument to useradd, it wi

[gentoo-user] Re: Iptables Tarpit

2006-03-08 Thread Erik Westenbroek
thank you to all. I now have tarpits up and running smoothly. On 3/8/06, Andrew Frink <[EMAIL PROTECTED]> wrote: > You could also just add the "extensions" USE flag to iptables and that > should give you tarpit support > > On 3/7/06, Dave Jones <[EMAIL

Re: [gentoo-user] Iptables Tarpit

2006-03-07 Thread Erik Westenbroek
I guess TARPIT is not in the default installation of iptables, Ill just use labrea. On 3/6/06, Ryan Tandy <[EMAIL PROTECTED]> wrote: > Erik Westenbroek wrote: > > iptables: No chain/target/match by that name > I don't see a chain or other target named TARPIT - it's n

[gentoo-user] Iptables Tarpit

2006-03-06 Thread Erik Westenbroek
hello I am attempting create a tarpit to protect against SSH Brute force attempts. I tried this: iptables -N SSH_Brute_Force iptables -A INPUT -p tcp --dport 22 -m state --state NEW -j SSH_Brute_Force iptables -A SSH_Brute_Force -s 192.168.1.254 -j RETURN iptables -A SSH_Brute_Force -m recent --n