Bug#751133: crash on startup

2014-09-15 Thread Simon Josefsson
Hi again -- I released 0.1.6 that changes the name of the project as
discussed below.  Just FYI.

/Simon

fre 2014-09-12 klockan 21:09 +0200 skrev Simon Josefsson:
 tis 2014-06-17 klockan 17:00 +0200 skrev Werner Heuser:
  Hello,
  
  you can close this, because it was my fault not to understand
  the man page.
 
 Thanks for confirming -- closing.
 
  When you ask me for improvements, I suggest renaming the tool:
 
  First instead of an abbrevation yk use yubico. This way the
  tool shows up when doing a 'aptitude search yubico'.
 
 Thanks for feedback.  I think it is too painful to rename the project
 though.  Btw, 'apt-cache show yubico' shows it since 'yubico' is part of
 the short package description.
 
  Second neomgr suggest this is a tool to completely manage
  the Yubico neo, but the tool manages only certain parts. You
  need e.g. key-personalization-gui for other usages.
 
 Yeah, it should probably have been called YubiKey NEO CCID Manager
 instead, since the scope of the project is the CCID-part of the NEO.
 We've been thinking about this, maybe we really should rename it to
 reduce confusion.
 
 /Simon
 
  
  Best regards,
  
  Werner
  
  On Tue, Jun 17, 2014 at 01:53:40PM +0200, Simon Josefsson wrote:
   I'm inclined to close this as I couldn't identify any unintended
   behaviour.  Let me know if you have any more questions, or if you can
   think of documentation improvements that would be of help.
   
   /Simon
   
   You wrote:
   
Hi,

Your NEO is in the OTP-only mode, so it is not a smartcard at all.
You need to put the NEO in OTP/CCID or CCID-only mode, see at the
bottom of the man page:

TROBLESHOOTING
   The  error  No  device found can be because a number of
reasons.  The simplest, of course, is that the device really is not
connected to  the machine (USB or NFC).  Another reason may be that
it is in a mode where ykneomgr cannot talk to it.  This can happen
if the device is in OTP??? only mode (mode 0), where you must use the
ykpersonalize tool to mode switch it from the OTP???only mode.  It
can also happen if the device  is in  a  MODE_FLAG_EJECT mode (i.e.,
81 or 82).  If that is the case, you must touch the button in order
to insert the virtual smartcard before you can invoke ykneomgr.

So run 'ykpersonalize -m82' or similar to change it from OTP-only
mode.

/Simon

You wrote:

 Hello,
 
 the Yubikey neo doesn't seem to be detected:
 
 #pcsc_scan
 PC/SC device scanner
 V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
 Compiled with PC/SC lite version: 1.8.10
 Using reader plug'n play mechanism
 Scanning present readers...
 Waiting for the first reader...
 
 This message stays forever-
 
 Though 'dmesg' says:
 
 [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49
 [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50
 using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found,
 idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB
 device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202]
 usb 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3:
 Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP
 as 
 /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24
 [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB
 HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on
 usb-:00:1d.7-6.3.3/input0
 
 I am using stock Debian testing with libccid 1.4.16-1 package with
 running pcscd on a i386 machine.
 
   Best regards,
 
   Werner
 
  
 



signature.asc
Description: This is a digitally signed message part


Bug#751133: crash on startup

2014-06-17 Thread Simon Josefsson
I'm inclined to close this as I couldn't identify any unintended
behaviour.  Let me know if you have any more questions, or if you can
think of documentation improvements that would be of help.

/Simon

You wrote:

 Hi,
 
 Your NEO is in the OTP-only mode, so it is not a smartcard at all.
 You need to put the NEO in OTP/CCID or CCID-only mode, see at the
 bottom of the man page:
 
 TROBLESHOOTING
The  error  No  device found can be because a number of
 reasons.  The simplest, of course, is that the device really is not
 connected to  the machine (USB or NFC).  Another reason may be that
 it is in a mode where ykneomgr cannot talk to it.  This can happen
 if the device is in OTP‐ only mode (mode 0), where you must use the
 ykpersonalize tool to mode switch it from the OTP‐only mode.  It
 can also happen if the device  is in  a  MODE_FLAG_EJECT mode (i.e.,
 81 or 82).  If that is the case, you must touch the button in order
 to insert the virtual smartcard before you can invoke ykneomgr.
 
 So run 'ykpersonalize -m82' or similar to change it from OTP-only
 mode.
 
 /Simon
 
 You wrote:
 
  Hello,
  
  the Yubikey neo doesn't seem to be detected:
  
  #pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...
  
  This message stays forever-
  
  Though 'dmesg' says:
  
  [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49
  [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50
  using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found,
  idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB
  device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202]
  usb 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3:
  Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP
  as 
  /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24
  [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB
  HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on
  usb-:00:1d.7-6.3.3/input0
  
  I am using stock Debian testing with libccid 1.4.16-1 package with
  running pcscd on a i386 machine.
  
  Best regards,
  
  Werner
  


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-17 Thread Werner Heuser
Hello,

you can close this, because it was my fault not to understand
the man page.

When you ask me for improvements, I suggest renaming the tool:

First instead of an abbrevation yk use yubico. This way the
tool shows up when doing a 'aptitude search yubico'.

Second neomgr suggest this is a tool to completely manage
the Yubico neo, but the tool manages only certain parts. You
need e.g. key-personalization-gui for other usages.

Best regards,

Werner

On Tue, Jun 17, 2014 at 01:53:40PM +0200, Simon Josefsson wrote:
 I'm inclined to close this as I couldn't identify any unintended
 behaviour.  Let me know if you have any more questions, or if you can
 think of documentation improvements that would be of help.
 
 /Simon
 
 You wrote:
 
  Hi,
  
  Your NEO is in the OTP-only mode, so it is not a smartcard at all.
  You need to put the NEO in OTP/CCID or CCID-only mode, see at the
  bottom of the man page:
  
  TROBLESHOOTING
 The  error  No  device found can be because a number of
  reasons.  The simplest, of course, is that the device really is not
  connected to  the machine (USB or NFC).  Another reason may be that
  it is in a mode where ykneomgr cannot talk to it.  This can happen
  if the device is in OTP??? only mode (mode 0), where you must use the
  ykpersonalize tool to mode switch it from the OTP???only mode.  It
  can also happen if the device  is in  a  MODE_FLAG_EJECT mode (i.e.,
  81 or 82).  If that is the case, you must touch the button in order
  to insert the virtual smartcard before you can invoke ykneomgr.
  
  So run 'ykpersonalize -m82' or similar to change it from OTP-only
  mode.
  
  /Simon
  
  You wrote:
  
   Hello,
   
   the Yubikey neo doesn't seem to be detected:
   
   #pcsc_scan
   PC/SC device scanner
   V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
   Compiled with PC/SC lite version: 1.8.10
   Using reader plug'n play mechanism
   Scanning present readers...
   Waiting for the first reader...
   
   This message stays forever-
   
   Though 'dmesg' says:
   
   [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49
   [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50
   using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found,
   idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB
   device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202]
   usb 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3:
   Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP
   as 
   /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24
   [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB
   HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on
   usb-:00:1d.7-6.3.3/input0
   
   I am using stock Debian testing with libccid 1.4.16-1 package with
   running pcscd on a i386 machine.
   
 Best regards,
   
 Werner
   

-- 
|=| Werner Heuser = Granitzstr. 26 = D-13189 Berlin = Germany
|=| werner.heuser at web.de = T. +49 - (0)30 - 349 53 86
|=| Skype wehe00 =  T. +49 - (0)176 - 256 58 303
|=| http://sentinel4mobile.de = Sicher unterwegs mit Smartphone und Tablet PC
|*| What is robbing a bank compared to founding a bank? -- B. Brecht


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-11 Thread Simon Josefsson
Hello again.  I don't see any indication of a crash, nor a backtrace
below.  So to me it looks like expected behaviour.

I have improved the documentation a bit to explain what you need to do
in situations like this, see:

https://github.com/Yubico/libykneomgr/commit/cc632bd49531d0adf48a6102bcbb5da24a89f5c6

Is pcscd running on your system?  Could you run 'pcsc_scan' to see that
it finds your YubiKey NEO?  Which version of the 'libccid' package do
you have?

Thanks,
/Simon

You wrote:

 Hello,
 
 thank you for your fast reply.
 
   Best regards,
 
 Werner
 
  Can you start ykneomgr from gdb and get a backtrace?
 
 #gdb --args ykneomgr -a
 GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1)
 Copyright (C) 2013 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.  Type show copying and show warranty for
 details. This GDB was configured as i486-linux-gnu.
 For bug reporting instructions, please see:
 http://www.gnu.org/software/gdb/bugs/...
 Reading symbols from /usr/bin/ykneomgr...(no debugging symbols
 found)...done. (gdb) run
 Starting program: /usr/bin/ykneomgr -a
 warning: Could not load shared library symbols for linux-gate.so.1.
 Do you need set solib-search-path or set sysroot?
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library
 /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. error:
 ykneomgr_init (-4): Backend error [Inferior 1 (process 8819) exited
 with code 01] (gdb) bt
 No stack.
 
 
 Here are also the first lines of strace
 
 xecve(/usr/bin/ykneomgr, [ykneomgr, -a], [/* 51 vars */]) = 0
 brk(0)  = 0x831a000
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or
 directory) mmap2(NULL, 8192, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb772e000
 access(/etc/ld.so.preload, R_OK)  = -1 ENOENT (No such file or
 directory) open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
 fstat64(3, {st_mode=S_IFREG|0644, st_size=129491, ...}) = 0
 mmap2(NULL, 129491, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb770e000
 close(3)= 0 ...
 
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-11 Thread Werner Heuser
Hello,

the Yubikey neo doesn't seem to be detected:

#pcsc_scan
PC/SC device scanner
V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
Compiled with PC/SC lite version: 1.8.10
Using reader plug'n play mechanism
Scanning present readers...
Waiting for the first reader...

This message stays forever-

Though 'dmesg' says:

[1171616.043090] usb 5-6.3.3: USB disconnect, device number 49
[1171622.388457] usb 5-6.3.3: new full-speed USB device number 50 using ehci-pci
[1171622.482191] usb 5-6.3.3: New USB device found, idVendor=1050, 
idProduct=0110
[1171622.482198] usb 5-6.3.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[1171622.482202] usb 5-6.3.3: Product: Yubikey NEO OTP
[1171622.482206] usb 5-6.3.3: Manufacturer: Yubico
[1171622.485176] input: Yubico Yubikey NEO OTP as 
/devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24
[1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB HID v1.10 
Keyboard [Yubico Yubikey NEO OTP] on usb-:00:1d.7-6.3.3/input0

I am using stock Debian testing with libccid 1.4.16-1 package with running 
pcscd on a i386 machine.

Best regards,

Werner


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-11 Thread Simon Josefsson
Hi,

Your NEO is in the OTP-only mode, so it is not a smartcard at all.
You need to put the NEO in OTP/CCID or CCID-only mode, see at the
bottom of the man page:

TROBLESHOOTING
   The  error  No  device found can be because a number of reasons.  The
   simplest, of course, is that the device really is not connected to  the
   machine (USB or NFC).  Another reason may be that it is in a mode where
   ykneomgr cannot talk to it.  This can happen if the device is in OTP‐
   only mode (mode 0), where you must use the ykpersonalize tool to mode
   switch it from the OTP‐only mode.  It can also happen if the device  is
   in  a  MODE_FLAG_EJECT mode (i.e., 81 or 82).  If that is the case, you
   must touch the button in order to insert the virtual smartcard before
   you can invoke ykneomgr.

So run 'ykpersonalize -m82' or similar to change it from OTP-only mode.

/Simon

You wrote:

 Hello,
 
 the Yubikey neo doesn't seem to be detected:
 
 #pcsc_scan
 PC/SC device scanner
 V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
 Compiled with PC/SC lite version: 1.8.10
 Using reader plug'n play mechanism
 Scanning present readers...
 Waiting for the first reader...
 
 This message stays forever-
 
 Though 'dmesg' says:
 
 [1171616.043090] usb 5-6.3.3: USB disconnect, device number 49
 [1171622.388457] usb 5-6.3.3: new full-speed USB device number 50
 using ehci-pci [1171622.482191] usb 5-6.3.3: New USB device found,
 idVendor=1050, idProduct=0110 [1171622.482198] usb 5-6.3.3: New USB
 device strings: Mfr=1, Product=2, SerialNumber=0 [1171622.482202] usb
 5-6.3.3: Product: Yubikey NEO OTP [1171622.482206] usb 5-6.3.3:
 Manufacturer: Yubico [1171622.485176] input: Yubico Yubikey NEO OTP
 as 
 /devices/pci:00/:00:1d.7/usb5/5-6/5-6.3/5-6.3.3/5-6.3.3:1.0/input/input24
 [1171622.485428] hid-generic 0003:1050:0110.0011: input,hidraw4: USB
 HID v1.10 Keyboard [Yubico Yubikey NEO OTP] on
 usb-:00:1d.7-6.3.3/input0
 
 I am using stock Debian testing with libccid 1.4.16-1 package with
 running pcscd on a i386 machine.
 
   Best regards,
 
   Werner
 


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-10 Thread Werner Heuser
Package: ykneomgr
Version: 0.1.2-1
Severity: important

Dear Maintainer,

when trying ykneomgr with different options I get an error e.g. with -a
ykneomgr -a
error: ykneomgr_init (-4): Backend error
and the program crashes.

Best regards,

Werner


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages ykneomgr depends on:
ii  libc6 2.19-1
ii  libykneomgr0  0.1.2-1

ykneomgr recommends no packages.

ykneomgr suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-10 Thread Simon Josefsson
Hello.  Thanks for the report.  I can't reproduce the crash.  With pcscd
not running, I see the following behaviour:

jas@latte:~$ ykneomgr -a
error: ykneomgr_init (-4): Backend error
jas@latte:~$ echo $?
1
jas@latte:~$ 

Which is expected behaviour.

Can you start ykneomgr from gdb and get a backtrace?

/Simon

You wrote:

 Package: ykneomgr
 Version: 0.1.2-1
 Severity: important
 
 Dear Maintainer,
 
 when trying ykneomgr with different options I get an error e.g. with
 -a ykneomgr -a
 error: ykneomgr_init (-4): Backend error
 and the program crashes.
 
   Best regards,
 
   Werner
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages ykneomgr depends on:
 ii  libc6 2.19-1
 ii  libykneomgr0  0.1.2-1
 
 ykneomgr recommends no packages.
 
 ykneomgr suggests no packages.
 
 -- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751133: crash on startup

2014-06-10 Thread Werner Heuser
Hello,

thank you for your fast reply.

Best regards,

Werner

 Can you start ykneomgr from gdb and get a backtrace?

#gdb --args ykneomgr -a
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1)
Copyright (C) 2013 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.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/ykneomgr...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/ykneomgr -a
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need set solib-search-path or set sysroot?
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
error: ykneomgr_init (-4): Backend error
[Inferior 1 (process 8819) exited with code 01]
(gdb) bt
No stack.


Here are also the first lines of strace

xecve(/usr/bin/ykneomgr, [ykneomgr, -a], [/* 51 vars */]) = 0
brk(0)  = 0x831a000
access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb772e000
access(/etc/ld.so.preload, R_OK)  = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=129491, ...}) = 0
mmap2(NULL, 129491, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb770e000
close(3)= 0
...


-- 
|=| Werner Heuser = Granitzstr. 26 = D-13189 Berlin = Germany
|=| werner.heuser at web.de = T. +49 - (0)30 - 349 53 86
|=| Skype wehe00 =  T. +49 - (0)176 - 256 58 303
|=| http://sentinel4mobile.de = Sicher unterwegs mit Smartphone und Tablet PC
|*| What is robbing a bank compared to founding a bank? -- B. Brecht


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org