Tod Beardsley ab3b173040 So, funny story with net-ssh. Turns out, there's insufficient housekeeping on closing out connections in the event of authentication failures, which means you can start sucking up connections pretty good when you fail authentication a whole bunch of times. Fixed in the library, so now, if you pass a block to Net::SSH.start, and the authentication fails, the connection will still close out correctly, just as it would when the authentication succeeds. ... Protip: If you don't pass a block, it's *still on the caller* to deal with the connection somehow. You'll want to basically always assign the connection to someplace you control, like so: sock = Net::SSH.start(whatever); sock.close). Otherwise, if you just Net::SSH.start without a block /or/ without assignment, you'll be stuck with all these useless connections hanging around. git-svn-id: file:///home/svn/framework3/trunk@8556 4d416f70-5f16-0410-b530-b9f4589650da		2010-02-19 03:02:25 +00:00
..
dns	See #434. Some libraries used the wrong exception class	2009-11-02 18:20:02 +00:00
ssh	See #842. Convering TCPSocket calls to Rex::Socket::Tcp calls.	2010-02-16 22:49:27 +00:00
dns.rb	Code cleanups	2008-10-19 21:03:39 +00:00
ssh.rb	So, funny story with net-ssh. Turns out, there's insufficient housekeeping on closing out connections in the event of authentication failures, which means you can start sucking up connections pretty good when you fail authentication a whole bunch of times. Fixed in the library, so now, if you pass a block to Net::SSH.start, and the authentication fails, the connection will still close out correctly, just as it would when the authentication succeeds.	2010-02-19 03:02:25 +00:00
ssh.rb.ut.rb	See #842. Convering TCPSocket calls to Rex::Socket::Tcp calls.	2010-02-16 22:49:27 +00:00