cbc padding breaks our code

[marspalepurple]

cbc padding breaks our code

[GoogleCodeExporter]

Whether padding is needed or not depends on which mode is used, and how much 
padding is needed depends on which cipher is used. It seems to me that the most 
appropriate place to handle message padding is within the encryption library.

That being said, I can move the code that adds and removes padding into 
addPadding and removePadding methods. That would give you the option to extend 
the CBC object and override the behavior of those methods.

In the mean time, I think you settled on the best option --  to create a new 
mode object that is compatible with your application.

Original comment by Jeff.Mott.OR on 18 Jun 2010 at 5:03

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by Jeff.Mott.OR on 18 Jun 2010 at 5:04

• Changed state: Accepted

[GoogleCodeExporter]

Could we get a fix for this soon? We are trying to make our library available 
under CC0 (~ public domain), and explaining that the modified CBC mode is 
available under different terms is a bit boring. Never the less, rewriting the 
whole mode from scratch is boring as well.

Original comment by [email protected] on 16 Sep 2010 at 9:17

[GoogleCodeExporter]

Hi, Toni. I am truly very sorry that this issue is still outstanding. Lately, 
my 9-to-5 has kept me busier than usual, and I can only promise that I'll get 
to it as soon as I can.

Original comment by Jeff.Mott.OR on 18 Sep 2010 at 9:13

[GoogleCodeExporter]

I figure the problem here is designing a good way to support padding "plugins" 
in the block modes. For now, could you just add a separate cbc-nopad mode to 
crypto-js?

Original comment by [email protected] on 28 Mar 2011 at 7:59

[GoogleCodeExporter]

r327

Original comment by Jeff.Mott.OR on 13 Apr 2011 at 11:53

• Changed state: Fixed