[lwip-users] [lwip] Modifying LwIP for secure ISNs

[Paul Sheer]

I have already posted new ISN code that replaces
the function tcp_next_iss()

Howeverk the function call now needs to be relocated
to where the connection gets made or accepted, so that
the remote host IP and port can be passed as arguments:
tcp_next_iss(sport, dport, my_ip, remote_ip)

Anyone up to this work?

Once this is done, we can plug in a number of
tcp_next_iss() build options: a minimal one, a
small secure one, and a fast secure one.

The minimal one will work as is, the small one
will use discrete logs, and the fast one will
use DES/MD?/?.

-paul

Paul Sheer Consulting IT Services . . Tel . . . +27 (0)21 6869634
Email . . . address@hidden . . . . . . Pager . . . 088 0057245
Linux development, cryptography, recruitment,  support,  training
http://www.icon.co.za/~psheer . . . . http://rute.sourceforge.net
L I N U X . . . . . . . . . . . .  The Choice of a GNU Generation

[This message was sent through the lwip discussion list.]