Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

3

+1 visualizing is the key. I always liked the example with a picture of a penguin in the ECB section of Block cipher article). An automated software rarely can detect such regularities

Maksee
– Maksee

2012-05-06 07:44:39 +00:00
Commented May 6, 2012 at 7:44
Eh? The point of that visualisation is to show that the distribution is not okay. The naïve shuffle algorithm makes certain orders much more likely than others. Notice how far more to the right the 2341, 2314, 2143 and 1342 bars extend?

hvd
– hvd

2016-01-02 16:16:02 +00:00
Commented Jan 2, 2016 at 16:16

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »