On Tue, 2015-05-19 at 13:58 +0200, Simon Josefsson wrote: > Long time, no release! I'm kicking off working on oath-toolkit with > this release to fix some minor issues.
Welcome back :) > Now is a good time to ping me about anything I have neglected to do > wrt oath-toolkit. How about making it easier to use for clients. I would love to have a function which I can simply pass the *filename* of a PSKC file, and have it just give me a token code. Updating the file as necessary, with some reasonable locking and power-fail-safety, if it's a HOTP token. As it is, there isn't even a simple way to use libpskc and liboath together, and even read the PSKC file and generate a token. Somewhat more out of scope, but it would also be *really* neat to be able to import tokens from other things, like the Java monstrosity that is McAfee Pledge :) -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
