Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with malleability
Search options not deleted
user 84695
A cipher or mode of operation is said to be malleable if it is feasible to modify ciphertext to produce meaningful changes in the corresponding plaintext without knowing the encryption key.
4
votes
2
answers
371
views
Making a cipher non-malleable using a plaintext transform?
The function does absolutely nothing except add non-malleability to the plaintext and thus ciphertext. It works before ANY cipher, and not with. … It is now quicker than ChaCha and achieves non-malleability at 512 bytes of input, without any bias (within limits of my testing). It adds a nonce on encoding that it removes on decoding. …
- 1,463
1
vote
Making a cipher non-malleable using a plaintext transform?
under chosen plaintext attack
As using OAEP as an all-or-nothing transform would require processing in blocks (with padding) and potentially some extra tweaking to design it for the purposes of non-malleability … Finally, it is not necessarily be the case that using such a transform function would only provide the benefit of non-malleability. …
- 1,463