1995-10-13 - Re: OneTimePasswd (not Pad)

Header Data

From: Adam Shostack <adam@homeport.org>
To: dl@hplyot.obspm.fr (Laurent Demailly)
Message Hash: 49dac3f44ad29a17661c0a1ba69cc9c6ae93421018214a5819918ff1428219ca
Message ID: <199510131429.KAA08941@homeport.org>
Reply To: <9510131250.AA28930@hplyot.obspm.fr>
UTC Datetime: 1995-10-13 14:27:57 UTC
Raw Date: Fri, 13 Oct 95 07:27:57 PDT

Raw message

From: Adam Shostack <adam@homeport.org>
Date: Fri, 13 Oct 95 07:27:57 PDT
To: dl@hplyot.obspm.fr (Laurent Demailly)
Subject: Re: OneTimePasswd (not Pad)
In-Reply-To: <9510131250.AA28930@hplyot.obspm.fr>
Message-ID: <199510131429.KAA08941@homeport.org>
MIME-Version: 1.0
Content-Type: text



| I'm about to implement an OTPasswd (mostly like s/key) scheme to my
| www browsers/clients/proxy, but I was wondering is the mere principle
| of storing H^n(S) and requesting H^(n-1) from peer (H beeing your
| favorite one way strong hash function (MD5), and S your seed+secret
| passwd) could possibly be patented somehow and thus preventing using a
| similar scheme without getting a license (from
| bellcore?),.... if there are any usage conditions/restrictions?,... 

	There is an IETF working group standardizing OTPassword
technology.  not sure how active it still is.
ietf-otp-request@@bellcore.com 

Adam


-- 
"It is seldom that liberty of any kind is lost all at once."
					               -Hume





Thread