Good idea, giving Microsoft control over every single open source project. I mean, what could go wrong, right?
this post was submitted on 02 May 2024
114 points (95.2% liked)
Open Source
31218 readers
26 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
Yes, what would possibly go wrong ? And OpenSSL is only a small and unimportant project and hardly anyone depends on it, right ? Right ? I can dig that they want to get rid of some of their own services but completely giving up on their own git repository ? Let's hope they do mirror the source code on Codeberg or sourcehut.
I'll mirror it on my selfhosted git. Just hit me up when you need the files lol
😀
I’ll put it up as a torrent soon
Read-only github mirror with read/write on a personal forge seems like one possible approach to make it more accessible/friendly without giving up any control to MS.
These were great in their day, but it’s time to move on to something better and safer.
How is it "safer" when contributing to the codebase or filing and discussing issues will now require creating an account and giving up personal information to one of the most privacy-invasive tech companies in the world? 😳
Agreed!
You are mistaking contributing and distributing.
Edit to clarify: The blog is strictly speaking about the means of distributing the release tarball. Distributing the release tarball has nothing to do with how contribution is accepted or how issue is handled. What they say on the blog is also very clear IMHO and for a good reason. Maintaining infrastructure takes work. Works that if you didn't do it right can be an attack vector. Do you guys remember xz? Do you read how the vulnerabilities came to be? Maintaining a single source of truth for the release tarball can help mitigate that. If one malicious actor can control even one of the distribution channels of the release tarball we get xz 2 electric boogaloo.
This announcement is just downloads which will continue to be available anonymously.
What the absolute fuck...
I think a lot of people here read the headine and think OpenSSL is moving everything to github and giving up everything else. It is not. They only moved the means of distributing the release tarball to github and stopped supporting the ftp and rsync. Do not confuse distribution and contribution/development.
Considering the absolutely devastating performance hits 3.x brings (and the apparent design failures that make it extremely difficult if not impossible to reclaim it) I wonder if openssl's days are numbered. WolfSSL seems to be favorable to the HAProxy team. Hopefully that can get some traction.
Good that you mention WolfSSL and that HAProxy team seems to like it. Years ago some Linux distributions made the switch to LibreSSL, but unfortunately that all (?) seems to have failed.
That's a pretty bad idea. I highly recommend this awesome write-up by Software Freedom Conservancy: Give Up GitHub!
sorry i get all my software from download.com
Fuck that... I guess we really should go with LibreSSL after all.
Speaking of, what is its current working state?
I'll take anything that has a compatible command line and library to be honest
Except ffmpeg/libav. I will always want the real ffmpeg 😤
I’ve also seen WolfSSL mentioned, which is HAProxy’s go-to. I haven’t played with it in depth myself though.
Federated Forgejo seems ideal.
I didn't think they had federation working yet? And forgefed/vervis isn't ready yet either.
I doubt many of the commentators here used any of the deprecated methods to contribute to openssl.
It's one thing to talk about what's good for open source, it's quite another to practice it.
I doubt many commenters here have used a wheelchair ramp to access a public building. Guess we should just remove all those ramps since that accessibility doesn’t affect them. The barrier to entry for setting up a wheel chair ramp is more expensive than offering at least one non-corporate code contribution method.
Your analogy would fit if the deprecated methods didn't have a higher barrier to entry than using GitHub.
This is less like removing the wheelchair ramps and more like removing the steps at the back of the building.
Maybe. Maybe if the back steps required an account with a US-based service owned by a publicly-traded megacorporation that is collecting your data as per the ToS just to enter. That’s a helluva barrier that should never be expected for free software.
And yet no actual contributor to openssl is losing sleep over this.
Weird and worrying choice
Bad clickbait headline.