[poppler] RFC: Crypto and poppler

[Kristian Høgsberg]

Brad Hards wrote:
> On Thu, 7 Jul 2005 03:33 am, Kristian Høgsberg wrote:
> 
>>Brad Hards wrote:
>>
>>>To support PDF 1.6 (ie Acrobat 7), we need to support AES decryption (or
>>>encryption, its symmetric). Now that could be coded, but I'm a bit
>>>reluctant to do so, because crypto is so messy, and hardware acceleration
>>>is so useful.
>>>
>>>I have a couple of ideas:
>>>1. Rely on an external library (probably something like libgcrypt,
>>>although Botan might also be a possibility)
>>>2. Provide hooks for plugable crypto implementions
>>>3. Code it.
>>>
>>>Right now, I'm thinking about the first one as the likely best bet.
>>>libgcrypt might also replace the alleged RC4 and MD5 stuff.
>>>
>>>Thoughts?
>>
>>I'd say 1, certainly -- libgcrypt sounds like a good choice.  We've been
>>moving away from 3 in a number of places in poppler already (libjpeg,
>>zlib) so that's out.  What would be the benefit of 2?
> 
> 2 would provide the capability to hook into hardware based encryption devices 
> which might make a lot of difference for embedded apps. Now I think about it, 
> gcrypt also has a pluggable API (although I haven't used it).

That's cool, it makes more sense to configure that stuff at the 
libgcrypt level.

Kristian