Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1276389

Re: [RFC PATCH 2/2] Crypto kernel tls socket

From Stephan Mueller <smueller@chronox.de>
Newsgroups linux.kernel
Subject Re: [RFC PATCH 2/2] Crypto kernel tls socket
Date 2015-11-24 13:40 +0100
Message-ID <qyl34-86O-9@gated-at.bofh.it> (permalink)
References <qy3pw-51A-13@gated-at.bofh.it> <qyjXk-7sn-13@gated-at.bofh.it> <qykqm-7Cj-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Am Dienstag, 24. November 2015, 12:54:07 schrieb Phil Sutter:

Hi Phil,
>
>There "still" are dedicated crypto engines out there which need a driver
>to be accessed, so using them from userspace is not as simple as with
>padlock or AESNI. This was the reasoning behind the various cryptodev
>implementations and af_alg. Using those to establish a TLS connection
>with OpenSSL means to fetch encrypted data to userspace first and then
>feed it to the kernel again for decryption. Using cryptodev-linux, this
>will be zero-copy, but still there's an additional context switch
>involved which the approach here avoids.

Well, when being nasty, I could ask, why not putting the entire web server 
into the kernel. Heck, why not getting rid of user space?

Sorry, I could not resist. :-)

But back to the technical discussion. My main concern is that TLS is a big 
protocol and it is by far not the only crypto protocol where all those 
protocols seem to uses the same crypto primitives. And to me, there should be 
a good reason why software executes in supervisor state. Simply saving some 
context switches is not a good argument, because the context switches are 
there for a reason: to keep the system safe and secure.

Ciao
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[RFC PATCH 0/2] Crypto kernel TLS socket Dave Watson <davejwatson@fb.com> - 2015-11-23 18:50 +0100
  [RFC PATCH 1/2] Crypto support aesni rfc5288 Dave Watson <davejwatson@fb.com> - 2015-11-23 18:50 +0100
    Re: [RFC PATCH 1/2] Crypto support aesni rfc5288 Herbert Xu <herbert@gondor.apana.org.au> - 2015-11-24 11:40 +0100
  [RFC PATCH 2/2] Crypto kernel tls socket Dave Watson <davejwatson@fb.com> - 2015-11-23 18:50 +0100
    Re: [RFC PATCH 2/2] Crypto kernel tls socket Sowmini Varadhan <sowmini.varadhan@oracle.com> - 2015-11-23 20:30 +0100
      Re: [RFC PATCH 2/2] Crypto kernel tls socket Dave Watson <davejwatson@fb.com> - 2015-11-23 22:50 +0100
        Re: [RFC PATCH 2/2] Crypto kernel tls socket Sowmini Varadhan <sowmini.varadhan@oracle.com> - 2015-11-23 23:00 +0100
    Re: [RFC PATCH 2/2] Crypto kernel tls socket Herbert Xu <herbert@gondor.apana.org.au> - 2015-11-24 11:40 +0100
      Re: [RFC PATCH 2/2] Crypto kernel tls socket Stephan Mueller <smueller@chronox.de> - 2015-11-24 12:10 +0100
        Re: [RFC PATCH 2/2] Crypto kernel tls socket Hannes Frederic Sowa <hannes@stressinduktion.org> - 2015-11-24 12:30 +0100
          Re: [RFC PATCH 2/2] Crypto kernel tls socket Phil Sutter <phil@nwl.cc> - 2015-11-24 13:00 +0100
            Re: [RFC PATCH 2/2] Crypto kernel tls socket Stephan Mueller <smueller@chronox.de> - 2015-11-24 13:40 +0100
          Re: [RFC PATCH 2/2] Crypto kernel tls socket Sowmini Varadhan <sowmini.varadhan@oracle.com> - 2015-11-24 13:00 +0100
          Re: [RFC PATCH 2/2] Crypto kernel tls socket Stephan Mueller <smueller@chronox.de> - 2015-11-24 13:40 +0100
  Re: [RFC PATCH 0/2] Crypto kernel TLS socket Hannes Frederic Sowa <hannes@stressinduktion.org> - 2015-11-23 20:20 +0100

csiph-web