On Thu 2017-08-17 22:39:21 -0300, Duane Whitty wrote:
> Sounds like a good approach but for someone who has more public keys
> stored than me. I only exchange encrypted email with a very, very
> small group of people and I am in regular voice communication with
> them.
If you're going to manage
On Thu 2017-08-17 22:48:36 -0300, Duane Whitty wrote:
> Well, I'm not familiar enough with the arcana to say whether it should
> be done away with or not but, I am a big believer in software not
> trying to guess what I want. As you said, in version 2.1 GnuPG would
> have complained that I hadn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17-08-17 09:20 PM, Daniel Kahn Gillmor wrote:
> On Mon 2017-08-14 22:12:18 -0300, Duane Whitty wrote:
>> Actually one suggestion, the way options and commands are
>> specified look the same. It might make things clearer if there
>> was a
e is going to happen in GnuPG, it will be in the
> 2.1 branch (or in 2.3 once 2.2 is released). the older branches of
> GnuPG (1.4.x and 2.0.x) receive very few changes from upstream.
>
>> I can say that what I usually end up being challenged by is
>> importing keys into my keyring a
On Mon 2017-08-14 22:12:18 -0300, Duane Whitty wrote:
> Actually one suggestion, the way options and commands are specified
> look the same. It might make things clearer if there was a difference
> in the way they are expressed on the command line. Perhaps keep the
> "--" for options and enter
and on being able to choose which UID I want to
> sign with. Maybe that just means I don't know the software well enough.
You don't sign with a UID, you sign with a key.
> The approach I took was "gpg2 --search u...@domain.com" and "gpg2
> - --recv-keys key-fingerprint&qu
ource
> they expected, in this case via apt or apt-get, etc. from an Oracle
> repo.
>
>
>>> Before I go down the road on offering an opinion on how the
>>> man page should be "fixed" (maybe it's not really broken) can
>>> you explain why it would b
own the road on offering an opinion on how the man
>> page should be "fixed" (maybe it's not really broken) can you
>> explain why it would be bad to let gpg generate and display the
>> fingerprint of a key in an ascii armoured file?
>
> I'm not saying it's "
y more about why you don't want to import the key,
and why you prefer to fetch it each time?
> Before I go down the road on offering an opinion on how the man page
> should be "fixed" (maybe it's not really broken) can you explain why
> it would be bad to let gpg generate an
ut I can see that --with-fingerprint is an
option under the section "Key related options" and so it makes sense
that a command should be entered as well.
I am not sure I understand why it would be bad to do the following,
which implies not importing the key to a keyring:
gpg --wi
On Mon 2017-08-14 13:25:58 -0300, Duane Whitty wrote:
> Thanks for your response. So, what you are saying is that the man
> page is wrong ;-)
I didn't think that was what i was saying, but there have certainly been
bugs in the documentation in the past. Is there specific text that you
think is
On Mon 2017-08-14 15:09:22 -0400, Todd Zullinger wrote:
> $ gpg --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary
> pub 4096R/FDB19C98 2016-03-31 Fedora 25 Primary (25)
> <fedora-25-prim...@fedoraproject.org>
> Key fingerprint = C437 DCCD 55
Daniel Kahn Gillmor wrote:
with more modern versions of gnupg, you can just use:
gpg --with-fingerprint --import-options show-only --import <
public-key-file.asc
FWIW, I've used "gpg --with-fingerprint public-key-file.asc" for what
seems like years to do this sort of quic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17-08-14 12:14 PM, Daniel Kahn Gillmor wrote:
> On Mon 2017-08-14 03:32:08 -0300, Duane Whitty wrote:
>> I was recently trying to compare the fingerprint of a key I
>> downloaded to its online stated value. I thought I sh
On Mon 2017-08-14 03:32:08 -0300, Duane Whitty wrote:
> I was recently trying to compare the fingerprint of a key I downloaded
> to its online stated value. I thought I should be able to accomplish
> my goal with "gpg --fingerprint public-key-file.asc". Gpg returned
> &
trying to compare the fingerprint of a key I downloaded
to its online stated value. I thought I should be able to accomplish
my goal with "gpg --fingerprint public-key-file.asc". Gpg returned
"gpg: error reading key: No public key"
So I did a search and found --with-fingerprint
16 matches
Mail list logo
