Repository navigation
Support Randomization of Stack Padding Bytes - #1673
Will Hawkins (hawkinsw) wants to merge 3 commits into
Conversation
|
I think that Litebox is so cool! I noticed a In particular, I chose:
Again, if this change is something that is helpful but does not follow all the best practices, please let me know! I would love to clean it up. Thanks again for this great effort! |
|
Praveen K Paladugu (@praveen-pk) Thank you for triggering the CI run! Obviously there is a change in the publicly-visible interfaces. If that is okay, just let me know how to handle the semver check/changes. If you would prefer to handle supporting randomized padding bytes without exposing the option to the user, that is absolutely ok! Just let me know how I can spruce up the PR! Thank you again for tiggering the CI run! |
|
Will Hawkins (@hawkinsw), this PR looks good to me! as to semver checks, I believe you only have to add some details to the commit message. Jay Bosamiya (Microsoft) (@jaybosamiya-ms) could you please help with the semver failure on this PR? |
There was a problem hiding this comment.
Thanks, some changes are needed before we can consider merging this, mostly we don't want to be pulling this in as a dependency in this crate. The semver failure, if it still remains, can be fixed right before we consider merging it, please don't worry about it. The Windows failure needs to be fixed in the code however.
|
Thank you Jay Bosamiya (Microsoft) (@jaybosamiya-ms) and Praveen K Paladugu (@praveen-pk) for the reviews! I am terribly sorry for the slow response! I should have an update today! Thank you for being so welcoming to a new contributor! |
In the ELF loader, support optionally initializing the stack with random padding bytes.
7afc9e7 to
cb6a727
Compare
|
Jay Bosamiya (Microsoft) (@jaybosamiya-ms) Using the platform's |
In the ELF loader, support optionally initializing the stack with random padding bytes.