Re: decrypt and trusting certs

Hi Ildar:

Am 05.10.12 22:20 schrieb(en) Ildar Mulyukov:
I started to look at this part and it has a little glitch: it displays 16-hexdigit Key fingerprint. But the useful part is actually digits 9 to 16 (the 8 digits that user sees in seahorse or even in `gpg2 --search-keys` output).

Wrong.  You can use either the key id or the key fingerprint as arg for '--search-keys' and friends.  See 'man gpg' for details.

emm. I am not sure what you mean.
$ rpm -qf /usr/bin/gpgsm

Say 'man gpg':
gpg - OpenPGP encryption and signing tool
       gpg  is  the OpenPGP part of the GNU Privacy Guard (GnuPG). It is a tool to provide digital encryption and signing ser‐
       vices using the OpenPGP standard. gpg features complete key management and all bells and whistles you can expect from a
       decent OpenPGP implementation.

Say 'man gpgsm':
gpgsm - CMS encryption and signing tool
       gpgsm  is  a  tool  similar to gpg to provide digital encryption and signing services on X.509 certificates and the CMS
       protocol.  It is mainly used as a backend for S/MIME mail processing.  gpgsm includes a full featured certificate  man‐
       agement and complies with all rules defined for the German Sphinx project.

I.e. two completely separate applications, serving related, but totally different purposes.

gpgsm binary is from the gnupg2 package.

If Redhat decides to pack both applications into one rpm it's basically their decision/problem.  Debian/Ubuntu use two separate ones, which makes sense as the dependencies are different.

Best, Albrecht.

Attachment: pgpRwAYKeyzew.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]