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, 15 Jan 2026 18:01:58 +0100 [thread overview]
Message-ID: <87jyxi24jd.fsf@redhat.com> (raw)
In-Reply-To: <CAHC9VhQHrnkMO0JMtDyEnsmgMJisSU5bs76bzLYXGirc8uDYmA@mail.gmail.com>
Paul Moore <paul@paul-moore.com> writes:
> On Thu, Jan 15, 2026 at 3:01 AM Petr Lautrbach <lautrbach@redhat.com> wrote:
>>
>> "68D2 1823 342A 1368 3AEB 3E4E FB4C 685B 5DC1 C13E" is not a subkey.
>
> Okay, in this case you need to get this new key signed by other
> individuals trusted by the SELinux community before we can consider
> including it in the SECURITY.md file.
>
My idea was:
Before this patch my address was there without gpg fingerprint. It means
that I could be contacted directly via un-encrypted email.
The key I used in this patch was already used for SELinux userspace
release, public key is available at 2 different locations connected to
me - github (I'm part of SELinux organization) and
plautrba.fedorapeople.org (I'm a packager for 15+ years) and it's also
used in Fedora [1] and RHEL [2] - only Red Hat employees can push there and it
was me who pushed [3]. That being said I expected that the key is
already trusted due to all the records.
But I see your point. I'll send another patch which will remove my address from SECURITY.md
and when the key is signed, I'll return it back.
[1] https://src.fedoraproject.org/rpms/policycoreutils/blob/rawhide/f/bachradsusi.gpg
[2] https://gitlab.com/redhat/centos-stream/rpms/policycoreutils/-/blob/c10s/bachradsusi.gpg?ref_type=heads
[3] https://gitlab.com/redhat/centos-stream/rpms/policycoreutils/-/commit/02af42ef7ea24c279708ea83cc2698b738bdee8c
Petr
next prev parent reply other threads:[~2026-01-15 17:02 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
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 [this message]
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=87jyxi24jd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.