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

Research: Delay-loaded DLLs for saner self-sandboxing #28

Closed
MaulingMonkey opened this issue Sep 5, 2022 · 1 comment
Closed

Research: Delay-loaded DLLs for saner self-sandboxing #28

MaulingMonkey opened this issue Sep 5, 2022 · 1 comment
Labels
research Possibly important investigations

Comments

@MaulingMonkey
Copy link
Owner

Use cases:

  • Have a single binary with both a UI component, and a low/untrusted launch token, without breaking user32.dll.
  • rustc 1.63.0 std init with lower token?

References:

@MaulingMonkey MaulingMonkey added the research Possibly important investigations label Sep 5, 2022
@MaulingMonkey
Copy link
Owner Author

This is mostly a matter of using the right build.rs settings. This repository's build.rs contains an example.

Importing firehazard just for some lousy build.rs println!s seems a bit much / overkill. I could add a second crate for querying linker setting availability or something? But given the need for vaguely adjacent settings to be copy+pasted to live in .cargo/config.toml, that seems like overkill - examples should suffice, and I kinda have those already.

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

No branches or pull requests

1 participant