Naeem,
It's highly unlikely that an individual would be capable of stealing a secret
key and using it to decrypt messages. A large corporation or government,
maybe. Make your passphrases complex.
I'm a little cautious myself with my secret keys, so I use two hardware based
approaches to ease m
Paulo,
I apologize in advance for the rtfm response, but you probably want to
investigate the --sign and --clearsign options in the gpg manpage. If you are
only looking for authenticity, and not secrecy, then encryption is probably not
necessary.
Best regards,
Harvey
- Original Mess
If you decide not to remove seahorse-agent, for any reason, you can workaround
the issue by using the --no-use-agent option with gpg. You still will be
unable to decrypt with seahorse agent.
HTH,
Harvey
- Original Message
> From: Stephan Hermann <[EMAIL PROTECTED]>
> To: Andreas Gras
Sven,
I think I just bumped into your problem. I've been testing Hardy, and haven't
had any problems with the OpenPGP card until now. I have to investigate
further, but preliminary results indicate a udev or related problem. In Gutsy,
the device is created in /dev, in Hardy it is not. Hardy
> Any ideas? Or, for starters, any hints to produce a more meaningful
> error message?
Sven,
I've used the OpenPGP card recently with Gutsy and the Hardy releases without
issue. To troubleshoot you can try:
$ ps aux | grep pcscd
The above commands should report two lines, one for the grep comm
