Re: is manual keying mandatory

Michael Richardson <mcr@sandelman.ottawa.on.ca> Mon, 23 March 1998 19:50 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id OAA25315 for ipsec-outgoing; Mon, 23 Mar 1998 14:50:18 -0500 (EST)
Message-Id: <199803232007.PAA00766@morden.sandelman.ottawa.on.ca>
To: ipsec@tis.com
Subject: Re: is manual keying mandatory
In-reply-to: Your message of "Mon, 23 Mar 1998 11:39:03 PST." <2.2.32.19980323193903.006e5768@trix.cisco.com>
Date: Mon, 23 Mar 1998 15:07:28 -0500
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

>>>>> "Steve" == Steve Sneddon <sned@cisco.com> writes:
    Steve> not rehash *that* issue again ;=)). And I think there's a
    Steve> very cogent case to be made that manual keying can't "work"
    Steve> (in a commercial sense of being scalable, supportable,
    Steve> security-risk-free, etc.) in everyday use on 10's of

  I'm sorry, but the spec doesn't say that manual keying has to be any
of these things. It simply must exist. 

  Like I said: you can burry your manual keying interface behind
a tty based command line interface that speaks only EBCDIC if you
want, and is available only on Thursdays with full moons.  So long as
someone who arrives at a certification lab has a EBCDIC terminal with
them, it won't matter.

  Just because it is in the spec doesn't mean you have to have it in
your GUI.

]     Network Security Consulting and Contract Programming      |  SSH IPsec  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |international[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |strong crypto[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [