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.

Sign up for GitHub

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

Jump to bottom

Exploit mitigations applied by default are not documented #71098

Open
Shnatsel opened this issue Apr 13, 2020 · 0 comments
Open

Exploit mitigations applied by default are not documented #71098

Shnatsel opened this issue Apr 13, 2020 · 0 comments
Labels
A-security Area: Security related issues (example: address space layout randomization) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@Shnatsel
Copy link
Member

There seems to be no documentation on exploit mitigations in Rust, specifically:

  1. What exploit mitigations are supported?
  2. What mitigations are enabled by default?
    1. Is that answer different if building with cargo instead of rustc directly?
    2. Does that vary by platform?
  3. How to enable/disable specific mitigations?

This is relevant not only for security assessment, but also for performance comparison against other languages - both languages need to have the same exploit mitigations enabled for an apples-to-apples comparison.
@jonas-schievink jonas-schievink added A-security Area: Security related issues (example: address space layout randomization) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-security Area: Security related issues (example: address space layout randomization) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Shnatsel @jonas-schievink