[xmlsec] build system changes
Jesse Pelton
jsp at PKC.com
Fri Sep 5 10:32:17 PDT 2003
Congratulations, Aleksey! XMLSec apparently meets one of my favorite
criteria for successful software: it's useful in ways you didn't envision
when you wrote it.
I still can't get over what a nice piece of work it is. It's an important
contribution to the collection of open source libraries.
> -----Original Message-----
> From: Edward Shallow [mailto:ed.shallow at rogers.com]
> Sent: Friday, September 05, 2003 1:21 PM
> To: 'Aleksey Sanin'; 'John Belmonte'
> Cc: xmlsec at aleksey.com
> Subject: RE: [xmlsec] build system changes
>
>
> So am I. For every Decrypt and Verify, someone has performed
> a Sign and
> Encrypt. Given key storage requirements, signature policies
> mandating active
> involvement of clients at signing time (e.g. the EU
> Directive), desktop
> signers, etc ... very often that client is a desktop.
>
> We are utilizing XMLSec on both the desktop and the server. This is a
> distinct advantage that XMLSec has over other XMLDSIG implementations,
> especially given its multiple crypto engine support. I need
> not deal with
> cross-library compatibility issues.
>
>
> -----Original Message-----
> From: xmlsec-admin at aleksey.com
> [mailto:xmlsec-admin at aleksey.com] On Behalf
> Of Aleksey Sanin
>
> Sent: September 5, 2003 10:43 AM
> To: John Belmonte
> Cc: xmlsec at aleksey.com
>
> Ok, you are right. The "rich" clients might use these
> technologies as well.
> It's just my limited view on the world from a browser window
> makes me think
> that all the xml security things are happen between two servers :)
>
> Aleksey
>
> John Belmonte wrote:
>
> > Aleksey wrote:
> >
> >> - The main usage for xmlsec is on servers, most likely
> there would
> >> be only one crypto
> >
> >
> > That sounds strange to me. XML is commonly used for client-server
> > applications, and for every server app using XML
> Signature/Encryption
> > there must be a client app using it too. I am designing such an
> > application, which is what brought me to xmlsec.
More information about the xmlsec
mailing list