Hi, all,


On 4/23/2011 10:17 PM, Christopher Morrow wrote:
...
If the issue is the lack of a TCP-AO implementation in Linux and FreeBSD, it
would be more productive to find the resources (6 man-months approx.) to
just write this than even to discuss it on this list at length further.

I don't think we've got folks yet volunteering to do this... though
it'd be nice :)

FWIW, I'm working on arranging this now.

If you do insist on including other alternatives, I would strongly suggest
listing only IPsec; if you do include ssh (or, AFAICT, if you really want to
get to servers, why not tls? surely servers are as likely if not more so to
have HTTPS support) then you should note the lack of protection to the
transport layer, and any implications that result.

it's not clear to me that https client support exists in routers,
there are also some issues with cert validation to think about (I
think, though maybe that's a simple problem where the cert only
validates up a chain for your as-level-cert? no other CA's
accepted...).

This brings up a useful question - what is the security model? CAs, self-signed certs, or just preshared keys?

The latter is very easy to support in TCP MD5 and will be similarly simple in TCP-AO, but doesn't seem to be the common mode for SSH (you'd need preshared keys without passwords, and that's not as commonly used, AFAICT).

Joe
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to