[27345] in Kerberos
Re: One Time Identification, a request for comments/testing.
daemon@ATHENA.MIT.EDU (Nicolas Williams)
Thu Feb 1 19:47:59 2007
Resent-From: Nicolas.Williams@sun.com
Resent-To: Sam Hartman <hartmans@mit.edu>, g.w@hurderos.org,
dev@directory.apache.org, kerberos@mit.edu, krbdev@mit.edu,
"Douglas E. Engert" <deengert@anl.gov>
Date: Thu, 1 Feb 2007 17:55:06 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sam Hartman <hartmans@mit.edu>
Message-ID: <20070201235506.GV28618@binky.Central.Sun.COM>
Mail-Followup-To: Sam Hartman <hartmans@MIT.EDU>, g.w@hurderos.org,
dev@directory.apache.org, kerberos@MIT.EDU, krbdev@MIT.EDU,
"Douglas E. Engert" <deengert@anl.gov>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <tslmz3xv3s0.fsf@cz.mit.edu>
Cc: dev@directory.apache.org, "Douglas E. Engert" <deengert@anl.gov>,
krbdev@mit.edu, g.w@hurderos.org, kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Thu, Feb 01, 2007 at 06:47:43PM -0500, Sam Hartman wrote:
> OK, so the requirements you are trying to meet are:
>
> 1) soft token support for flash drives.
>
> 2) Support for central password management.
>
> 3) Allow minimal or no identifying information on the token.
>
> Any more?
4) Interoperability (meaning that you can use the softtoken on any OS).
Which to me means a standard, de facto or otherwise, for the
softtoken format.
Nico
--
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
