Re: [xslt] [PATCH] new crypto namespace and hash functions forlibexslt
- From: Malcolm Tredinnick <malcolm commsecure com au>
- To: xslt gnome org
- Subject: Re: [xslt] [PATCH] new crypto namespace and hash functions forlibexslt
- Date: Wed, 05 May 2004 13:00:12 +1000
On Tue, 2004-05-04 at 10:36 -0400, joel reed wrote:
> the attached patch
No patch attached. :-)
> implements a new crypto namespace for libexslt.
> the following stylesheet shows the 3 implemented functions: md5sum,
> sha1sum, and ripemd160sum:
>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:crypto="http://exslt.org/crypto"
> extension-element-prefixes="crypto">
>
> <xsl:template match="foo/bar">
> md5sum=<xsl:value-of select="crypto:md5sum(.)"/>
> sha1sum=<xsl:value-of select="crypto:sha1sum(.)"/>
> ripemd160sum=<xsl:value-of select="crypto:ripemd160sum(.)"/>
> </xsl:template>
>
> </xsl:stylesheet>
>
> the patch makes libexslt and by extension ;) xsltproc dependent
> on openssl. if this is acceptable, please accept this patch for inclusion.
> if not, let me know what i can do to fix any blocking issues. thanks!
Without seeing the patch, my first thought is whether this really has to
be a build time decision -- maybe you have made it dynamically loadable
at runtime, though.
Also, anything linked against openssl is no longer GPL-compatible (and
probably not LGPL compatible, although I cannot remember the verdict on
that one right at the moment). This will be inconvenient / unacceptable
for a number of places where libxslt is being used (e.g. in many Linux
distributions). So if crypto support is something that is really of
widespread use in practice, we might also need an interface that builds
against gnulibtls, for example.
Cheers,
Malcolm
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]