On 02/03/2018 04:15 PM, Pijus Kar wrote:
> Is it something for the version incompatibility or in the key?
As far as I can see the keyblock referenced is DSA2, which is specified
in FIPS-186-3 from 2009, and you're using a gnupg version from 2002.
--
Kristian
Basic questions:
1) Is the above message in fact an "error"?
2) What exactly does it mean?
3) Why does it appear to be backwards? (i.e. Why is the first number it says it
"wrote" larger than what it says it "expected"?
4) How can I detect when this occurs as an "error" to prevent the encryption
Please see attached patches to add support for arc4random_buf() as an
alternate to /dev/{u}random. I tried to be as unobtrusive as possible
and maintain style. It should also allow the user to still define
RANDOM_CONF_ONLY_URANDOM if they would prefer to use /dev/urandom. This
will allow gpg
Hello,
I'm using an OpenPGP card and gnupg 2.1.19 on my FreeBSD workstations
and my Ubuntu mobile device to store crypted passwords (tool: password-store),
to lock/unlock desktop sessions and to sign emails. This is all working
fine and without any hick-ups.
What makes me worry, is that single
