-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Adam,
2011/11/8 Adam :
> when creating a new key, gpg2 creates a selfsig and a subkey which is
> selfsiged as well. Why does it do so? Why not create just a plain key
> without subkey and selfsig?
gpg2 (and gpg 1 the same) by default creates a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Priya,
I'm not an expert of Solaris 10 on Sparc architecture, however I might
have found your problem in the procedure you followed.
> 1) I untar 'ed the build libraries from required tar files
> 2) After unzip/untar, formed below directories [.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi zerious,
First of all:
The following answer is about "how to get those informations from an
encrypted message".
If you need to force some algorithms, you can use the --cipher-algo,
--digest-algo, --compress-algo and --cert-digest-algo options.
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello veidaal and gnupg-users list.
> My understanding, (which may be outdated),
> is that there are too many variations in individual user systems,
> so that the compiled files would never have 'exactly' the same
> hash independent of where they a
