Redhat were very successful with the open source, but paid support model, so it could happen.

Inertia would be hard to overcome, anyone using sales force right now is probably not gonna want to risk a newcomer.

Isnt that exactly what minikube is? Kubernetes in docker.

I’ve used docker-in-docker images, but its usually not fun.

Looks like Test Driven Development + AI.

Hopefully the AI doesn’t get lazy and churn out huge if/else chains to pass the tests :D

You use a console? Noob… Magnetised needle is where the real productivity is at.

I was under the impression the latest “firefox” package was a kind of “meta” package that caused the snap to get installed instead.

Certainly seems that way according to: https://packages.ubuntu.com/search?keywords=firefox

Note that 22.04 is described as a transitional package to snap.

Apt does use debian packages (.deb files), but on ubuntu it uses ubuntus repositories.

Correct me if I am wrong, but apt-get install firefox installs the snap version unless you go out of your way to fix that?

You are correct. Ill add an edit. Thanks!

Those are all hardware management services (as far as I can tell), and are configured before the root is mounted.

I have hit this exact error before, that is what failing to mount the root disk looks like. A bunch of services will start, and then you get dropped into a shell (with a login).

If you want to see it for yourself, change /etc/fstab such that /root is now pointing to the wrong device, and then rebuild your initrd. When you reboot you’ll see exactly that output. To fix it, login to the shell and mount your root on /new_root, and ctrl-d to continue the boot (from memory it has a message telling you to do that anyway). When your system boots you can fix fstab and rebuild initrd. Its reversable, but maybe test on a machine you dont care about to be safe :)

Easy then, buy a new one for you, give the old one to your friend :)

I wasnt really joking either, the upfront costs might be higher, but longer term will be cheaper than a cloud service. And hopefully more secure.

I think you can detect when your in a VM, not sure exactly how though. But they could even be checking for other environment factors, like network addresses, system language, or timezone details.

Buy another NAS and run it at a mates house? If your house burns down hopefully theirs is fine?

It is actually a boot failure. Normally the kernel reads some config from the initrd (the bootloader loads initrd and passes it to the kernel - thanks dan) and then does a bunch of setup stuff, and then it mounts the actual root filesystem, and then switches to using that. In this case, the root filesystem has failed to mount.

Hardware failure is most likely the cause, but misconfiguration can also make this happen. Probably hardware though.

If its misconfiguration, an admin can reattempt to mount the root drive on /new_root, and then ctrl-d to get the init system to try again

ELI5: couldnt open C:/ drive

Edit: clarified what loads the initrd - as per dans comment.

Yup, there is a lot of prior art on how to get this wrong :(, and I dont know of any good solutions either. Curation and moderation are probably the best case, but arent bulletproof either.

I raised this not to kill OPs project, but to make sure they go into it eyes open. I personally would be very uncomfortable if my website was being abused to distribute malware, so they deserve to at least be aware of the risks.

Very understandable. And from a security standpoint not necessarily indicitive of anything. A good malicious script would just check its environment first.

Have you considered some form of CI? I.e: Spin up a VM, run the script, reboot, report what changed? Might be a little expensive, but could help auditing?

You have probably invested a lot of time and effort into this, so please take this as constructive criticism.

Your security systems are probably not going to be sufficient, for a whole number of reasons.

Script Voting

The general public is not able to appropriately audit shell scripts. This extends even to sysadmins and more technical people. The people who can properly audit scripts are a minority, and they may not even be amongst your user base. Anyone who gets a script that “does its job” is going to upvote it as fine, because they may not even be aware of its malicious side effects.

Scripts will naturally need to evolve over time, so script updates will be a normal part of your system. Will the votes reset for new versions? Is there anything stopping someone uploading farming votes with valid scripts, and then backdoor the script once it gets sufficiently popular?

Is there any form of vote manipulation prevention planned? If not, bad actors can create an army of accounts and upvote their malicious content. Can you remove a users votes if they are found to be acting maliciously? Will it even be possible for you to tell the difference between a naive user who doesn’t understand the maliciousness of the script, versus an account actively increasing the rating of a bad package?

User Reputation

This seems easy to game as well. Upload a host of valid scripts, gain reputation, and then when ready, upload malicious scripts.

Collaboration

Allowing non-maintainers to edit and upload scripts seems like a wildly bad idea. There must be some level of maintainer approval for that right? Still will have the same issues, easy for someone to build trust on a script repo and then exploit it when it suits them.

None of these issues are unique to your site, pypi, dockerhub etc have all hit these issues in the past.

I think the only real answer is to have very strong human moderation, but I fear that if your site takes off, the workload will rapidly spiral out of control. Otherwise, interesting idea, Good Luck!

In a healthy democracy, the second part of voting would come into play: You contact your local representative, and tell them what you want them to do. If enough of a representatives constituents directly voice their disapproval, the representative is forced to act, or else lose those voters. Its essentially lobbying, but leveraging your vote directly.

The caveats of course are that it doesnt work well for minorities, and you need a healthy functioning democracy, so, your mileage may vary :(

My experience is Australian, but given we have weaker laws than you, its probably the baseline experience.

If your bot is a very small bot, for personal use, no. But once you go over 75 servers, discord will require you to submit both a privacy policy and a terms of service.

They dont seem to care about the content of the docs, they just have to exist. There are tools to generate both docs. They serve a very different purpose to a licence, so that is not sufficient.

Poor thing. Wait until they learn what a single python did to humanity.

I’m using seafile, and you just gave me flashbacks to the CSRF nonsense. Dont remember how i fixed it unfortunately.

I dont understand why nextcloud is so slow. I tried it out recently and its just so slow to upload files. Good to know owncloud is better, but might wait a little while before I try that out again.