MAC is generally more complex than simple Unix permissions. Whether SELinux is more complex than AppArmour is more up to preference in my opinion

ACLs are pretty good and have come in handy for me multiple times

SRE here and I agree with you. I’m basically a glorified Linux admin lol

The very act of writing FOSS code is altruistic. Indeed, I’m looking at the big corporations when I point and say “thief!”.

Some companies do work that I like though. Mullvad is a prime example. Recently I’ve been looking at Nym and I like their ideas and work. I really liked that the big giants like Google and IBM collaborated for k8s. I believe Uber has done something wonderful for the FOSS community too but I don’t remember what it is. The fact is that they can if they try

I understand that if your boss tells you to write MIT/Proprietary code, you do so. I just wish that the ones who had a choice would use GPL

I understand. I can’t argue against wanting to earn money and be told to do something. I just wish that those that have a choice would take the extra minute to use GPL

Because most corporations do not contribute their changes back if it’s MIT/BSD licensed

Look, I understand if your boss tells you to not write Open-source/only use MIT so they can profit off of it later on. But for the people who have a choice, why wouldn’t they? I don’t see how it hurts their bottom line.

I’m middle class and here I am raging on Lemmy about software licenses LMAO

In this case, yes. If you were altruistic toward the community, shareholders could instruct devs to use it anyway so it works out for both groups. Doesn’t work the other way around

Sorry, I’m not much of a software dev so bear with me:

If the libraries are GPL licensed, is there a problem? Unless you’re editing the libraries themselves.

Now if the application is GPL licensed and you’re adding functionality to use other libraries, please push upstream. It helps the community and the author will more likely than not be happy to receive it

Exactly

Yeah I think it’s a much bigger pain on Android

I have and I’ve been left scratching my head both times. AppArmour just deals with files whilst SELinux has contexts - that’s the only operational difference I’ve needed to notice. I create custom policies and am on my way.

Exactly. I use setroubleshoot myself and it’s awesome.

I agree that creating custom policies for a bunch of apps day in day out will be tiring. But that is an argument against all MAC. I personally don’t want to see Linux going the way of abandoning MAC

I guess I can’t really fault that. Developers not interested in the license they use to publish code baffles me

What freedom in the sense of writing code does the GPL inhibit? GPL simply says that changes to the source must be published. MIT is just a scapegoat for companies to get stuff for free without helping the developer that’s giving their time and soul for it

Not using GPL or derivatives doesn’t force companies to publish changes (which are usually improvements) which harms the community

Do you feel that way about all MAC or just SELinux? AppArmour is similarly arcane when you’re in the zone configuring your application. TBH RedHat has troubleshooting instructions in their docs, I just Copts paste and edit as necessary and it doesn’t take that long. I guess I just spent more time at it

To be honest I had the exact same situation with AppArmor, and since then I have grown to like MAC. I know they’re doing it to keep me safe so I don’t complain. Honestly if people find MAC to be a hassle they should also in theory find file permissions and ACLs a hassle

SELinux is installed by default on RHEL derivatives like AppArmour is on Debian derivatives. Sure maybe it’s annoying to see a package you didn’t download explicitly but I still don’t see why it’s a big deal. I guess having to delve into SELinux in the middle of configuring another app will cause some pain