- cross-posted to:
- apple@lemmy.zip
- apple_enthusiast@lemmy.world
- cross-posted to:
- apple@lemmy.zip
- apple_enthusiast@lemmy.world
You must log in or register to comment.
TL;DR? > The problem is strictly speaking not even in curl code. It comes with the version of LibreSSL that Apple ships and builds curl to use on their platforms.
But because they’re Apple (right next to the Pope, for infallibility), they know best; same old story, rinse’n’repeat.
Really liked their stuff back in the day. Now? It’s another walled garden they scrabble to maintain.
You know, Steve Jobs used to be a huge jerk. Then he passed away.
Thank you Piped bot.
What day was it that you liked their stuff, and what made you stop?
Apple adheres to the principle of form over function, instead of the old but still valid form follows function design principle. But TBH I never liked their stuff or their over the top big cheese attitude. So it’s not a disgruntled apple user writing this.
Okay? Thanks for your… participation?
LibreSSL is the fucking bane of my existence at work. So many issues caused by the keys it spits out vs others.
Never had the chance to seriously look into libressl. Do you think it would work fine if most of the world was running it rather than openssl?
Probably so, but Apple is the only one I’ve encountered actually using it. The whole point is it’s supposed to be backwards compatible and it’s just not
If you meant that they’ve dropped plenty of openssl functionality - well, the whole purpose of the fork was to refactor it into something less scary. And since it was done by OpenBSD people - they have their own approach, not always culturally compatible with enterprise usage.
You can follow curl’s lead developer on mastodon: @bagder@mastodon.social, seems like a very reasonable guy.
