131–140 of 282 posts
Somehow "maintainability" has never been something I'd ever associate with Ubuntu. Is it a reference to their source tree? That'd make a lot more sense than if they were referring to the OS itself.
Earlier quoted context omitted.
What kind of free pass would you want to give to locally run software? Can't you already do anything you want to GPL code locally?
I think it is not that local code does not get a free pass by itself but the combination. By letting cloud services that use GPL software stay closed source it actively encourages development of cloud based tooling in a commercial context and users end up getting forced to sign up with and connect to a closed source cloud service they have even less control over than traditional locally running closed source software…
This is why AGPL was invented. You might use my AGPL code in your cloud service, but you need to provide the source code you are running to your clients. You are not allowed to keep any secret sauce secret from your users.
MIT and BSD (and plain GPL) don’t protect users again abuses like this.
What are the implications of the license not being GPL?
Earlier quoted context omitted.
What kind of free pass would you want to give to locally run software? Can't you already do anything you want to GPL code locally?
GPLv2 was fine. AGPL is fine. V3 is incompatible with selling bootloader locked software stacks (pretty much all consumer hardware these days). Concretely, I can’t do this local thing: Take GPLv3 software, build a board, link the software to vendor blob firmware (~ all current hardware requires this step), flash it to a ROM on the board and sell it to you with a copy of the GPLv3 software’s source code. I can take th…
Which is great. It prevents enshitification of consumer devices.
Earlier quoted context omitted.
Do you have an example of the logic bugs you're referring to?
I am pretty sure it is around here somewhere: https://github.com/trifectatechfoundation/sudo-rs/issues . I apologize, I do not bookmark these issues, but maybe I should start doing that? In any case, you will find logic bugs which may raise the question "is it really worth the rewrite?".
> Ubuntu is the most widely deployed Linux operating system Nitpicking, but I thought Android was the most widely deployed Linux OS around...
Android uses the Linux Kernel, but iirc (correct me if I'm wrong), it doesn't come with the required application to make it Unix and hence is not the Linux operating system. That would mean it's only using the same kernel as the Linux operating system? Idk, just speculating to maybe get the thought process
There's no "Linux operating system". Linux is the name of the kernel. Android is an operating system, GNU/Linux is, things like BusyBox/Linux are. They're all operating systems that use the Linux kernel.
Earlier quoted context omitted.
> 1) Would a hypothetical "sudo-lite" with these features removed lead to better security without a rewrite? OpenBSD did this with their doas utility: * https://en.wikipedia.org/wiki/Doas
"without a rewrite" means cutting down the existing code. A completely different program goes into the same category as "rewrite".
Next they should adopt uutils[1] as coreutils, findutils, diffutils, etc alternative. [1] http://github.com/uutils/
> This move is part of a broader effort by Canonical to improve the resilience and maintainability of core system components. Sudo-rs is developed by the Trifecta Tech Foundation (TTF), a nonprofit organization that creates secure, open source building blocks for infrastructure software. Ubuntu continuously updates itself without permission, killing apps and losing previous state. You have the Javascript based Gnome…
I think you mean a magic bullet instead of a smoking gun :)