[Bug 262174] gpg.conf options in Committer's guide should be reviewed/updated

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 28 Feb 2022 14:30:35 UTC

Danilo G. Baio <dbaio@freebsd.org> changed:

           What    |Removed                     |Added
                 CC|                            |dbaio@freebsd.org

--- Comment #2 from Danilo G. Baio <dbaio@freebsd.org> ---
It seems we also need to update the example and checkkey.sh script to let
everything in the current standards.

$ gpg --full-gen-key                                                           
gpg (GnuPG) 2.3.3; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Please select what kind of key you want:
   (1) RSA and RSA
   (2) DSA and Elgamal
   (3) DSA (sign only)
   (4) RSA (sign only)
   (9) ECC (sign and encrypt) *default*
  (10) ECC (sign only)
  (14) Existing key from card
Your selection?
Please select which elliptic curve you want:
   (1) Curve 25519 *default*
   (4) NIST P-384
   (6) Brainpool P-256
Your selection?
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 3y
Key expires at Thu Feb 27 11:23:05 2025 -03
Is this correct? (y/N) y

GnuPG needs to construct a user ID to identify your key.

Real name: Example Name
Email address: examplegpg@example.com
You selected this USER-ID:
    "Example Name <examplegpg@example.com>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o

$ ./checkkey.sh examplegpg@example.com
WARNING: Multiple keys found for <examplegpg@example.com>; checking all.
WARNING: If this is not what you want, specify a key ID on the command line.
key 058D86854BCA9F3E: *UNKNOWN*, 802551913614111591151 bits
    ** problems found:
        non-preferred algorithm

    ** key 058D86854BCA9F3E should not be used!

You are receiving this mail because:
You are the assignee for the bug.