Yubico Forum

...visit our web-store at store.yubico.com
It is currently Tue Jan 30, 2018 8:33 pm

All times are UTC + 1 hour




Post new topic Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Wed Sep 23, 2015 8:55 pm 
Offline

Joined: Wed Sep 23, 2015 7:24 pm
Posts: 2
Hello everyone,

I just got my Yubikey NEO and I want to use it as a GPG smartcard. My GPG private key is already generated, when I want to import it, I get an error (Translated from French) :

Code:
gpg: KEYTOCARD failed : Unknown IPC command

My system is Ubuntu 15.04, GnuPG 2.1.6
I'm using standard procedure, as intructed here. I guess it may be usefull to tell you that the first command does return what is expected and that I've change my key to mode 82 :

Code:
>>> ykpersonalize -m82
Firmware version 3.4.3 Touch level 1551 Program sequence 3

The USB mode will be set to: 0x82

Commit? (y/n) [n]: y

>>> gpg-connect-agent --hex "scd apdu 00 f1 00 00" /bye
 D[0000]  01 00 10 90 00                                     .....
 OK

Here is what I get from gpg2 :

Code:
>>> gpg2 --version
gpg (GnuPG) 2.1.6
libgcrypt 1.6.3
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Algorithmes pris en charge :
Clef publique : RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Chiffrement : IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
              TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256
Hachage : SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression : Non compressé

>>> gpg2 --edit-key F646F813
gpg (GnuPG) 2.1.6; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

La clef secrète est disponible.

pub  rsa4096/F646F813
     créé : 2015-06-07  expire : 2018-06-06  utilisation : C   
     confiance : ultime        validité : ultime
sub  rsa2048/8CDA097E
     créé : 2015-06-07  expire : 2018-06-06  utilisation : S   
sub  rsa2048/77A93788
     créé : 2015-06-07  expire : 2018-06-06  utilisation : E   
sub  rsa2048/8E427FB0
     créé : 2015-06-07  expire : 2018-06-06  utilisation : A   
[  ultime ] (1). XXXXXX <XXXX@XXXX.XXX>

gpg> toggle
           
pub  rsa4096/F646F813
     créé : 2015-06-07  expire : 2018-06-06  utilisation : C   
     confiance : ultime        validité : ultime
sub  rsa2048/8CDA097E
     créé : 2015-06-07  expire : 2018-06-06  utilisation : S   
sub  rsa2048/77A93788
     créé : 2015-06-07  expire : 2018-06-06  utilisation : E   
sub  rsa2048/8E427FB0
     créé : 2015-06-07  expire : 2018-06-06  utilisation : A   
[  ultime ] (1). XXXXXX <XXXX@XXXX.XXX>

gpg> key 1
         
pub  rsa4096/F646F813
     créé : 2015-06-07  expire : 2018-06-06  utilisation : C   
     confiance : ultime        validité : ultime
sub* rsa2048/8CDA097E
     créé : 2015-06-07  expire : 2018-06-06  utilisation : S   
sub  rsa2048/77A93788
     créé : 2015-06-07  expire : 2018-06-06  utilisation : E   
sub  rsa2048/8E427FB0
     créé : 2015-06-07  expire : 2018-06-06  utilisation : A   
[  ultime ] (1). XXXXXX <XXXX@XXXX.XXX>

gpg> keytocard   
Veuillez sélectionner l'endroit où stocker la clef :
   (1) Clef de signature
   (3) Clef d'authentification
Quel est votre choix ? 1
gpg: échec de KEYTOCARD : Commande IPC inconnue

I don't know what this IPC Command mean, nor where it comes from. I'm not sure it's a Yubikey failure, this may be related to GnuPG, or my system...

Thank you a lot for helping me !


Last edited by TiiXel on Wed Sep 23, 2015 9:37 pm, edited 1 time in total.

Top
 Profile  
Reply with quote  

Share On:

Share on Facebook FacebookShare on Twitter TwitterShare on Tumblr TumblrShare on Google+ Google+

PostPosted: Wed Sep 23, 2015 9:36 pm 
Offline

Joined: Wed Sep 23, 2015 7:24 pm
Posts: 2
Ok, problem solved ! Of course I googled again after posting and I found similar error, leading me to solution.

If anyone needs this, this is what I had to do :

Acording to this bug report the problem is due to incompatibility between the gpg-agent being used, and the gpg2 version.

I did not update my gpg-agent as it was already up to date, but, I changed the way it's run when my session starts : I switched from this configuration to this one. The former was, indeed, meant for an older version.

This is how I solved !


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 15 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group