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
82 points (100.0% liked)
Open Source
823 readers
21 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
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
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.
Even if they don’t I’m sure many others will
Well, yes. But let's say the OpenSSL developers copy new changes of source code to GitHub, and something goes wrong after the copying (Think of a malicious attacker breaking in and changes some code), then all the people copying from that one download link will be in the same boat as well.
Any official mirrors would sync the changes anyway, it’s automatic
Edit: Oh, I think I misunderstood your point. I agree that hosting the repos themselves would make it harder for randoms to maliciously introduce code
I was trying to say that if the OpenSSL developers upload new source code to only GitHub and something goes wrong, even for example simply a mistake or failure by GitHub, then other users wanting to download will not have to wait for the OpenSSL developers to repair that problem when OpenSSL project would for example have mirrors on Codeberg or sourcehut or their own git server, the latter which they intend to deprecate.
If they were to set up an official mirror it would be automatic, so I don’t think there’s any real way to avoid that problem with their current plan. But you’re right! Sorry for the confusion
n p
What is your definition of harder? I think bugs/breaches are even more likely on personal forges than github. Not that one should rely on github anyways...
I agree
I think "something goes wrong" is even MORE likely to happen on randomdude.com's insecure git forge
Codeberg and SourceHut are not really randomdude.com's insecure git forge. Both are doing development on their own services, and those services are not bad, like at all
Microsoft GitHub is riddled with bugs, is down at least once a month, & throttles non-Western IPs.
load more comments
(2 replies)
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.
Aren't they going to shut down their git mirror too, soon?
Well, I've took it to read it for myself on how they receive contribution, and it always need to be from github anyway unlike say Linux which accept email patches.
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.
OpenWRT was also using WolfSSL until October last year: https://openwrt.org/releases/23.05/notes-23.05.0#switch_from_wolfssl_to_mbedtls_as_default
That's a pretty bad idea. I highly recommend this awesome write-up by Software Freedom Conservancy: Give Up GitHub!
load more comments
(6 replies)
sorry i get all my software from download.com
Bad clickbait headline.