Re: new ftp proxy: pftpx

2004-12-17 Thread Tobias Wigand
hi, I've put up the latest version at http://www.sentia.org/downloads/pftpx-0.5.tar.gz many thanks, works great. i´m planning on trying pftpx on our main firewall, as we have some mac users with picky ftp clients and also pasv ftp for everyone would be cool. so it would be really nice if you

pf port knocking

2004-12-17 Thread A
Hey all I am getting tired of seeing the following popping up every day (with various IPs) on my log server. * ROOT FAILURES jasper ssh2(pw) @221.143.156.58(3) * User Failures admin ssh2(pw) jasper(2) andrew ssh2(pw) jasper(1) angel ssh2(pw) jasper(1) barbara ssh2(pw) jasper(1) ben

Re: Re: (why can't)/(does) carp work on bridges ?

2004-12-17 Thread Joel CARNAT
On Thu, Dec 16 2004 - 20:46, Jason Dixon wrote: On Dec 16, 2004, at 10:18 AM, Joel CARNAT wrote: I wanted to do CARPing on interfaces which were part on bridges. According to my readings and testing (it's been 1 week I'm trying to have it working ;), it seems you can't enable carp on an

Re: Re: (why can't)/(does) carp work on bridges ?

2004-12-17 Thread Camiel Dobbelaar
On Fri, 17 Dec 2004, Joel CARNAT wrote: my test is pinging 192.168.10.200 (the carp interface). it's OK until I brconfig bridge0 up. from then, I can see (tcpdump) echo request on bge0 and bge1 but nowhere else (and no ack anywhere). then I brconfig bridge0 down and the ping works back.

Re: Re: (why can't)/(does) carp work on bridges ?

2004-12-17 Thread Camiel Dobbelaar
On Fri, 17 Dec 2004, Joel CARNAT wrote: that's why I'm pretty sure the bug is the bridge (or @least the way I configured it ;)... I thought, maybe, setting the bridge confuses carp because paquets are first forwarded from bge0 to bge1 and as carp0 is linked to bge0, it doesn't work on the

Re: pf port knocking

2004-12-17 Thread jared r r spiegel
For those unfamiliar with the technique, it is like knocking a certain pattern/code on a door to open it. anyone unfamiliar with the technique hasn't read the archives whatsoever and thus is not going to garner favour from anyone here at all. Has anyone heard of anyone working on a

RE: pf port knocking

2004-12-17 Thread Roy Morris
change your ssh port to like 30222 or something .. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of A Sent: December 17, 2004 12:12 AM To: [EMAIL PROTECTED] Subject: pf port knocking Hey all I am getting tired of seeing the following popping

Re: CARP

2004-12-17 Thread Ryan McBride
On Thu, Dec 16, 2004 at 08:54:54PM -0500, Jason Dixon wrote: There is probably a good reason for this, but might be hard to determine a) for an experienced user without access to your network, or b) for an inexperienced user *with* access to your network. ;-) I suggest monitoring your

Re: pf port knocking

2004-12-17 Thread Ed White
On Friday 17 December 2004 15:45, Roy Morris wrote: change your ssh port to like 30222 or something .. That's dumb. Choose a port 1024.

Re: pf port knocking

2004-12-17 Thread Ed White
On Friday 17 December 2004 06:11, A wrote: Further, jasper is the only machine that is externally accessible via SSH (the only other open ports are domain, web and mail on other servers). I need to leave SSH open as a number of people work remotely and tunnel through it to some of the services

Re: CARP

2004-12-17 Thread Jason Dixon
On Dec 17, 2004, at 1:47 PM, Ryan McBride wrote: I suggest larger advskew differences. You can only go as high as the size of your segment (256-1 for /24, for example). If you're only using 2 firewalls, I suggest advskews of 0 and 100. This isn't documented anywhere, and is only based on my own

Re: CARP

2004-12-17 Thread ed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 17 Dec 2004 18:47:47 + Ryan McBride [EMAIL PROTECTED] wrote: $ ifconfig -a $ sysctl net.inet.carp $ netstat -sp carp Thankyou I will provide this with my next post. - -- /-- _| | Regards. Please note, my PGP key ID has changed. |--

Re: pf port knocking

2004-12-17 Thread Peter GILMAN
Ed White [EMAIL PROTECTED] wrote: | On Friday 17 December 2004 15:45, Roy Morris wrote: | change your ssh port to like 30222 or something .. | | That's dumb. why? Choose a port 1024. why?

Re: pf port knocking

2004-12-17 Thread Jason Opperisano
On Fri, 2004-12-17 at 15:51, Peter GILMAN wrote: Ed White [EMAIL PROTECTED] wrote: | On Friday 17 December 2004 15:45, Roy Morris wrote: | change your ssh port to like 30222 or something .. | | That's dumb. why? Choose a port 1024. why? not trying to speak for ed, but

RE: pf port knocking

2004-12-17 Thread Roy Morris
not trying to speak for ed, but IMHO...it's dumb because any yahoo with a local account on a machine can create a listening socket on a port = 1024. Anyone can create a socket above 1024 anyway, regardless .. this has nothing to do with ssh. If you are running a server, full of users with