On Thu, 5 Nov 2009 15:45:44 -0500, Jeffrey Bloss wrote:

On Thu, 5 Nov 2009 15:33:28 -0500, Klaatu wrote:

On Thu, 5 Nov 2009 14:29:45 -0500, Ron May wrote:

On Thu, 05 Nov 2009 12:22:17 -0600, brian whatcott wrote:

Hi folks,

Anybody have Bloss's address and job details?

Brian W

And if you send an error when that happens, you know the padding
failed. Now if you keep trying different random blocks, what's
eventually going to happen?

You'll get a message with valid padding. Valid padding might be 0x3 0x3
0x3. Or it might be 0x4 0x4 0x4 0x4. But if you're basically generating
random blocks, what's the mostly likely padding you're going to get
that will pass the check?

HTH

0x1.

And you're randomizing the output by tacking a random block in front of
real ciphertext, which gets XOR'd during decryption. So you know the
last byte of your random block...

And the 0x1 that you know the padding is, and so that random byte XOR
the last byte of the plaintext is 0x1, and so you know the last byte of
the plaintext.

(Pausing)

And now that you know the last byte of the plaintext, you can make the
padding come out to 0x2 and try randomizing the other 15 bytes to find
out the next byte, and so on?

Blow me, hummingbird and all your socks!
--
Virus Removal http://max.shplink.com/removal.html
Change nomail.afraid.org to gmail.com to reply by email.
nomail.afraid.org is specifically set up for use in USENET.
Feel free to use it yourself.