Hi, ALL
This is regarding to TCP-MD5 option [RFC2385]. In current
implementation, only one md5 password is saved in the kernel and it
brings in the problem for changing key: Changing key in the middle of
tcp session will break the session unless new md5 password is updated
at both ends at the same time (there is no window for key change).
Does anybody know any patches currently exist to address this issue? I
know rfc4808 is targeting to solve this issue. Does there any plan to
implement rfc4808 for linux?
Best Regards!
Shawn Lu
Xiaochun Lu wrote:
> know rfc4808 is targeting to solve this issue. Does there any plan to
> implement rfc4808 for linux?
>
There's a replacement effort at:
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-auth-opt-08.txt
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-ao-crypto-01.txt
Probably going another round with them before writing code for Linux.