Hi Maintainers;
Not sure if I have my terminology correct, but in my researches into how to link extra functionality into a custom ld.so (copy protection, encrypted elf files, license verification.), . I saw a post by one of the maintainers (lost reference) that it was being considered to strip libc functionality support from ld.so. PLEASE DO NOT DO SO. My application (custom loader ld-so, working, in alpha trial) depends on having basic libc functionality in ld.so and, I am sure, as we all become more security conscious, part of the solution is adding functionality to ld.so If you are determined to do so, suggest it be consolidated into one place and removed by conditional compile, so it can be used by those who require it. It is my intent to license this copy protection technology Particulars: X86_64, eglibc-2.19 ELF files are protected (no changes to source or build process) Each license consists of RSA license and personalized ELF file, delivered by network upon user request at discretion of license server Public / Private encryption Time Limited (trial licenses) Full license Locked to hardware (licensor choice) Local and / or network license server license verification License server creates / distributes / verifies licences, maintained in SQL database Thanks; Bill Ross Rossbcan UKNOWWHAT gmail.com
