public inbox for selinux@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <lautrbach@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] SECURITY.md: add lautrbach@redhat.com gpg fingerprint
Date: Thu, 08 Jan 2026 09:57:17 +0100	[thread overview]
Message-ID: <87cy3kv5w2.fsf@redhat.com> (raw)
In-Reply-To: <CAHC9VhQmYLMqFzytgauijn_C6TXksBVsptEdNb2ZcyKFT8fsCg@mail.gmail.com>

Paul Moore <paul@paul-moore.com> writes:

> On Wed, Jan 7, 2026 at 7:08 AM Petr Lautrbach <lautrbach@redhat.com> wrote:
>> Paul Moore <paul@paul-moore.com> writes:
>> > On Mon, Jan 5, 2026 at 12:46 PM Petr Lautrbach <lautrbach@redhat.com> wrote:
>> >>
>> >> The key is available at:
>> >> https://github.com/bachradsusi.gpg
>> >> https://plautrba.fedorapeople.org/lautrbach@redhat.com.gpg
>> >>
>> >> Also update the email address
>> >>
>> >> Signed-off-by: Petr Lautrbach <lautrbach@redhat.com>
>> >> ---
>> >>  SECURITY.md | 3 ++-
>> >>  1 file changed, 2 insertions(+), 1 deletion(-)
>> >>
>> >> diff --git a/SECURITY.md b/SECURITY.md
>> >> index 2a7ce5b317a7..faa060ccff03 100644
>> >> --- a/SECURITY.md
>> >> +++ b/SECURITY.md
>> >> @@ -24,7 +24,8 @@ list is below. We typically request at most a 90 day time period to address
>> >>  the issue before it is made public, but we will make every effort to address
>> >>  the issue as quickly as possible and shorten the disclosure window.
>> >>
>> >> -* Petr Lautrbach, plautrba@redhat.com
>> >> +* Petr Lautrbach, lautrbach@redhat.com
>> >> +  *  (GPG fingerprint) 68D2 1823 342A 1368 3AEB  3E4E FB4C 685B 5DC1 C13E
>> >
>> > I think you may want to list the fingerprint of your primary key and
>> > not a subkey, as the primary key is what carries the signatures and
>> > helps verify trust.
>> >
>>
>> I guess I need help then:
>>
>> $ gpg --show-keys --fingerprint lautrbach@redhat.com.gpg
>
> You want to use the key fingerprint which displays when you run 'gpg
> --fingerprint <email>'.  Assuming you have the keys for the other devs
> in your keyring, you'll notice that command can be used to reproduce
> the other fingerprints in the file.
>
> %  gpg --fingerprint plautrba@redhat.com
> pub   rsa4096 2012-04-03 [SC]
>      E853 C184 8B01 85CF 4286  4DF3 63A8 AD4B 982C 4373
> uid           [  full  ] Petr Lautrbach <plautrba@redhat.com>
> sub   rsa4096 2012-04-03 [E]
> sub   rsa4096 2017-12-05 [S]
> sub   rsa4096 2017-12-05 [A]

I've also changed my email contact address to lautrbach@redhat.com which I
use for some time already:

> From: Petr Lautrbach <lautrbach@redhat.com>

> -* Petr Lautrbach, plautrba@redhat.com
> +* Petr Lautrbach, lautrbach@redhat.com

> Signed-off-by: Petr Lautrbach <lautrbach@redhat.com>


$ git log | grep lautrbach@redhat.com | wc -l
175

$ gpg --fingerprint lautrbach@redhat.com
pub   rsa4096/FB4C685B5DC1C13E 2024-11-04 [SC] [expires: 2026-11-04]
      Key fingerprint = 68D2 1823 342A 1368 3AEB  3E4E FB4C 685B 5DC1 C13E
      Keygrip = 834230A0854D7A8698B5432C007560FE7AECC504
uid                 [ultimate] Petr Lautrbach <lautrbach@redhat.com>
sub   rsa4096/C500C028A770AB66 2024-11-04 [E] [expires: 2026-11-04]
      Key fingerprint = 58E9 06B2 5680 15A7 91C8  D2EC C500 C028 A770 AB66
      Keygrip = 2EF1D48B43E234CAAE155A0AD032C00063FCB102
sub   rsa4096/CDCAE8C927C6BE31 2024-11-04 [S] [expires: 2026-11-04]
      Key fingerprint = 7200 EB2C 3F5E 4884 63C0  CE9E CDCA E8C9 27C6 BE31
      Keygrip = CAE3E6B80FFD15958C813CC635CFFDF9F86D9C17
sub   rsa4096/37BCD711A64B2890 2024-11-04 [AR] [expires: 2026-11-04]
      Key fingerprint = 832F CF4A 82B0 7F2A 51E4  3DDB 37BC D711 A64B 2890
      Keygrip = 850707DAF56607DEABD28933FD0A77D382923F1C

pub   rsa4096/BC3905F235179CF1 2022-10-26 [SC] [expired: 2024-10-25]
      Key fingerprint = B868 2847 764D F60D F52D  992C BC39 05F2 3517 9CF1
      Keygrip = FA0CE92171EEBAC2DD084E6399F18709A2F7353B
uid                 [ expired] Petr Lautrbach <lautrbach@redhat.com>




> %  gpg --fingerprint paul@paul-moore.com
> pub   rsa4096 2011-10-10 [SC]
>      7100 AADF AE6E 6E94 0D2E  0AD6 55E4 5A5A E8CA 7C8A
> uid           [ultimate] Paul Moore <paul@paul-moore.com>
> uid           [ultimate] Paul Moore <pcmoore@umich.edu>
> sub   rsa4096 2018-10-15 [E]
> sub   rsa4096 2018-10-15 [S]
> sub   rsa4096 2020-06-19 [A]
>
>> >>  * Nicolas Iooss, nicolas.iooss@m4x.org
>> >>    *  (GPG fingerprint) E25E 254C 8EE4 D303 554B  F5AF EC70 1A1D A494 C5EB
>> >>  * Jeffrey Vander Stoep, jeffv@google.com
>> >> --
>> >> 2.52.0
>
> -- 
> paul-moore.com


  reply	other threads:[~2026-01-08  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 17:40 [PATCH] SECURITY.md: add lautrbach@redhat.com gpg fingerprint Petr Lautrbach
2026-01-06 22:03 ` Paul Moore
2026-01-07 12:08   ` Petr Lautrbach
2026-01-07 20:18     ` Paul Moore
2026-01-08  8:57       ` Petr Lautrbach [this message]
2026-01-09 21:29         ` Paul Moore
2026-01-14 18:28           ` Petr Lautrbach
2026-01-14 20:55             ` Paul Moore
2026-01-15  8:00               ` Petr Lautrbach
2026-01-15 16:22                 ` Paul Moore
2026-01-15 17:01                   ` Petr Lautrbach
2026-01-15 18:30                     ` Paul Moore
2026-01-15 18:34                       ` Paul Moore
2026-01-15 19:29                         ` Petr Lautrbach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cy3kv5w2.fsf@redhat.com \
    --to=lautrbach@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox