Skip to main content
12 events
when toggle format what by license comment
Apr 13, 2017 at 12:48 history edited CommunityBot
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
Aug 4, 2014 at 4:17 comment added Antikithira you mean if it would make a difference if the padding is invalid or CRC? They would both fail with different failure code, so you could distinguish between the two
Jul 24, 2014 at 4:50 history edited user991 CC BY-SA 3.0
added an attack that uses less resources
Jul 24, 2014 at 4:06 comment added user991 Also, since the CRC computes over headers as well, "plaintexts" from four comments ago should be interpreted as "header/data pairs". $\;$
Jul 24, 2014 at 4:03 comment added user991 @Antikithira : $\:$ Do the outputs distinguish between invalid padding and invalid CRC? $\hspace{1.3 in}$
Jul 24, 2014 at 3:57 comment added Antikithira The CRC computes over headers as well. The padding would be a PKCS#5. There wouldn't be a lot of plaintexts, maybe up to ten.
Jul 23, 2014 at 17:48 comment added user991 @Antikithira : $\:$ Also, is the CRC computers over Headers too or just Data? $\hspace{1.62 in}$
Jul 23, 2014 at 4:14 comment added user991 What padding do they use? $\:$ How many possible plaintexts are there? $\;\;\;\;$
Jul 23, 2014 at 2:32 comment added Antikithira Th message could be as small as 16 bytes and as big probably to a couple of hundrend bytes
Jul 22, 2014 at 2:18 comment added user991 How long is the message? $\;$
Jul 22, 2014 at 1:53 comment added Antikithira I should have added that the protocol doesn't support asking for a specific plaintext to be encrypted. So basically the server will send a message to the client and the client will authenticate it using this protocol. The plaintext could be predicted though.
Jul 21, 2014 at 5:52 history answered user991 CC BY-SA 3.0