A fifteen year old TCP bug?
In 2002 we did custom patch for an energy company which had hundreds of outdated remote RS232 terminals hooked up via wireless links to the central station for control and monitoring. Their goal was to encrypt transmitted messages so it will not be intercepted and messed with during wireless transmission. Solution was Linux boxes on both sides that encrypts communication using OpenSSL...
The problem was the terminal do not want to talk to Linux over crossover Ethernet because of.... you guessed...  bug in TCP... To solve that we had to make patch for Linux kernel. and let me tell you that code in 2.4 kernel was very ugly with extremely funny comments :-)My companion since than developing drivers and "he feels that he is doing something important rather than boring UI".but all he is doing is mostly his own projects and drivers since updating open source IS a pain in the neck.I guess problem in collaborative work is the reason why people do open source vs something that have to be supported. What do you think?