3 ms·

Pretty clean shell script: https://github.com/keylase/nvidia-patch/blob/master/patch.sh https://github.com/keylase/nvidia-patch/blob/master/patch.sh Surprised

Pretty clean shell script: https://github.com/keylase/nvidia-patch/blob/master/patch.sh https://github.com/keylase/nvidia-patch/blob/master/patch.sh Surprised there are no protection/obfuscation methods against patching the `.so` in this fashion. No checksums, signatures, etc.

bravetraveler 2y ago
Give it time, the Bogeyman for this will be attestation and verified boot/data integrity+safety Took them a while to sort out BIOS mods/signing firmware. The irons are in the other fires. Not an endorsement, I got into computing because of the openness. I'm with Torvalds RE: nvidia
izacus 2y ago
That's because the target market isn't going to risk running this kind of patch. From my experience working on enterprise software, you just need something basic to curb the "oh, intern installed it and then we copied it to production" type behaviour. As soon as you have something that gets flagged to legal/managers you're good. Not worth going beyond that.