Difference between revisions of "VPP/HostStack/TLS"
From fd.io
Florin.coras (Talk | contribs) |
Florin.coras (Talk | contribs) |
||
| Line 1: | Line 1: | ||
== TLS App == | == TLS App == | ||
| − | TLS service is offered by the stack to other client applications via a custom builtin application. The TLS application implements a special transport type that allows it to behave as an application, from the underlying TCP transport perspective, but also as a transport, from the client application perspective. The app does not directly implement the TLS protocol, i.e., the record layer, handshaking protocols and the cryptographic computations and suites, instead it relies on the mbedtls library. | + | TLS service is offered by the stack to other client applications via a custom builtin application. The TLS application implements a special transport type that allows it to behave as an application, from the underlying TCP transport perspective, but also as a transport, from the client application perspective. The app does not directly implement the TLS protocol, i.e., the record layer, handshaking protocols and the cryptographic computations and suites [1], instead it relies on the mbedtls library. |
| + | |||
| + | == References == | ||
| + | |||
| + | [1] [https://tools.ietf.org/html/rfc5246 | RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2] | ||
Revision as of 06:11, 7 March 2018
TLS App
TLS service is offered by the stack to other client applications via a custom builtin application. The TLS application implements a special transport type that allows it to behave as an application, from the underlying TCP transport perspective, but also as a transport, from the client application perspective. The app does not directly implement the TLS protocol, i.e., the record layer, handshaking protocols and the cryptographic computations and suites [1], instead it relies on the mbedtls library.
References
[1] | RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
