Subject: Re: bin/953: login.c changes to sanify S/key use
To: Ty Sarna <email@example.com>
From: Bill Sommerfeld <firstname.lastname@example.org>
Date: 04/12/1995 09:47:10
An IETF working group to standardize S/key is about to form (it met as
a BOF at the Danvers IETF). BTW, the real reason for the S/key ->
OPIE name change (according to Ran Atkinson of NRL) is that Bellcore
has a trademark on S/key, and NRL's lawyers didn't want them to do
anything which looked even remotely like trademark infringement..
They're attempting to come up with consensus on a a standard before
the next IETF (~4 months), so they don't actually have to meet as a
However, they're only working on standardizing the "protocol" /
"interoperability" aspects of S/key, not purely local policy issues
like the ones we're talking about here ("When do we require S/key
vs. when do we allow long-term passwords?"); I see no reason to hold
up the change requested in PR953 for this.