openbsd-ports/net/ftpsesame/distinfo

MD5 (ftpsesame-0.95.tar.gz) = 358UP2YV2vZzaePjxET2Lg==
RMD160 (ftpsesame-0.95.tar.gz) = 01D5TaAIBzFSO3LTRmAyQKbftzo=
SHA1 (ftpsesame-0.95.tar.gz) = yPv4MJxqVnpdSDeQLkIZ4bJmvAQ=
SHA256 (ftpsesame-0.95.tar.gz) = nOSGWQyvQirPNiDfsVpXfSCyxebVVNnybWch1HLAu7c=
SIZE (ftpsesame-0.95.tar.gz) = 10974
base64 checksums. 2007-04-05 12:19:55 -04:00			`MD5 (ftpsesame-0.95.tar.gz) = 358UP2YV2vZzaePjxET2Lg==`
			`RMD160 (ftpsesame-0.95.tar.gz) = 01D5TaAIBzFSO3LTRmAyQKbftzo=`
			`SHA1 (ftpsesame-0.95.tar.gz) = yPv4MJxqVnpdSDeQLkIZ4bJmvAQ=`
			`SHA256 (ftpsesame-0.95.tar.gz) = nOSGWQyvQirPNiDfsVpXfSCyxebVVNnybWch1HLAu7c=`
Initial import of ftpsesame 0.95 ftpsesame helps the FTP protocol get through your pf firewall. It does this by passively analysing FTP control connections and adding rules into a pf anchor when an FTP data connection is about to commence. You might want to try ftpsesame instead of ftp-proxy(8) from the OpenBSD base system for the following reasons: - it runs on "transparent" (no IP address) bridges - you need packetfilter performance on all data connections - you have to handle lots of simultaneous sessions - you do not want to redirect any traffic to the firewall itself: for IP accounting or other reasons 2005-07-30 11:45:30 -04:00			`SIZE (ftpsesame-0.95.tar.gz) = 10974`