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.

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

Explain how bias in a keystream can lead to attacks #331

Open
trackpick opened this issue May 1, 2017 · 0 comments
Open

Explain how bias in a keystream can lead to attacks #331

trackpick opened this issue May 1, 2017 · 0 comments

Comments

@trackpick
Copy link
Contributor

I've seen the argument before, so I don't particularly need convincing (though TBH I've forgotten the details), but it would be nice to give readers an intuition for a possible attack based on a keystream containing bias. Noting this while reading the section on attacks on RC4 but it could equally well be connected to the description of one-time pads I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant