> The same happens with OpenSC. People are going to use OpenSSH or VPN X/Y > and they need to know which public keys they are going to use, quickly. > Thinking they can access OpenSC documentation and get education is not > the right way to analyse the problem.
AFAIK: OpenSSH and lots of other applications are using PKCS#11 API. So, why not using pkcs11-tool for that task? pkcs11-tool -O pkcs11-tool --id a59f --type pubkey --read-object | base64 Regards Andre _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
