It’s not that there isn’t a license, there is, but the license says there is no license, it’s public domain, do whatever you like. It’s not a problem if your license says that there is no license, but yes, it is a problem if you don’t have any license attached to your code. In those cases, yes, most distros don’t touch that code… or maybe point at the project, but do whatever you deem is right with it, we’re officially not touching it.

You’re your own worst enemy 🤷…

Cuz I found it on reddit.

Yeah, it might be a good idea to embed the cabox.moe link and share the archive.org link in the comment.

Arch nemesis… only Arch users have those.

Oh, didn’t know that meaning 😁.

What might those edge cases be? Unlicense literally says there is no license, do whatever you want.

And beer.

It means whore.

Here’s the direct link: https://web.archive.org/web/20241006015615/https://files.catbox.moe/deetxa.mp4

I just chose it because I really don’t care about that. It’s my own personal repo for Void, but if anyone wants to use it, that’s fine, use it however you like.

IDK if CC is available on GH from the drop down menu, I know Unlicense is… it was the fastest way to say “I really don’t care what you do”.

I actually don’t care to be honest.

Oh, yeah, you’re right. I thought USB 3.x had Thunderbolt specs, not 4.

No prob 😊.

My point was, it flopped as a standard. It’s not that it’s good or bad, it’s just not used any more, there are no new devices with FireWire. USB killed it essentially. The same will happen with Thunderbolt, USB 3.x will kill it.

I seriously doubt there will be something that will replace USB. It’s backwards compatible to oblivion and just supports newer and newer things. It’s very hard to beat that.

If by maliciously you mean a virus might take advantage of the system in those 5 minute, the answer is, yes, it is possible… not likely, but possible.

If the question was, can the shell by itself escalate a command that does not have sudo in front of the command, the answer is no. If it did that, than there are some serious bugs in the code… or some malicious code planted in it. By definition, it’s not supposed to do what you don’t tell it to do.

So that is why I always have to install sudo manually 🤦.

And I think older versions also left you at root, you had to define a user account manually. I think that’s not the case now as I recall (I haven’t installed Debian in a while).

It’s challenging, big place, big problems. Managing the whole thing is the hard part, especially when you’re on a budget.

But, to be honest, that’s about it. It’s getting boring for me after 5 years there. I was thinking about quitting and moving abroad.

Sorry (again 😂, this happens quite a lot with you, lol), it’s early in the morning here, didn’t have my coffee yet.

If the question is can privileges be escalate later on while a command or a script is executing, the answer is yes. You can also deescalate them once the root creds stuff is done executing. You just have to make it clear in the script or the command that “you do this with root creds, but then you continue with user creds”.

The point I was trying to make with my previous comment was that, if a process (command, script, whatever) is ran with root privileges, every program, command, script it invokes later on is ran with root privileges, unless it’s specifically noted to run this or that part with some other privileges.

They just don’t wanna port it to Linux… it’s basically that simple.