Next | Query returned 15 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2005-06-17 05:50:45 by Johnny C. Lam | Files touched by this commit (387)
Log message:
Create directories before installing files into them.
   2004-11-29 01:07:15 by Todd Vierling | Files touched by this commit (2)
Log message:
Update to 0.49a; fix MAINTAINER.  Changelog:

2004-05-29 0.49a

 - numerous portability fixes here and there
 - real event.3 manpage

2004-05-27 0.49

 - autoconf'ified, sort of
 - use advanced event mechanisms (epoll, kqueue, devpoll) when available
 - new option: -i file (or -i -) to read hosts to check from file
 - add timeout for dsbl cookie

2004-02-17 0.46

 - adopted for new DSBL format
 - changed protocol names: http=>http-connect, ftp=>ftp-user
 - do not stop on Content-Type: header seen in HTTP-CONNECT
   responses (what an idiotic software does this?!)
 - removed obsolete 118[0-4] ports (old mimail variants)

2003-08-07 0.45a

 - fixed multihomed proxy detection with new DSBL
   (DSBL now correctly replies with "250 listed [ip.add.re.ss]" instead of
   "220 listed [ip.add.ress]" to the final end-of-message terminator)
   2003-06-11 22:15:15 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 0.45, from Todd Vierling in PR 21859.
2003-05-11 0.45

 - new option -D to not reset default portlist if -p is given
 - new port - 5490 - NONAME/1.4 HTTP CONNECT-only proxy (trojan?)

2003-05-05 0.44

 - added ports 1075 to list of ports for socks and http (MSP proxy)

2003-05-01 0.43

 - determine DSBL-listed IP for DSBL submissions (new DSBL listme@
   server now allows this by printing an IP that was listed on final
   \r\n.\r\n reply line)
 - added some proxy info recognision (proxy-agent - yay!), activate with -x.
 - removed broken HTTP GET support altogether
 - moved HTTP PUT and wingate/telnet to be more "advanced"
 - added port 21 to the list of FTP ports
 - changed connect timeout to be half of -t
 - yet another wingate/telnet prompt ("telnet>")
 - CCProxy Telnet handler
 - write "open" string w/o stdio/buffering
 - fixed error (proxycheck always prints "closed" lines ignoring -n flag)
   2003-04-09 11:12:11 by Thomas Klausner | Files touched by this commit (3)
Log message:
Update to 0.42, provided by Todd Vierling in PR 21068:
2003-02-20 0.42
 - fixed a long-standing bug in dsbl handler - data received from
   the remote was not collected correctly.  Well, this one wasn't
   happened too frequently - I only seen it once, when a proxy
   delivered data from the target mailserver one byte at a time.
 - added yet another port, 1813 (socks5), as advanced (level2) port.
   SKK proxy listens here, but it is seen unfrequently.
2003-02-14 0.42b2
 - added proxylogger - receiving part of proxycheck, to be used
   from inetd and with -c chat.
2003-02-12 0.42b1
 - fixed a small bug in last wingate/telnet code changes (mostly
   cosmetic: "Resource temporarily unavailable" vs "Connection \ 
timed out").
 - added another telnet/wingate proxy variant, with a prompt
   "SpoonProxy>", which expects a command in form "host port"
   (instead of tn-wg/wingate which is of the form "host:port").
2003-02-04 0.42b
 - some code cleanups/changes: may break things, testing...
 - FTP proxy detection added, port 1183 only for now.  Interesting
   to experiment with M$ ftp servers ;)
 - fixed not finding advanced protocol if no ports are specified
   (e.g. -pwg: tried default protos:ports instead of wg:25,1181)
 - modified telnet/wingate proxy code to be a bit faster and to
   know which command to sent to a particular proxy.
   2003-02-17 12:50:43 by Tomasz Luchowski | Files touched by this commit (5) | Imported package
Log message:
Initial import of net/proxycheck (version 0.41)

proxycheck is a simple tool that will work on a reasonable *nix system
and may be used to quickly check whenever a given host or set of hosts
has open proxy server running.

Open proxies of various kinds are (ab)used nowadays for various evil
things like sending mass spam, hacking into your machine, making denial
of service attacks (DoS) and the like. Every such machine should be
either secured properly or turned off permanently, but that's not an
option, since in most cases there is either no administrator of such
machines exists at all, or he has no clue about what's on that machine,
or it's irrelevant for him.

Provided by Todd Vierling in PR#20110.


Next | Query returned 15 messages, browsing 11 to 20 | previous