Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: PGP key question

Great you guys, thank you so much.  Glad to hear that source forge hasn't swooped so low as cnet.

My coworker Thibault was showing me around zsh yesterday.  I think I actually drooled.

Cheers

Clark

On 10/2/18, 7:16 AM, "Daniel Shahaf" <d.s@xxxxxxxxxxxxxxxxxx> wrote:

    Peter Stephenson wrote on Tue, 02 Oct 2018 09:23 +0100:
    > On Tue, 2 Oct 2018 08:51:17 +0100
    > Ben Oliver <ben@xxxxxxxxxxxx> wrote:
    > > On 18-10-02 01:21:03, Clark Dunson wrote:
    > > >gpg: WARNING: This key is not certified with a trusted signature!
    > > >
    > > >gpg:          There is no indication that the signature belongs to the owner.
    > > >
    > > >Primary key fingerprint: E966 46BE 08C0 AF0A A0F9  0788 A5FE EE3A C793 7444
    > > >
    > > >     Subkey fingerprint: 6EB6 0B63 7CE5 ACBF 2449  A2DA DB27 E997 429A F20C
    > > >
    > > >Is there a concern here?  
    > > 
    > > This is just a warning that you have not personally signed the key, ie 
    > > verified that you know this person.
    > > 
    > > gpg just knows that key X was used to sign the package, it doesn't know 
    > > if the key truly belongs to the owner - that's on you to find out. If 
    > > you are 100% sure (usually after meeting the owner) you can sign the key 
    > > to avoid the warning.
    
    In gpg(1), you can use 'lsign' to mark the key as known without
    accidentally publishing the signature.  This is useful even without
    verifying my identity, since it'll allow you to be sure that the 5.7
    artifacts (when that version is released) will have been signed by the
    same key who signed the 5.6.2 artifacts.
    
    > To fill in the obvious: we're quite sure the releases were actually
    > signed either by Daniel or me.
Messages sorted by: Reverse Date, Date, Thread, Author