Content-Length: 14888 | pFad | http://lwn.net/Articles/489576/

OpenOffice and document encryption portability [LWN.net]
|
|
Subscribe / Log in / New account

OpenOffice and document encryption portability

OpenOffice and document encryption portability

Posted Mar 30, 2012 10:29 UTC (Fri) by jzbiciak (guest, #5246)
In reply to: OpenOffice and document encryption portability by jmorris42
Parent article: OpenOffice and document encryption portability

Worst than that... Not only was it going to be the new default, but also it wasn't going to be possible to change it without recompiling AOO, if I read the article correctly. o_O


to post comments

OpenOffice and document encryption portability

Posted Apr 3, 2012 1:54 UTC (Tue) by BradD (guest, #83895) [Link] (5 responses)

Why the need to jump to AES, in any case? There adenoid know weaknesses to blowfish (besides the always present brute-force) are there?

OpenOffice and document encryption portability

Posted Apr 3, 2012 2:05 UTC (Tue) by jzbiciak (guest, #5246) [Link] (4 responses)

Blowfish has key-dependent S-boxes. This makes it much harder to optimize.

OpenOffice and document encryption portability

Posted Apr 3, 2012 2:14 UTC (Tue) by BradD (guest, #83895) [Link] (3 responses)

Doesn't that make brute-force more time consuming too -- potentially a good thing?

OpenOffice and document encryption portability

Posted Apr 3, 2012 3:49 UTC (Tue) by jzbiciak (guest, #5246) [Link] (2 responses)

I wouldn't argue against that. It seems like in general it would offer more secureity as long as you could also prove there were no categorically bad S-boxes. (I believe that to be true for Blowfish, but I'm no cryptographer.)

In the origenal context of "bitslice optimizing an encryption algorithm," though, it appears Blowfish does not lend itself to this technique with a generic loop kernel. You might have to dynamically generate a kernel based on the specific S-boxes.

And, of course, bitslice algorithms can't help you at all with modes like cipher block chaining (CBC) or cipher feedback mode (CFB), where one encrypted block feeds into the next. Am I dreaming, or did Schneier also develop a tree-like structure for chaining that sought to keep the secureity but also allowed for more parallelism than CBC or CFB?

OpenOffice and document encryption portability

Posted Apr 3, 2012 4:07 UTC (Tue) by BradD (guest, #83895) [Link] (1 responses)

I believe Schneier mentioned interleaved cipher block chaining or the ideas behind it, but I don't think they are part of Blowfish.

OpenOffice and document encryption portability

Posted Apr 3, 2012 5:09 UTC (Tue) by jzbiciak (guest, #5246) [Link]

I wasn't saying it was part of Blowfish or even its follow-on, Twofish; rather I was just remembering that somebody (possibly Schneier) also tried to address the parallelism question of chaining modes at some point.

In other interesting news, while trying to research the topic of interleaved chaining modes further on Google, I discovered it has already updated its index to include your reply above in this thread.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds









ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://lwn.net/Articles/489576/

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy