899
top 50 comments
sorted by: hot top controversial new old
[-] stoy@lemmy.zip 2 points 23 minutes ago

This has nothing to do with security, and everything to do with liability.

You can't really sue an open source project using a proper license, they disclaim any liability or warranty, meaning the buck stops with you.

If you hire a software development firm and pay for them to build software for you, you will have a different license, the software company can just repackage open source software into their own UI and branding, take the money and declare bankruptcy if their customers try to sue them.

The customers are mostly happy, they get to tick the box that they have a support contract for the software and a company is liable if shit hits the fan. The software development company is happy, they get money for doing very little actual work.

The open source project probably doesn't know about the abuse of the license and thus mostly doesn't care.

[-] Rai@lemmy.dbzer0.com 15 points 4 hours ago

My org told me “you can’t install open source software”

Everyone uses Firefox

I just want OpenShell

[-] TootSweet@lemmy.world 17 points 5 hours ago* (last edited 5 hours ago)

Honestly, a policy of "no free-of-charge software installed on workstations except FOSS" might improve security a bit and probably without doing all that much damage to the day-to-day workings of the company.

For that matter, if my employer instituted a policy of "no software except FOSS", my own particular job probably would be a surprisingly small adjustment. As long as they were willing to do the work to set up infrastructure and/or let us switch to FOSS alternatives that require third-party server providers as necessary. About all I can think of that's installed on my work machine that's proprietary is:

  • Zoom
  • A paid corporate VPN client
  • A random program that I use to authenticate to Kubernetes clusters in use where I work (so I can use Kubectl)
  • Chrome
  • The Client Management software my company uses (the software they use to remotely administrate the company-provided machines -- force install shit without telling you, spy on you, nag people who have computers that aren't actually used to return them, wipe your computer if you report it stolen, etc)
  • And, of course, bios, proprietary firmware blobs, etc

Beyond that, I honestly can't think specifically of anything else proprietary installed on my work machine. My personal computers have far less proprietary software installed than the above list.

[-] derpgon@programming.dev 3 points 5 hours ago

Not related, but did you ever use k9s? Quite nifty CLI tool to control Kube, albeit not on a very advanced level, it helped me a lot to not get drowned in Kube commands.

[-] ashenone@lemmy.ml 40 points 10 hours ago

Every day I wake up I thank God I'm not an MBA 🙏

[-] lka1988@sh.itjust.works 5 points 2 hours ago

Sometimes I wish I was a piece of shit so I didn't need to worry about money.

[-] Flax_vert@feddit.uk 9 points 8 hours ago

MBAs would just buy an LLM software subscription to fix it

[-] ChickenLadyLovesLife@lemmy.world 7 points 9 hours ago

"This fucking paycheck! What am I going to do with all this money?"

[-] QueenHawlSera@sh.itjust.works 27 points 10 hours ago

Everyday my misnathropy is justified

[-] ChickenLadyLovesLife@lemmy.world 25 points 9 hours ago

I majored in Anthropology in college. I should have done Misanthropology.

[-] InternetCitizen2@lemmy.world 5 points 4 hours ago

You did; just need to apply it.

[-] ChickenLadyLovesLife@lemmy.world 8 points 4 hours ago
[-] InternetCitizen2@lemmy.world 6 points 4 hours ago

They grow up so fast sheds tear

[-] Vanilla_PuddinFudge@infosec.pub 8 points 8 hours ago

Print the fucking t-shirt man. I'll buy one for every day of the week.

[-] psmgx@lemmy.world 23 points 10 hours ago

It's not more secure, it's so they can offload blame and have people to sue if/when something ugly happens. Liability control, essentially.

We had to pay for fucking Docker container licenses at my last job because we needed an escalation to the vendor in case our SMEs couldnt handle things (they could), and so we had a vendor to blame if something out of our control happened. And that happened: we sued Mirantis when shit broke.

[-] brbposting@sh.itjust.works 1 points 56 minutes ago

Hey PS: search engines do return a result for a suit against that company so potential self-doxxing territory (but maybe you’re open in your comment history IDK)

(Don’t have a PACER login so couldn’t tell what was up with the suit that came back when I checked this morn, also could’ve been an unrelated suit)

[-] brbposting@sh.itjust.works 5 points 8 hours ago

Ever hear how the suit turned out, generally?

[-] psycho_driver@lemmy.world 23 points 12 hours ago

Don't forget your new 32 character/symbol/number/nordic rune passwords that will need to be changed every 17 days.

[-] AllHailTheSheep@sh.itjust.works 14 points 9 hours ago

I hate sites that make me constantly change passwords. it's been shown time and time again that making users change passwords often decreases security by a pretty large factor, and yet a lot of sites still do it

[-] MrsDoyle@sh.itjust.works 10 points 8 hours ago

Our workplace did that. You had to change every month and you weren't allowed to just add a digit. It meant that people started writing their passwords on post-its stuck to the monitor.

Mind you, back in the 90s your password was the same as your username. It was very handy, because if someone went home leaving a document locked, you could just log in and unlock it. Our first "proper" IT professional was horrified.

[-] brbposting@sh.itjust.works 7 points 8 hours ago

Interesting, stopped seeing this a while back. Forced change after the inevitable hack though of course

[-] Object@sh.itjust.works 6 points 8 hours ago

Could be because OWASP now actively recommends against periodic password changes.

Ensure credential rotation when a password leak occurs, at the time of compromise identification or when authenticator technology changes. Avoid requiring periodic password changes; instead, encourage users to pick strong passwords and enable Multifactor Authentication Cheat Sheet (MFA). According to NIST guidelines, verifiers should not mandate arbitrary password changes (e.g., periodically).

[-] wolframhydroxide@sh.itjust.works 3 points 8 hours ago

And don't forget required 2-factor authentication, in an age where that becomes 1-factor authentication as soon as someone has your phone, because both factors are accessible there!

2FA is utterly worthless in the age of smartphones, and whenever my employer tries to implement it, I refuse and tell them that, if they want me to do 2FA, they can either provide me with a work phone, or they can give me a USB key that is just going to sit in my desk drawer.

[-] a_wild_mimic_appears@lemmy.dbzer0.com 4 points 8 hours ago* (last edited 8 hours ago)

which still requires someone to swipe the phone and the owner not recognizing it long enough to do a remote wipe. I am not someone who hangs on the smartphone 8 hours per day, and even i would realize my phone is gone within 15 - 30 minutes, giving an attacker a pretty small time window to act.

e: and they have to break into the phone as well - if it's updated, that might buy more than enough time

[-] shalafi@lemmy.world 36 points 13 hours ago

My last boss got rid of the pfSense routers because "open source is not secure". I argued that pfSense has been vetted over and over and over again. Nope. "Everyone can see the source code." That's the fucking point!

TBF, pfSense isn't the fastest routing, but at our small company is was more than sufficient.

[-] MehBlah@lemmy.world 16 points 12 hours ago

For a small to medium sized business pfsense is the only solution that makes sense. The only requirement is that you have a actual sysadmin on staff and not a vendor jockey.

load more comments (6 replies)
[-] Sylvartas@lemmy.dbzer0.com 46 points 14 hours ago

There is an entire sub-industry and probably thousands of jobs being propped up by this stupid way of thinking about software. I can't be mad at it because it pays the bills for a few of my friends...

[-] Landless2029@lemmy.world 18 points 13 hours ago

I could really see companies just fork open source and give it a tweak like UI or new switches...

Terrible.

[-] Flax_vert@feddit.uk 3 points 8 hours ago

New wealth redistribution method?

load more comments (5 replies)
load more comments (1 replies)
[-] daggermoon@lemmy.world 7 points 10 hours ago

This pisses me off

[-] frezik@lemmy.blahaj.zone 108 points 16 hours ago

It's "more secure" because there's a specific company to blame when it goes wrong.

[-] DarkDarkHouse@lemmy.sdf.org 91 points 15 hours ago

Security through liability

load more comments (1 replies)
load more comments (12 replies)
[-] DickFiasco@sh.itjust.works 53 points 15 hours ago

Worked for a company that had a similar policy against free software, but simultaneously encouraged employees to use open-source software to save money. I don't think upper management was talking to the IT department.

load more comments
view more: next ›
this post was submitted on 27 Jul 2025
899 points (98.9% liked)

Greentext

6835 readers
1216 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 2 years ago
MODERATORS