A fifteen year old TCP bug?
blogmal.42.org
A fifteen year old TCP bug?
1–10 of 61 posts
Re: A fifteen year old TCP bug?
#2Re: A fifteen year old TCP bug?
#3This is true hacking news! Discusses a possible new bug in TCP, teaches how TCP works, has links to useful and relevant books on the subject, AND includes remarks about how difficult it is for a newbie to actually make changes to open source software and not get yelled at. I love it!
Re: A fifteen year old TCP bug?
#4Re: A fifteen year old TCP bug?
#5http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committe...
Edit: edited for clarity. Thanks, pinko!
Re: A fifteen year old TCP bug?
#6This is true hacking news! Discusses a possible new bug in TCP, teaches how TCP works, has links to useful and relevant books on the subject, AND includes remarks about how difficult it is for a newbie to actually make changes to open source software and not get yelled at. I love it!
Re: A fifteen year old TCP bug?
#7Re: A fifteen year old TCP bug?
#8Re: A fifteen year old TCP bug?
#9Re: A fifteen year old TCP bug?
#10So much of this is caused by unsigned types. They are evil; avoid them wherever you can.