Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a227b2798d19c235

Jump to content

Talk:TLS acceleration

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 9 years ago by 2A01:E35:8BD7:2180:EC8D:1BFA:DAFD:4EA8 in topic Advertisement?

Advertisement?

[edit]

Many ARM SoCs have a crypto accelerator, why mention Allwinner products specifically? 2A01:E35:8BD7:2180:EC8D:1BFA:DAFD:4EA8 (talk) 19:42, 10 August 2016 (UTC)Reply

[edit]

There is need for a link from the crypto page to this page 66.90.182.183 06:55, 5 September 2006 (UTC)Reply

Symmetric/Asymmetric keys

[edit]

This sentence is confusing/incorrect "[...] software is required to decrypt the SSL session key (an asymmetric key) that has been sent to it from the SSL client (usually a web browser)". There was a modification in this revision (small typo - handshake uses asymmetric keys (public/private pair)).

The problem is that the session key is the symmetric key: that's what's encrypted and decrypted indeed, but that's not what's used to encrypt/sign the handshake messages. What's used to encrypt and sign the handshake messages (including those containing the session keys) are the asymmetric keys in the certificates. —Preceding unsigned comment added by BrunoHarbulot (talkcontribs) 17:23, 1 November 2010 (UTC)Reply