linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Stoica <cristian.stoica@freescale.com>
To: Andy Lutomirski <luto@amacapital.net>,
	<herbert@gondor.apana.org.au>, <linux-crypto@vger.kernel.org>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add TLS record layer encryption module
Date: Fri, 1 Aug 2014 11:24:35 +0300	[thread overview]
Message-ID: <53DB4EC3.3080507@freescale.com> (raw)
In-Reply-To: <53DAA031.30405@amacapital.net>

>> This set of patches introduces support for TLS 1.0 record layer
>> encryption/decryption with a corresponding algorithm called
>> tls10(hmac(<hash>),cbc(<cipher>)).
>>
>> Similarly to authenc.c on which it is based, this module mixes the base
>> algorithms in software to produce an algorithm that does record layer
>> encryption and decryption for TLS1.0.
>> Any combination of hw and sw base algorithms is possible, but the purpose
>> is to take advantage of hardware acceleration for TLS record layer offloading
>> when hardware acceleration is present.
> 
> What is this used for?  AF_ALG?  I find it hard to believe that the
> kernel will ever want to use this internally.

Yes, AF_ALG is what we have in mind.

Cristian S.

  reply	other threads:[~2014-08-01  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  9:32 [PATCH 0/2] Add TLS record layer encryption module Cristian Stoica
2014-07-29  9:32 ` [PATCH 1/2] crypto: add support for TLS 1.0 record encryption Cristian Stoica
2014-07-31 20:01   ` Andy Lutomirski
2014-08-01  9:06     ` Cristian Stoica
2014-08-01 14:44       ` Andy Lutomirski
2014-08-04  6:21         ` Cristian Stoica
2014-07-29  9:32 ` [PATCH 2/2] crypto: add TLS 1.0 test vectors for AES-CBC-HMAC-SHA1 Cristian Stoica
2014-07-31 19:59 ` [PATCH 0/2] Add TLS record layer encryption module Andy Lutomirski
2014-08-01  8:24   ` Cristian Stoica [this message]
2014-08-25  9:44   ` Herbert Xu
2014-08-25 13:12 ` Hannes Frederic Sowa

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=53DB4EC3.3080507@freescale.com \
    --to=cristian.stoica@freescale.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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;
as well as URLs for NNTP newsgroup(s).