4 ms·
Shared libraries are the real difficulty. If your SSL library patches a security vulnerability, you generally want any program that uses that SSL library to be
by naasking 8y ago
Shared libraries are the real difficulty. If your SSL library patches a security vulnerability, you generally want any program that uses that SSL library to be immune.
- AnIdiotOnTheNet 8y agoNot a problem, something as fundamental as SSL should be part of the OS's provided library set that you can depend on being there so you don't have to include it in your self contained application. There's no reason to have all this complicated crap so that you don't have 2 copies of 200k libsomebullshit.so.
- scroot 8y agoIf you ever write a manifesto I think you should grab the libsomebullshit.so domain name
- AnIdiotOnTheNet 8y agoIf .so TLD wasn't so expensive I'd be tempted to do that.
- naasking 8y agoYou could argue the same about many other libraries, like all of the basic data structures and algorithm libraries, string libraries, time and date handling, nowadays machine learning, etc.