Easy way to reproduce:

nc -l -p 1230
Then add 127.0.0.1 +6667 as an IRC server (important: ssl!) and see it eat all
the CPU time. I'm not yet 100% sure what exactly happens, but it's definitely
waiting for the SSL handshake to finish.

@Michael: Why are you connecting to a broken SSL server with three users? :p

Cheers,
Uli
-- 
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to