Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

One last question on this. The gpg4win-3.0.0.exe installs among others an
OutLook plugin (GpgOl DLL) which let you encrypt and sign mails in
OutLook. Ofc, my keypair I'm using with the OpenPGP Card was built for 
'Matthias Apitz  ' and not for my company mail addr 
matthias.ap...@oclc.org; this brings always on signing up a Window like this
http://www.unixarea.de/kleo3.jpg of Kleopatra because it can not choose
by its own the correct certificate. Is there a way to configure this
within Kleopatra or GpgOl?

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día martes, noviembre 21, 2017 a las 06:50:18p. m. +0900, NIIBE Yutaka 
escribió:

> Matthias Apitz  wrote:
> > The produced log is:
> >
> > $ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
> [...]
> > 2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
> > portstr=(null)
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> > Contacted SmartCard 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> > Contactless SmartCard 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC 
> > Smartcard Reader 1'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 
> > SAM slot Token 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
> > 2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
> 
> You have five card readers (the last one looks strange, though).
> 
> GnuPG's scdaemon select the first one as default.  IIUC, you want to use
> 'Identiv uTrust 3512 SAM slot Token 0'.
> 
> In .gnupg/scdaemon.conf, you should have something like:
> ===
> reader-port "Identiv uTrust 3512 SAM slot Token"
> ===
> 
> ... to select the token.

Thanks! Adding the above line to GNUPGHOME/scdaemon.conf makes it all work,
even the GPA and other GUI tools.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[NIIBE Yutaka]

Matthias Apitz  wrote:
> The produced log is:
>
> $ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
[...]
> 2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
> portstr=(null)
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
> SmartCard 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> Contactless SmartCard 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
> Reader 1'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
> slot Token 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
> 2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected

You have five card readers (the last one looks strange, though).

GnuPG's scdaemon select the first one as default.  IIUC, you want to use
'Identiv uTrust 3512 SAM slot Token 0'.

In .gnupg/scdaemon.conf, you should have something like:
===
reader-port "Identiv uTrust 3512 SAM slot Token"
===

... to select the token.
-- 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

Hello,

Thanks, Werner, for the helping hand. I did so to capture the log of the 
scdaemon.
But did not used the nice trick of TCP, because I did not wanted to have the VM
up and running and blocking the OpenPGP Card on USB. I run all the GnuPG 
commands
from the DOS cmd shell, only the tail of the scdaemon.log was done in Cygwin.

The scdaemon.conf used was:

$ cat /cygdrive/c/Users/apitzm/AppData/Roaming/gnupg/scdaemon.conf
log-file scdaemon.log
debug-level guru
debug-all
debug-log-tid
card-timeout 30

The produced log is:

$ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
2017-11-21 08:24:04 scdaemon[3868.1] Es wird auf Socket 
`C:\Users\apitzm\AppData\Roaming\gnupg\S.scdaemon' gehört
2017-11-21 08:24:04 scdaemon[3868.2] Handhabungsroutine für fd -1 gestartet
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK GNU Privacy 
Guard's Smartcard server ready
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- GETINFO socket_name
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> D 
C:\Users\apitzm\AppData\Roaming\gnupg\S.scdaemon
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- OPTION 
event-signal=f0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- serialno
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
portstr=(null)
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
SmartCard 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contactless 
SmartCard 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
Reader 1'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
slot Token 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_open_reader => slot=0 
[pc/sc]
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_connect: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] pcsc_connect failed: removed card 
(0x80100069)
2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_connect => sw=0x10008
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_close_reader: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_disconnect: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_disconnect => sw=0x0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_close_reader => 0x0 
(close_reader)
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> ERR 100696144 No 
such device 
2017-11-21 08:24:23 scdaemon[3868.2] DBG: chan_0x00b0 <- RESTART
2017-11-21 08:24:23 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:26:07 scdaemon[3868.2] DBG: chan_0x00b0 <- serialno
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
portstr=(null)
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
SmartCard 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Broadcom Corp Contactless 
SmartCard 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
Reader 1'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
slot Token 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader ''
2017-11-21 08:26:07 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_open_reader => slot=0 
[pc/sc]
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_connect: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] pcsc_connect failed: removed card 
(0x80100069)
2017-11-21 08:26:07 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_connect => sw=0x10008
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_close_reader: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_disconnect: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_disconnect => sw=0x0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_close_reader => 0x0 
(close_reader)
2017-11-21 08:26:07 scdaemon[3868.2] DBG: chan_0x00b0 -> ERR 100696144 No 
such device 
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 <- help
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # NOP
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # CANCEL
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # OPTION
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # BYE
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # AUTH
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # RESET
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # END
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # HELP
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # SERIALNO 
[--demand=] []

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día lunes, noviembre 20, 2017 a las 03:07:44p. m. +0100, Peter Lebbing 
escribió:

> On 20/11/17 08:56, Matthias Apitz wrote:
> > I killed a running SmartCard Service on Win7 and tested GnuPG on a
> > Cygwin command line.
> 
> Involving Cygwin is yet another non-trivial hurdle to take. I think it's
> best if you get it working on Windows first, and only then try to
> involve another layer in the form of Cygwin.
> 
> You can see what happens when you use gpg.exe from the Windows command
> prompt. If that works out, see what happens in the GUI manager(s)
> included with gpg4win-3.0.0.exe. Assuming it does include GUI software :-).


This gives the same output as from Cygwin:


C:\Users\apitzm\vb\GnuPG\bin>gpg.exe --card-status --debug-all --debug-level 
guru
gpg: Optionen werden aus
'C:/Users/apitzm/AppData/Roaming/gnupg/gpg.conf' gelesen
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache
memstat trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_0x00d0 <- OK Pleased to meet you
gpg: DBG: connection to agent established
gpg: DBG: chan_0x00d0 -> RESET
gpg: DBG: chan_0x00d0 <- OK
gpg: DBG: chan_0x00d0 -> GETINFO version
gpg: DBG: chan_0x00d0 <- D 2.2.1
gpg: DBG: chan_0x00d0 <- OK
gpg: DBG: chan_0x00d0 -> OPTION allow-pinentry-notify
gpg: DBG: chan_0x00d0 <- OK
gpg: DBG: chan_0x00d0 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_0x00d0 <- OK
gpg: DBG: chan_0x00d0 -> SCD GETINFO version
gpg: DBG: chan_0x00d0 <- D 2.2.1
gpg: DBG: chan_0x00d0 <- OK
gpg: DBG: chan_0x00d0 -> SCD SERIALNO openpgp
gpg: DBG: chan_0x00d0 <- ERR 100696144 No such device 
gpg: selecting openpgp failed: No such device
gpg: OpenPGP Karte ist nicht vorhanden: No such device
gpg: DBG: [not enabled in the source] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:build=0 update=0 insert=0 delete=0
gpg:reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
  outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks

C:\Users\apitzm\vb\GnuPG\bin>

I saw the next mail from Werner, and will try to follow this.
Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Werner Koch]

On Mon, 20 Nov 2017 08:56, g...@unixarea.de said:

> I killed a running SmartCard Service on Win7 and tested GnuPG on a
> Cygwin command line. It says:

Cygwin - I would not suggest to use this.  We have no idea on whether
the RNG does what we want it to do.  The IPC mechanism and
descriptor/handle passing may have surprising effects .

There is a new gnupg 2.2.3 installer available, I better use that


> $ gpg --card-status --debug-all --debug-level guru 

Smartcard access is done by scdaemon.  Thus you have to modify or
create scdaemon.conf: 

  log-file tcp://192.168.x.y:42042
  verbose
  debug ipc,cardio

The tcp line is what I use to debug on Windows.  On my Unix box I run

  watchgnupg --time-only --tcp 42042

so that I can work with the logs without resorting to strange Windows
tools.  After changing scdaemon.conf you should kill scdaemon; gpg-agent
will start it as neede.  Tetsing with gpg is okay, but you can also use

  gpg-connect-agent 
  
and then enter

  scd help

to see all commands supported by scdameon.  The "scd " prefix simply
routes the rest of the command to scdaemon.

  scd help serialno

shows you help for scdaemon's "serialno" command. 

  scd serialno

and runs the command which select the "best" appliication on the current
card.  If the OpenPGP card does not work, try you banking card - there
is a simple application for the "Geldkarte" included.
 

Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgplyrYn0TLPk.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Peter Lebbing]

On 20/11/17 08:56, Matthias Apitz wrote:
> I killed a running SmartCard Service on Win7 and tested GnuPG on a
> Cygwin command line.

Involving Cygwin is yet another non-trivial hurdle to take. I think it's
best if you get it working on Windows first, and only then try to
involve another layer in the form of Cygwin.

You can see what happens when you use gpg.exe from the Windows command
prompt. If that works out, see what happens in the GUI manager(s)
included with gpg4win-3.0.0.exe. Assuming it does include GUI software :-).

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día domingo, noviembre 19, 2017 a las 03:20:16p. m. +0100, Peter Lebbing 
escribió:

> On 17/11/17 16:09, Matthias Apitz wrote:
> > It seems that the USB token is fine, but the Card is not (see
> > attachment).
> 
> I don't use Windows myself, but AFAIK, this is normal and not a problem.
> 
> AFAIK, the exclamation mark triangle on the smartcard means that the OS
> has no driver to work with that specific smartcard. But GnuPG
> communicates directly with the smartcard; the "driver" so to speak is
> inside GnuPG. In fact, if you found another OS-level driver that is
> happy to work with your smartcard, you are probably /creating/ an issue
> since it will keep a lock on the smartcard so GnuPG no longer can get
> access to it. While shared access to a smartcard is not impossible per
> se, often you'll find that programs want exclusive access, and you can't
> use two programs with the same smartcard at the same time.
> 
> An exclamation mark triangle on the /reader/ would probably indicate an
> issue, but an exclamation mark triangle on the /smartcard/ is probably
> for the best.
> 
> Still, I've only used different types of smartcards on Windows, and only
> very sporadically, so I don't think I can be of much further help.

Hello,

Thanks for your feedback, Peter.

I killed a running SmartCard Service on Win7 and tested GnuPG on a
Cygwin command line. It says:


$ uname -a
CYGWIN_NT-6.1 APITZM-LTOH 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64 Cygwin

$ gpg --version
gpg (GnuPG) 2.2.1
libgcrypt 1.8.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Users/apitzm/AppData/Roaming/gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ gpg --card-status --debug-all --debug-level guru 
gpg: reading options from 'C:/Users/apitzm/AppData/Roaming/gnupg/gpg.conf'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat 
trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_0x00d8 <- OK Pleased to meet you
gpg: DBG: connection to agent established
gpg: DBG: chan_0x00d8 -> RESET
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> OPTION ttytype=xterm
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> GETINFO version
gpg: DBG: chan_0x00d8 <- D 2.2.1
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> OPTION allow-pinentry-notify
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> SCD GETINFO version
gpg: DBG: chan_0x00d8 <- D 2.2.1
gpg: DBG: chan_0x00d8 <- OK
gpg: DBG: chan_0x00d8 -> SCD SERIALNO openpgp
gpg: DBG: chan_0x00d8 <- ERR 100696144 No such device 
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device
gpg: DBG: [not enabled in the source] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:build=0 update=0 insert=0 delete=0
gpg:reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
  outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks

It does not make any difference, if I also start the scdaemon with
$ scdaemon --daemon &

or not.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Peter Lebbing]

On 17/11/17 16:09, Matthias Apitz wrote:
> It seems that the USB token is fine, but the Card is not (see
> attachment).

I don't use Windows myself, but AFAIK, this is normal and not a problem.

AFAIK, the exclamation mark triangle on the smartcard means that the OS
has no driver to work with that specific smartcard. But GnuPG
communicates directly with the smartcard; the "driver" so to speak is
inside GnuPG. In fact, if you found another OS-level driver that is
happy to work with your smartcard, you are probably /creating/ an issue
since it will keep a lock on the smartcard so GnuPG no longer can get
access to it. While shared access to a smartcard is not impossible per
se, often you'll find that programs want exclusive access, and you can't
use two programs with the same smartcard at the same time.

An exclamation mark triangle on the /reader/ would probably indicate an
issue, but an exclamation mark triangle on the /smartcard/ is probably
for the best.

Still, I've only used different types of smartcards on Windows, and only
very sporadically, so I don't think I can be of much further help.

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día jueves, noviembre 16, 2017 a las 07:23:03p. m. +0100, Werner Koch 
escribió:

> Usually the Windows hardware detection (a menu item like "Install new
> hardware", ot a small icon in the taskbar) can locate all common reader
> types and their drivers.  It not, you need to check the website of the
> reder's vendor.

Hi,

It seems that the USB token is fine, but the Card is not (see
attachment).

I installed some driver and after this the the problem symbol is away,
but neither GPA nor Kleopatra can use the Card.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día jueves, noviembre 16, 2017 a las 07:23:03p. m. +0100, Werner Koch 
escribió:

> Usually the Windows hardware detection (a menu item like "Install new
> hardware", ot a small icon in the taskbar) can locate all common reader
> types and their drivers.  It not, you need to check the website of the
> reder's vendor.

Hi,

It seems that the USB token is fine, but the Card is not (see
http://www.unixarea.de/SnipToolPlusImg.jpg )

I installed some driver and after this the the problem symbol (!) is away,
but neither GPA nor Kleopatra can use the Card.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Werner Koch]

On Thu, 16 Nov 2017 13:56, g...@unixarea.de said:

> I copied over GNUPGHOME and gpa and OutLook can see/use the pub key. To
> get access to the Card, I need some driver in Win7. Do you know any
> reliable place to fetch from.

Usually the Windows hardware detection (a menu item like "Install new
hardware", ot a small icon in the taskbar) can locate all common reader
types and their drivers.  It not, you need to check the website of the
reder's vendor.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgptEGIlrmUhd.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Matthias Apitz]

El día miércoles, noviembre 15, 2017 a las 12:19:30p. m. +0100, Werner Koch 
escribió:

> On Wed, 15 Nov 2017 09:06, g...@unixarea.de said:
> 
> > Before digging into all the details by my own and esp. because in Windows 
> > I'm only a
> > DAU(*), is there some step by step guide to configure the OpenPGP Card in
> > Windows and using the files from the GNUPGHOME on FreeBSD in Windows?
> 
> Actually you could copy the entire GNUPGHOME to the respective Windows
> directory.  The name of the lock files and some temporary files are
> different but that does matter.  "gpg --version" (or "gpgconf
> --list-dirs") shows you the standard home directory on Windows.
> 
> If you only want to copy some keys, you can use the same procedure you
> would use between Unix boxes.
> 
> Kleopatra's card manager is pretty basics.  If you don't like it you can
> use the one in gpa (which can optionally be installed), or just resort
> to the command line.  

I copied over GNUPGHOME and gpa and OutLook can see/use the pub key. To
get access to the Card, I need some driver in Win7. Do you know any
reliable place to fetch from.

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Using the OpenPGP Card on Unix && Win7

[Werner Koch]

On Wed, 15 Nov 2017 09:06, g...@unixarea.de said:

> Before digging into all the details by my own and esp. because in Windows I'm 
> only a
> DAU(*), is there some step by step guide to configure the OpenPGP Card in
> Windows and using the files from the GNUPGHOME on FreeBSD in Windows?

Actually you could copy the entire GNUPGHOME to the respective Windows
directory.  The name of the lock files and some temporary files are
different but that does matter.  "gpg --version" (or "gpgconf
--list-dirs") shows you the standard home directory on Windows.

If you only want to copy some keys, you can use the same procedure you
would use between Unix boxes.

Kleopatra's card manager is pretty basics.  If you don't like it you can
use the one in gpa (which can optionally be installed), or just resort
to the command line.  


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgp1BlLz7PkzA.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users