OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Anton Rager (a_ragerYAHOO.COM)
Date: Wed Feb 28 2001 - 15:09:40 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    --- *Hobbit* <hobbitAVIAN.ORG> wrote:
    > Looks like Netscreen has a similar issue, but it's
    > documented. One must
    > use the "pre-g2-des-md5" proposal to talk to version
    > 1.6 of their
    > software. 2.x accepts 3des.
    >
    > Earlier versions of the IPSEC standards required
    > single-DES at a minimum,
    > so it's not surprising that holdovers of this sort
    > exist in any product.

    AFAIK ICSA certification and IPSec RFCs require IKE
    implementations to support Diffie-Helman 768MODP and
    DES encryption with MD5 HMAC. [someone point me to the
    updated RFCs if this is not the case] This requirement
    means that all implementations should support this
    along with any other options available. Keep in mind
    that an implementation must default to something, and
    frequently the lowest common denominator is DH
    768MODP/DES/MD5. Unlike ESP SAs, IKE/ISAKMP SA
    negotiation can only propose one set of
    methods/transforms for the IKE SA, so implementations
    normally default to group 1 DH and DES....except
    FreeS/WAN which has dropped group 1 DH and DES ;)

    > Would it be worth collecting a public list of "IKE
    > to watch out for"?
    >
    > _H*

    I would expect all vendors to default to group 1
    DH/DES/MD5.....A better list would be a comprehensive
    summary of additional IKE methods and transforms
    supported, as well as additional ESP methods and
    transforms supported by different vendors.

    Anton Rager

    __________________________________________________
    Do You Yahoo!?
    Get email at your own domain with Yahoo! Mail.
    http://personal.mail.yahoo.com/