Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make PIE building/linking mandatory #48

Open
TheAssassin opened this issue Nov 28, 2024 · 2 comments
Open

Make PIE building/linking mandatory #48

TheAssassin opened this issue Nov 28, 2024 · 2 comments

Comments

@TheAssassin
Copy link
Member

Future runtime types must be linked as PIE. Current ones should. This allows the kernel to apply ASLR and makes the runtime compatible with tools like https://github.com/io12/userland-execve-rust.

@probonopd
Copy link
Member

Please elaborate the motivation for this. Especially why you think it should be a "must".

@TheAssassin
Copy link
Member Author

See AppImage/type2-runtime#88 for additional context. Using PIE is an advantage security wise (it allows the kernel to apply ASLR, non-PIC code cannot be loaded that way). Also, it allows the runtime to be launched via https://github.com/io12/userland-execve-rust, which is a convenient way for tools like AppImageLauncher to launch statically linked runtimes while bypassing binfmt_misc. It doesn't cost anything either and should be possible with any modern compiler toolchain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants