Re: ECB-Counter AES mode

Karl Malbrain <malbrain@xxxxxxxxx> wrote:
The application is an encrypted file with lots of redundancy (eg identical
16 byte segments) that is randomly read and written in blocks at given
offsets. As I understand it, CTR mode by itself is insecure since the block
number would be reused when updating a block.

Perhaps you are looking for tweakable block ciphers.

--
Kristian Gjøsteen
.

Relevant Pages

  • Re: ECB-Counter AES mode
    ... 16 byte segments) that is randomly read and written in blocks at given ... offsets. ... CTR mode by itself is insecure since the block ...
    (sci.crypt)
  • Re: Which assembler can handle the BIG stuff ?
    ... It doesn't matter because it won't change the fact that too many of it's ... This restricts the size of segments to 32 KB because the PC-relative instructions on the MC68000 processor use a 16-bit offset. ... references to addresses expressed as offsets from the address stored in A5 are also limited to 16-bit offsets on the MC68000 processor. ... The classic 68K runtime architecture reflects the need for maximum memory efficiency in the original Macintosh computer which had 128 KB of RAM and an MC68000 CPU. ...
    (alt.lang.asm)
  • Re: Buffer overflow prevention
    ... the EXE file contains a ... relocation table of offsets in the code segmentthat have to be ... modified after loading the segments into memory. ...
    (Bugtraq)
Quantcast