Linux cryptographic layer development
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@mcafee.com>
To: Ruggero SUSELLA <ruggero.susella@st.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 1/1] arm/crypto: Add optimized AES and SHA1 routines
Date: Tue, 9 Oct 2012 07:00:22 +1000	[thread overview]
Message-ID: <20121008210022.GA15013@mcafee.com> (raw)
In-Reply-To: <E7C3A19B6E9F994EB4D796DB533BD7F5B9184896D8@SAFEX1MAIL3.st.com>


Jivin Ruggero SUSELLA lays it down ...
> Is this code compatible with GPL ?
> 
> To me it looks like it falls under the OpenSSL license which, accordingly to Wikipedia, is not compatible with GPL.
> Where am I wrong ?

The license on the 2 asm files from openssl the explicitly states:

	@ ====================================================================
	@ Written by Andy Polyakov <appro@fy.chalmers.se> for the OpenSSL
	@ project. The module is, however, dual licensed under OpenSSL and
	@ CRYPTOGAMS licenses depending on where you obtain it. For further
	@ details see http://www.openssl.org/~appro/cryptogams/.
	@ ====================================================================

If you follow the URL for the CRYPTOGAMS license and read the actual license
at the end of the file it is very clearly dual licensed.  So I think it is
ok :-)

Cheers,
Davidm

> -----Original Message-----
> From: linux-crypto-owner@vger.kernel.org [mailto:linux-crypto-owner@vger.kernel.org] On Behalf Of Herbert Xu
> Sent: Thursday, September 06, 2012 10:20 PM
> To: David McCullough
> Cc: linux-kernel@vger.kernel.org; linux-crypto@vger.kernel.org
> Subject: Re: [PATCH 1/1] arm/crypto: Add optimized AES and SHA1 routines
> 
> On Tue, Aug 07, 2012 at 02:01:03AM +0000, David McCullough wrote:
> > 
> > Add assembler versions of AES and SHA1 for ARM platforms.  This has 
> > provided up to a 50% improvement in IPsec/TCP throughout for tunnels using AES128/SHA1.
> > 
> > Platform   CPU SPeed    Endian   Before (bps)   After (bps)   Improvement 
> > 
> > IXP425      533 MHz      big     11217042        15566294        ~38%
> > KS8695      166 MHz     little    3828549         5795373        ~51%
> > 
> > Signed-off-by: David McCullough <ucdevel@gmail.com>
> 
> Patch applied.  Thanks!
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@vger.kernel.org More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-- 
David McCullough,      david_mccullough@mcafee.com,  Ph:+61 734352815
McAfee - SnapGear      http://www.mcafee.com         http://www.uCdot.org

  reply	other threads:[~2012-10-08 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  2:01 [PATCH 1/1] arm/crypto: Add optimized AES and SHA1 routines David McCullough
2012-09-06 20:20 ` Herbert Xu
2012-10-08 14:24   ` Ruggero SUSELLA
2012-10-08 21:00     ` David McCullough [this message]
2012-10-09  4:27       ` Jussi Kivilinna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121008210022.GA15013@mcafee.com \
    --to=david_mccullough@mcafee.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=ruggero.susella@st.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox