----- Original Message ----- From: "Anton Okmianski (aokmians)" <[EMAIL PROTECTED]> To: "Sam Hartman" <[EMAIL PROTECTED]> Cc: "Chris Lonvick (clonvick)" <[EMAIL PROTECTED]>; "Tom Petch" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, January 17, 2006 10:54 PM Subject: RE: [Syslog] Re: Threat model and charter
Sam: > May I recommend TLS PSK Interesting option. Probably not as mature as just using HMAC message digests. Is there some document which compares and contrasts TLS and SSH? It seems recent RFCs surrounding both have put them on a redundancy path. I'd really like to learn why IETF is pursuing both of those at the same time. > [tp] As I said previously, I think that transport level security is a topic for 2007 and not 2006, but if and when we do go down that route, then I think the choice of which needs careful consideration. SSL, and to some extent TLS, is stated to be the most widely used security system on the Internet but then it is used with that most widely used protocol HTTP, to access (Enterprise) web servers. Look at network operators and a different picture emerges. The survey that was required before isms came into being showed that ssh was the most widely used system; TLS did not figure, appearing less often than Windows Active Directory, while local accounts scored higher than RADIUS/.TACACS+ (this is also the picture I get from looking at network products on websites). This set the direction for isms. Whatever the issues are of distributing security credentials, they have been accommodated, else these systems would not be in use (although I suspect the quality of key management might not meet the standards wanted by the IETF).. So for me the choice should is one of the marketplace. Enterprise web servers and SSL(TLS) is in place and should give good leverage. Network Operators and the answer is SSH. Tom Petch _______________________________________________ Syslog mailing list [email protected] https://www1.ietf.org/mailman/listinfo/syslog
