Did you have time to look at the two patches I sent some times ago ?
It was about "How to avoid the node passed to xmlSecEncCtxXmlEncrypt to
be released" and "Detached signature validation problem"
Ops, I really apologize. Somehow these patches disappeared from
my radar. Will take a look toda
Thanks for the answer, it's clear :-)
Did you have time to look at the two patches I sent some times ago ?
It was about "How to avoid the node passed to xmlSecEncCtxXmlEncrypt to
be released" and "Detached signature validation problem"
And Alexandre, of course I'm interested in a WS-Security l
Hi Frank,
I have some written at c-functions at create WS-Security envelope and
validating a
document.
If Alexey will count necessary to include them in the library I can to add the
function in the repository.
I had idea create separate ws-security lib (libwsec) over libxmlsec, but my
projec
I accept patches :)
Aleksey
Frank Gross wrote:
Hi,
I've read the WS-Security spec from OASIS, and saw that some
WS-Security tokens can be child of a ds:KeyInfo node. Are there any
plans to support WS-Security or at least a mechanism to extend xmlsec in
order to handle such WS-Security toke
Hi,
I've read the WS-Security spec from OASIS, and saw that some
WS-Security tokens can be child of a ds:KeyInfo node. Are there any
plans to support WS-Security or at least a mechanism to extend xmlsec in
order to handle such WS-Security token when signing or validating a
document ?
Regar
