Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Security Encryption

Security Top Concern for New IETF Chair 54

BobB writes "New IETF chair Russ Housley speaks out about bolting security on after the fact, the prospects for IPv6 and a new security technology called Hokey that could help safeguard wireless and wired networks."
This discussion has been archived. No new comments can be posted.

Security Top Concern for New IETF Chair

Comments Filter:
  • Re:Huh? (Score:3, Informative)

    by TheRaven64 ( 641858 ) on Saturday July 28, 2007 @11:57AM (#20023559) Journal

    the fact you can't use named based virtual hosts if you do.
    By the way, there is an RFC describing a STARTTLS-like extension for HTTP. You first connect, then you specify the hostname of the server you want, and complete the TLS handshake. This is the same system used for XMPP, SMTP, and IMAP for virtual hosts.
  • Re:Huh? (Score:4, Informative)

    by Zeinfeld ( 263942 ) on Saturday July 28, 2007 @08:58PM (#20027809) Homepage
    Actually he *is* talking about HTTPS, TLS is the successor to SSL it came about because the MD5 & SHA-1 algorithms have been "technically" compromised.

    TLS is the successor to SSL but that is not the reason that the spec came about. The MD5 compromise came after the work was already started.

    The work started when Microsoft sumbitted their Transport Layer Security protocol to the IETF as a standards proposal. Up to that point Netscape had attempted to keep SSL as a proprietary specification under their control. Which was not too popular with those of us who had broken SSL 1.0 without any difficulty and then been completely ignored in the design of SSL 2.0, which was also botched.

    Sometime after the group began to start up Netscape came out with SSL 3.0 which had been extensively reworked by Paul Kocher and Netscape offered to release change control to the IETF. Microsoft agreed since that is all they had actually wanted all along. The only thing that was really changed in the end was the name and the ciphersuite options.

    BTW its not surprising that Russ thinks security is the major challenge, he was until recently the security area director. Before that he was chair of the S/MIME working group.

  • IPv6 and IPsec (Score:3, Informative)

    by Skapare ( 16644 ) on Saturday July 28, 2007 @09:03PM (#20027835) Homepage

    IPsec works over IPv4. IPv4 works without IPsec. I haven't found anyone (yet) that has gotten IPsec over IPv6 (I'm not talking about IPv6 tunneled over IPsec protected IPv4) to actually work on Linux or BSD. Surely someone has. But Google turns up a number of reports of problems that go unresolved and unanswered (except in one case people reporting they also cannot get it to work). I've only been spending a couple weeks trying to get it to at least establish a security association between 2 machines.

    Which protocol to scrap and start over? Or is it just bad implementation? If we can at least get this working, IPv6 might be considered ready to go.

"Experience has proved that some people indeed know everything." -- Russell Baker

Working...