Ask HN: What rabbit hole(s) did you dive into recently?

Re:Ask HN: What rabbit hole(s) did you dive into recently? by rapjr9 on Tuesday April 23, 2024 @05:46PM (#40137722)

This sounds like it would benefit from modifications to linkers to make decomposition easier. The benefits of code reuse might make it worthwhile, although the security implications of code reuse without having any idea of what's in the code seem formidable.

[ Parent | on HN ]

Re:Ask HN: What rabbit hole(s) did you dive into recently? by boricj on Wednesday April 24, 2024 @05:28AM (#40142285)

Some linkers can be instructed to leave the relocation sections in the output (-q/--emit-relocs for gold/mold), but it's extremely unlikely that an artifact you would care about was built with this obscure option.

I'm mostly using this delinking technique on PlayStation video games, Linux programs from the 90s and my own test programs, so I'm not that worried about security implications in my case. If you're stuffing bits and pieces taken from artifacts with questionable origins into programs and then execute them without due diligence, that's another story.

[ Parent | on HN ]