From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] using tls-psk cipher suits vs roll our own handshake
Date: Fri, 25 Dec 2015 04:03:57 +0100 [thread overview]
Message-ID: <7cce8a1dde0616a1f6c3960ed928f0e0@felloff.net> (raw)
In-Reply-To: <CAGi9AcbUCjhPEeLQ8M-czhbGyEBc3xMJsYYfM1Gc0LSeSN2Xug@mail.gmail.com>
no. the "shared secret from the authentication process" refers to
the random key generated by the AS (and transported to both the server
and client in tickets that are encrypted with the servers/clients key).
the situation is that server and client already authenticated each
other and have a random shared secret key for the "session" and now
want to setup encryption on the channel.
the functionality that is desired is to be able to "negotiate" the
cipher suits and record layer protocol versions.
--
cinap
next prev parent reply other threads:[~2015-12-25 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 16:45 cinap_lenrek
2015-12-24 17:09 ` Iruatã Souza
2015-12-24 23:49 ` cinap_lenrek
2015-12-25 2:34 ` Alex Weber
2015-12-25 3:03 ` cinap_lenrek [this message]
2015-12-29 18:34 ` Charles Forsyth
2015-12-29 18:35 ` Charles Forsyth
2016-01-03 4:03 ` cinap_lenrek
2015-12-29 20:31 ` Kenny Lasse Hoff Levinsen
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=7cce8a1dde0616a1f6c3960ed928f0e0@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.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).