We upgraded from gpg 1.2.6 to 1.4.5 on "Red Hat Enterprise Linux AS
release 4 (Nahant Update 5)".
After that we encrypted a file as "/usr/bin/gpg --armor --output
$out_file --encrypt -q --yes -r '$gpg_userid' $file".
However, with 1.4.5 we get an encrypted file everything in one line
and gets cut
Am Mi 13.02.2013, 20:16:01 schrieb Jan Ignatius:
> Coming back to your original proposal, could you give me some guidance
> on how i can check the user permissions for the Crypto Stick?
That's easy:
lsusb shows you the bus and device number.
ls -l /dev/bus/usb/002/
for all devices on bus 2 or
On Wed, 13 Feb 2013 11:55:59 +0100
Hauke Laging wrote:
> Am Mi 13.02.2013, 07:46:31 schrieb Jan Ignatius:
>
> > scdaemon[2740]: PC/SC OPEN failed: reader unavailable
>
> I think this is the relevant problem with thr rest being the result
> of that. What are the access rights for the reader? Can
Am Mi 13.02.2013, 07:46:31 schrieb Jan Ignatius:
> scdaemon[2740]: PC/SC OPEN failed: reader unavailable
I think this is the relevant problem with thr rest being the result of that.
What are the access rights for the reader? Can your user account access it?
Perhaps you need a suitable udev rule.
