manual says:
-sfile save configuration to file instead of key. (if file is -, send to stdout)
-ifile read configuration from file. (if file is -, read from stdin)
from this, i thought that the file will contain all information, including:
AES secret key
access code
public identity
private identity
I would like to be able to use this file to personalize my yubikey and few seconds later to use it again to import values into authentication manager DB (i am using ubiserver now) and securely backup it...
While having this file with generic options is sweet, i think having definitive slot description would be even more useful... i would let user to redefine options on commandline, but take defaults from the file.
If we should keep this file only for generic options, it should be better described in manual as such. it definitely creates impression that everything will be saved there. From reading manual, I imagined this to work somewhat like dd or sfdisk does.
manual says: -sfile save configuration to file instead of key. (if file is -, send to stdout) -ifile read configuration from file. (if file is -, read from stdin)
from this, i thought that the file will contain all information, including:
I would like to be able to use this file to personalize my yubikey and few seconds later to use it again to import values into authentication manager DB (i am using ubiserver now) and securely backup it...
While having this file with generic options is sweet, i think having definitive slot description would be even more useful... i would let user to redefine options on commandline, but take defaults from the file. If we should keep this file only for generic options, it should be better described in manual as such. it definitely creates impression that everything will be saved there. From reading manual, I imagined this to work somewhat like dd or sfdisk does.