Den Tue, 19 May 2015 22:53:05 +0100 skrev Re: OATH Toolkit 2.6.0: > On Tue, 2015-05-19 at 23:24 +0200, Simon Josefsson wrote: > > Yeah, an URI approach sounds better. There is a PKCS#11 amendment > > for OTP tokens, not sure if the PKCS#11 URI handles this, or wheter > > it makes any sense though. > > I don't think the PKCS#11 URI covers that even for tokens which really > are in a PKCS#11 device, let alone other things.
So, another kind of URL? otp:hotp-pskc?h=sha1&file=/var/lib/foo/bar4711.pskc otp:totp?h=sha1&key=010203040506070809000A0B0C0D0E0F otp:hotp-ykneo?h=sha1&id='Facebook' otp:stoken?... Just brainstorming, I still don't see exactly how it all would fit together. /Simon
pgpe5TWd1NiNT.pgp
Description: OpenPGP digital signatur
