On Fri, Jun 19, 2026 at 12:20:17AM -0400, Neal Gompa wrote: > On Fri, Jun 19, 2026 at 12:15 AM Kevin Fenzi <[email protected]> wrote: > > > > On Fri, Jun 19, 2026 at 03:22:51AM +0000, Gary Buhrmaster wrote: > > > On Thu, Jun 18, 2026 at 9:01 PM Kevin Fenzi <[email protected]> wrote: > > > > > > > So, we can surely change the requirement to be MUST (and we probibly > > > > should), but there's a bunch of corner cases and things to note: > > > > > > (is that a "should" or a "MUST" (ha ha)) > > > > > > SHOULD was best the community would seem to accept > > > at the time due to some strong objections to a MUST. > > > > :) > > > > > > The new ssh keys that use fido2/etc won't work against > > > > src.fedoraproject.org because it's RHEL8 and doesn't understand them, > > > > but we could perhaps setup some requirement for the new forgejo setup > > > > to need them. > > > > > > Is there any resourced plan to upgrade to a RHEL that > > > supports the ssh FIDO2 encryption types? I would love > > > to migrate to a FIDO2 required ssh key (and while I am > > > not a PP, so am probably not a major risk to the > > > community, I like to believe I take security seriously). > > > > Yes, by migrating src.fedoraproject.org away to forgejo. > > > > Does that mean you have working SSH support for foregejo?
You mean forge.fedoraproject.org? Not yet, but I have been working on it and I think we are close... For the src.fedoraproject.org forgejo version we should likely be able to re-use the same setup (just with different ips,etc). kevin -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
