Re: USB key form-factor smart-card readers with pinpads?

2014-01-11 Thread Sam Kuper
On 07/01/2014, Peter Lebbing wrote: > On 07/01/14 17:27, Werner Koch wrote: >> See the card HOWTO or try gpg --card-edit, admin, help. > > Additionally, in the OpenPGP Card 2.0.1 spec, the DO with tag C4 on page > 17, > section 7.2.2 (VERIFY) and section 7.2.8 (PSO: COMPUTE DIGITAL SIGNATURE) > al

dirmngr segfaults

2014-01-11 Thread Fabio Coatti
Hi all, I'm seeing several segfaults from dirmngr, tried googling around but with no success this time :) [sab gen 11 13:22:51 2014] dirmngr[11220]: segfault at 580 ip 7fdbfe5abbe1 sp 7fff12335980 error 4 in libpth.so.20.0.27[7fdbfe5a2000+13000] backtrace: cova@calvin ~ $ gdb /usr/bin/di

Re: USB key form-factor smart-card readers with pinpads?

2014-01-11 Thread Sam Kuper
On Jan 9, 2014 7:16 PM, "David Tomaschik" wrote: > > if the machine you are using for crypto operations is compromised, you have > lost (at least for the operations conducted while it is compromised) Perhaps I'm wrong, but I don't entirely accept this. Surely if you are signing with a key stored

Re: USB key form-factor smart-card readers with pinpads?

2014-01-11 Thread David Tomaschik
On Sat, Jan 11, 2014 at 1:05 PM, Sam Kuper wrote: > On Jan 9, 2014 7:16 PM, "David Tomaschik" > wrote: > > > > if the machine you are using for crypto operations is compromised, you > have lost (at least for the operations conducted while it is compromised) > > Perhaps I'm wrong, but I don't ent

Re: USB key form-factor smart-card readers with pinpads?

2014-01-11 Thread Sam Kuper
On 11/01/2014, David Tomaschik wrote: > On Sat, Jan 11, 2014 at 1:05 PM, Sam Kuper wrote: >> On Jan 9, 2014 7:16 PM, "David Tomaschik" >> wrote: >> > if the machine you are using for crypto operations is compromised, you >> have lost (at least for the operations conducted while it is compromised

Re: USB key form-factor smart-card readers with pinpads?

2014-01-11 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Saturday 11 January 2014 at 11:18:55 PM, in , Sam Kuper wrote: > Yes, as I said, it could tamper with the message. But > if it does that, then when a recipient attempts to > verify the signature, gpg --verify will give the > message, "gpg: