Re:32-bit x86 Position Independent Code – It's That Bad
by danieldk on Wednesday April 15, 2015 @03:10AM
(#9379335)
IOW, it's tricky to guarantee that your software will work flawlessly across all the incarnations of CentOS 6.x,
It's not so tricky, since Red Hat specifies nowadays what guarantees can be expected for what packages:
https://access.redhat.com/articles/rhel-abi-compatibility#Ap...
Re:32-bit x86 Position Independent Code – It's That Bad
by pjc50 on Wednesday April 15, 2015 @04:36AM
(#9379590)
Dynamic linking is required for anything resembling a plugin architecture (such as PAM).
Re:32-bit x86 Position Independent Code – It's That Bad
by wtbob on Wednesday April 15, 2015 @08:06AM
(#9380342)
Not really—one could use processes and some form of IPC (shared memory, pipes, whatever). The efficiency could be pretty bad, but the safety and reliability could be better.
Re:32-bit x86 Position Independent Code – It's That Bad
by JoachimSchipper on Wednesday April 15, 2015 @09:52AM
(#9380934)
In fact, OpenBSD delegates logins to a login_<foo> binary, e.g. http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/.... That works. OpenBSD's system is not as flexible as PAM, with the attendant upsides and downsides.
That said, I'd like to point out that it is convenient for the developer - since customers are ultimately interested to know if your software is vulnerable, and you'll have to explain how the vulnerability affects it -.
It's also a double edged sword: openssl has a good ascending compatibility record, but that can't be said about all user space libraries. IOW, it's tricky to guarantee that your software will work flawlessly across all the incarnations of CentOS 6.x, if you have a lot of external dependencies, for example.