Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nope.

1. That link is dead ("Access Denied")

2. The bug is not in Devuan, it's in something called refractainstaller, which is used for Devuan live-ISOs. If you just install Devuan that doesn't happen.

3. With a refractainstaller live-ISO, and if you chose to not define a root user, then this bug manifests.

The bug seems to have lingered for so long because despite being rather obvious (i.e. you can just become root) because nobody tried to secure a live-ISO-based system, which is something you typically use as a "rescue disk" or to diagnose hardware.

So - is this a screw-up? Yes. Does it reflect significantly on Devuan as a project? Not really.

To draw a parallel - the fact that systemd has had bugs which other init systems didn't, or had gotten over decades before, does not mean it's an undesirable project. My (and many people)'s problems with systemd regard its fundamental design philosophy, as well as its governance/behavior as a software project.



>1. That link is dead ("Access Denied")

Works for me.

>2. The bug is not in Devuan, it's in something called refractainstaller, which is used for Devuan live-ISOs. If you just install Devuan that doesn't happen.

From the link:

>>When you download and install the desktop-live Devuan image, you will be prompted to create a user account at the end of the process.

... ie it seems to be talking about the normal process for installing a Linux distro - you make a live CD, boot it, and run the installer.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: