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

fix "reply attack" typo #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix "reply attack" typo #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion state_harmful.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -865,7 +865,7 @@ inject the malware].
The author believe such a move would be extremely risky for a vendor like Intel.
Again, we should remember that such malware insertion (by either the processor
or FSP blob) could not be conditioned on any persistent state, and so would be
subject to reply "attack". In other words, once the processor or the FSP got
subject to replay "attack". In other words, once the processor or the FSP got
caught while pulling this off, it should be possible for the user to reproduce
and demonstrate this malicious behaviour arbitrary number of times subsequently.

Expand Down