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

Prose editing #375

Merged
merged 2 commits into from
Sep 25, 2020
Merged

Prose editing #375

merged 2 commits into from
Sep 25, 2020

Conversation

nktrejo2020
Copy link
Contributor

rows 1-111

rows 1-111
Copy link
Member

@lvh lvh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! I have a few inline comments, but overall I think this is a great improvement.

A block cipher is a *keyed permutation*. First, the key determines exactly which
blocks are mapped. Second, the permutation aspect allows mapping of all possible blocks
to other blocks. Permutation is important because the recipient must map blocks back to the
original blocks by analyzing one-to-one.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not entirely sure about this paragraph.

First, the key determines exactly which blocks are mapped.

That's true, but I'm worried that it implies that not all blocks are mapped under all keys, but that's not true. It changes which blocks map to which blocks, but all blocks are always mapped to something.

Second, the permutation aspect allows mapping of all possible blocks to other blocks. Permutation is important because the recipient must map blocks back to the original blocks by analyzing one-to-one.

I don't really understand "by analyzing one-to-one.", maybe without it'd be fine? Or "must be able to map blocks back..."?

computes the inverse permutation. In :numref:`fig-BlockCipherDecryption`,
you can see that we get the same illustration, except that all the arrows are
going in the other direction.
we get the same illustration. The exception is that all arrowheads point
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to imply that it's only accidentally the case that the arrowheads are reversed, but that's a fundamental property. Perhaps "The difference is" or "The difference between the illustrations is"?



The only way to know which block maps to which other block, is to know
the key. A different key will lead to a completely different set of
Knowing the key helps in understanding which block maps to other blocks.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's important that the key defines which blocks map to which; perhaps "helps in understanding" implies that you know e.g. 10% of them normally but you need the key to know all of them, whereas in reality you need the key to know any of them. Consider "The key defines which blocks map to which blocks". (It's also maybe not entirely accurate to say "which blocks map to which other blocks" since you'll typically have a few blocks that map to themselves under any key. They're rare, but it happens.)

@lvh
Copy link
Member

lvh commented Sep 25, 2020

Looks great!

@lvh lvh merged commit 64e8ccf into crypto101:master Sep 25, 2020
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

Successfully merging this pull request may close these issues.

2 participants