We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a follow-on after #16 is completed, or just tackled separately beforehand:
Re-implement (and cite in README.md) the work of Kim et. al. from "How'd Security Benefit Reverse Engineers? The Implication of Intel CET on Function Identification" (DSN 2022)
README.md
Identified functions should be listed in the --symbols output (and tagged as CET-derived)
--symbols
CET-based symbol population can be part of the public xgadget API, to be leveraged by external crates/tools
xgadget
Motivation: Intel CET's Indirect Branch Tracking (IBT) is prototype-insensitive, it limits but does not prevent JOP
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As a follow-on after #16 is completed, or just tackled separately beforehand:
Re-implement (and cite in
README.md
) the work of Kim et. al. from "How'd Security Benefit Reverse Engineers? The Implication of Intel CET on Function Identification" (DSN 2022)Identified functions should be listed in the
--symbols
output (and tagged as CET-derived)CET-based symbol population can be part of the public
xgadget
API, to be leveraged by external crates/toolsMotivation: Intel CET's Indirect Branch Tracking (IBT) is prototype-insensitive, it limits but does not prevent JOP
The text was updated successfully, but these errors were encountered: