Re: [xmlsec] lasso is impacted by removal of soap.{c,h}
It is more than 6 years since SOAP functions in xmlsec were deprecated. Looks like Lasso removed the dependency quite some time ago as well: https://git.entrouvert.org/lasso.git/commit/?id=760eb947ab5888992dff39c76b7129178fd134f1 Any objections if I remove these functions from xmlsec? Thanks, Aleksey On 4/20/16 12:32 PM, Aleksey Sanin wrote: Just shipped 1.2.22 with SOAP restored. Hope this will help. Best, Aleksey On 4/15/16 7:41 AM, Benjamin Dauvergne wrote: Hi Aleksey, We were using the implementations in soap.{c,h} in lasso (http://lasso.entrouvert.org/) a GPL library for implementing SAML 2.0. It breaks the expected ABI from xmlsec1 from our side. Would you consider re-adding it ? It's not really difficult for us to implement a work-around (we only use accessor functions like GetBody, GetHeaer, etc.) but it could break many deployments if they update libxmlsec. ___ xmlsec mailing list xmlsec@aleksey.com http://www.aleksey.com/mailman/listinfo/xmlsec ___ xmlsec mailing list xmlsec@aleksey.com http://www.aleksey.com/mailman/listinfo/xmlsec
Re: [xmlsec] lasso is impacted by removal of soap.{c,h}
Just shipped 1.2.22 with SOAP restored. Hope this will help. Best, Aleksey On 4/15/16 7:41 AM, Benjamin Dauvergne wrote: > Hi Aleksey, > > We were using the implementations in soap.{c,h} in lasso > (http://lasso.entrouvert.org/) a GPL library for implementing SAML 2.0. It > breaks the expected ABI from xmlsec1 from our side. Would you consider > re-adding > it ? It's not really difficult for us to implement a work-around (we only use > accessor functions like GetBody, GetHeaer, etc.) but it could break many > deployments if they update libxmlsec. > ___ xmlsec mailing list xmlsec@aleksey.com http://www.aleksey.com/mailman/listinfo/xmlsec
Re: [xmlsec] lasso is impacted by removal of soap.{c,h}
Ops... Sorry about that. Let me see what I can do. Aleksey On 4/15/16 7:41 AM, Benjamin Dauvergne wrote: > Hi Aleksey, > > We were using the implementations in soap.{c,h} in lasso > (http://lasso.entrouvert.org/) a GPL library for implementing SAML 2.0. It > breaks the expected ABI from xmlsec1 from our side. Would you consider > re-adding > it ? It's not really difficult for us to implement a work-around (we only use > accessor functions like GetBody, GetHeaer, etc.) but it could break many > deployments if they update libxmlsec. > ___ xmlsec mailing list xmlsec@aleksey.com http://www.aleksey.com/mailman/listinfo/xmlsec