Fedora 30 Release Readiness meeting
by Ben Cotton
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30
Release Readiness meeting. This meeting will be held on Thursday,
2018-04-25 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the release
of Fedora 30. Please note that this meeting will be held even if the
release is delayed at the Go/No-Go meeting on the same day two hours
earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/meeting/9514/?from_date=2019-04-22
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
5 years, 1 month
sshd defaults in server
by Chris Murphy
Hi,
I ran into this "fun" hack
https://news.ycombinator.com/item?id=19642554 and I'm wondering
whether it'd be a good idea for F31 to ship with:
#AllowAgentForwarding no
#PasswordAuthentication no
Cockpit provides an interface to add SSH public keys for a while now.
However the installer doesn't require creation of an admin user, it's
an option.
Related to that, I'd like to see the installer:
a. Require creation of a non-root user with "Make this user
administrator" checked by default
b. Root user has "Lock root account" checked by default
When I check "lock root account" and return to the installation
overview, it shows for root user that logins are disabled, so it's not
like the person doing the install has to go dig around for the fact
root user will be disabled. And they can easily uncheck it and set a
password.
Any thoughts?
--
Chris Murphy
5 years, 1 month
