On 01/23/2016 10:11 PM, Fulano Diego Perez wrote:
> NIIBE Yutaka:
>> Please note that you need to invoke gpg-agent with LD_LIBRARY_PATH, too.
>
> can explain how you mean to invoke ?
Well, it seems terminology issue. I mean, to start, to kick the service,
and to run the service.
In general, the
On Sun 2016-01-24 13:55:38 -0500, Werner Koch wrote:
> If you talk to people on how they verify SSH fingerprints (that is even
> MD5 for most installations)
SSH key fingerprints are a different thing than software distribution
checksums because the material digested in ssh originates entirely from
On Sat, 23 Jan 2016 12:29, prze...@gmail.com said:
> I would like to sign someone's key with my non-primary UID.
> Why? To reflect that given UID is the one I use when contacting owner
You do not sign a key with a user id but with your key. Thus it does
not make sense to declare which user id ma
On Sun, 24 Jan 2016 00:01, d...@fifthhorseman.net said:
> fwiw, MD5 and SHA1 are both old digest algorithms, and are not as strong
> as they should be. I recommend that anyone using checksums for file
> integrity switch to SHA256 as soon as possible.
That is correct for MD5 given how easy it is
Hello!
After upgrading my packages (now on gnupg 2.1.9), I am getting an error
when trying to sign:
$ echo "test"|gpg2 -sa
gpg: signing failed: Invalid IPC response
-BEGIN PGP MESSAGE-
gpg: signing failed: Invalid IPC response
gpg-agent.conf contains:
pinentry-program /usr/local/bin/pin
## W Wong (wwongwong2...@gmail.com):
> 4a88f90a01b0ba8e3eb0073f7b6a4bfb ..\..\downloads\gpg4win-2.3.0.exe
That is the MD5 checksum of the gpg4win-2.3.0.exe file, which has
the SHA1 checksum 88d90ee9a1ea3e66b198ea866063140b882444d5.
Regards,
Christoph
--
Spare Space
___
