David Woodhouse <[email protected]> writes: > On Tue, 2015-05-19 at 23:06 +0200, Simon Josefsson wrote: >> >> Thanks. So how would an ideal API look like? Does this make sense: >> >> otp_global_init (int flags); >> otp_global_deinit (void); >> otp_generate_oath_from_pskc (const char *pskcfilename, char **otp); >> otp_generate_oath_from_ykneo (const char *accountid, char **otp); >> otp_generate_stoken (const char *stokendatabase, char **otp); >> >> Or should the interface be cut at some other abstraction level? > > Perhaps a URI of some form? Some of these already exist for stoken.
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. /Simon
signature.asc
Description: PGP signature
