-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Amazon "Application Security Best Practices" Alert Firing #47345
Labels
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
What does |
Ok, yeah, it's marked as requiring an executable stack:
A rust-built cdylib doesn't have one, so it seems like this is being injected by the postprocessing? |
I think it may be as simple as just telling the linker to not set the execute bit:
|
pietroalbini
added
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
Feb 6, 2018
Not our bug, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
For a few years, users have been reporting that libskylight.so, a compiled Rust binary, is triggering an Amazon "Application Security Best Practices" inspection with a "High" severity.
The issue is tracked on our tracker but we've not had great luck tracking down the source of the problem.
We're using Cargo to compile a
staticlib
, and then turning it into anso
with a bit of postprocessing viagcc
with these settings:We don't do anything special with
stack-protector
ornxcompat
.Our best guess at the moment is that the Rust compiled output is somehow tripping these alerts, but we don't have many leads.
The text was updated successfully, but these errors were encountered: