| Summary: | "ENABLE_SULOGIN" in msec should modify the file /etc/sysconfig/init | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jean Michel Varvou <jeanmichel.varvou> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | cazzaniga.sandro, dmorganec, doktor5000, mageia, stormi-mageia, thierry.vignaud, tmb |
| Version: | 2 | Keywords: | Junior_job, PATCH, Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | http://www.mageialinux-online.org/forum/topic-13186+mageia-et-le-mode-degrade.php | ||
| Whiteboard: | |||
| Source RPM: | msec | CVE: | |
| Status comment: | |||
|
Description
Jean Michel Varvou
2012-07-21 17:42:33 CEST
In the file /etc/inittab after the comment # Single user mode do you see something ? Source RPM:
(none) =>
msec Hello ENABLE_SULOGIN to NO # Single user mode ca::ctrlaltdel:/sbin/shutdown -t3 -r now ENABLE_SULOGIN to YES # Single user mode ca::ctrlaltdel:/sbin/shutdown -t3 -r now ~~:S:wait:/sbin/sulogin ok so msec seems ok ihmo, more in the basic level maybe Any ideas thomas or colin ? CC:
(none) =>
mageia, tmb Note that under systemd in mga2 that /etc/inittab is no longer used so it's irrelevant. Check /etc/sysconfig/init and see what the SINGLE= variable says. This should be what controls what is used for login in failsafe mode. I'm not sure that things work nicely anyway as I'm pretty sure there was/is a problem with sulogin anyway. Note that all this stuff is just fake security anyway... just boot with init=/bin/bash and you'll see why. Unless you lock down the bootloader to prevent this, this approach bypasses any security anyway. If you are going to the effort of locking down the bootloader then whey are you still providing a failsafe option at all in the first place? :) Hello By default, in /etc/sysconfig/init, we have SINGLE=/sbin/sushell . If we change to have SINGLE=/sbin/sulogin, the password for root is required when we start in single user mode. Well done Colin!
Manuel Hiebel
2012-07-22 15:29:29 CEST
Component:
Security =>
RPM Packages seems it was not imported in our svn, http://svn.mandriva.com/viewvc/soft/msec/trunk/src/msec/plugins/msec.py?revision=270437&view=markup Keywords:
(none) =>
Junior_job Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. Keywords:
(none) =>
PATCH, Triaged This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |