[xmlsec] extended character set encryption/decryption
beall at usc.edu
Tue Apr 2 16:32:32 PDT 2013
Sorry to keep hitting this list, but I had to correct this note. Editing line 4497 of parser.c in version 2.9.0 of libxml2 actually does correct the behavior. When I wrote this note I hadn't quite edited the line the same way as before, and so I caused processing errors for other parsing before fixing my typo.
On Apr 2, 2013, at 4:00 PM, Russell Beall <beall at usc.edu> wrote:
> Anyway, after compiling this and trying it out, I confirmed that the behavior is still present, but that fixing the corresponding line in parser.c does not entirely cause it to work, because then the parser complains about extra content at the end of the document. But it is complaining about the <KeyName> field contained in the xmlsec KeyInfo block.
> I guess this usage of encrypting an entire XML document instead of just content is not really the supported way of using these APIs?
More information about the xmlsec