On 2 April 2014 17:15, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Wed, Apr 02, 2014 at 02:12:50PM -0400, Simo Sorce wrote:Posting here is a good start. You can also add a note in the FESCo ticket
> How does someone express strong disagreement to this change ?
for approval once one is filed, and if you are incredibly passionate you can
come to the FESCo meeting (although I'm hoping we can make those meetings
more efficient, so that's not a good place for back and forth -- if possible
we should work out the issues before the meeting).
I haven't seen a ticket listed and the wiki entry does not mention one. I personally think it is a bad default having had to deal with this from people who did this with the old Bastille scripts and choosing the equivalent to SECURE EVERYTHING without knowing exactly what that idd no matter how many "Do you really want to do that?" popups. While it sounds like a useful task, it basically requires a bad sudo file and you are now having to use very complicated rescue steps to get back into the box (and if you added other things.. maybe not even that.)
> This change makes it very hard to do necessary maintenance. I canI assume that it's for a kiosk or public (or at least managed) lab
> understand blocking SSH login as root with password by default, but I do
> not understand what is the point of blocking console login as root.
situation. It makes sense for that, but I'm not convinced of a benefit
otherwise, and I don't think that situation is the default....
--
Matthew Miller -- Fedora Project -- <mattdm@xxxxxxxxxxxxxxxxx>
"Tepid change for the somewhat better!"
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Stephen J Smoogen.
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
