On Thu, 3 Mar 2016 16:33:42 + (UTC)
lukep wrote:
> Hi,
> I'm trying to understand the hybrid protocol that's described here.
> The server generates the parallel secret PAR_SEC or P and then
> computes C = ENCRYPT( P | B | Y, QSPK);
> The client decrypts C to get P and then uses it combination
Interested in coding on Tor and getting paid for it by Google? If you
are a student, we have good news for you: we have been accepted as a
mentoring organization for Google Summer of Code 2016!
https://summerofcode.withgoogle.com/organizations/6655685232164864/
Here's the facts: GSoC gives you
Zhenfei Zhang writes:
> 2.2.2 Handshake
>
> To perform the handshake, the client needs to know an identity key
digest
> for the server, and an ntor onion key (a curve25519 public key) for that
> server. Call the ntor onion key "B".
>
> The client generates a tempora
Great, lots of good comments. I'll respond in depth once the fever has
left my brain! =D
On Thu, Mar 03, 2016 at 03:15:26PM +0100, George Kadianakis wrote:
> Ola Bini writes:
>
> > Hi,
>
> Here are some more comments to the latest version of the proposal, as seen
> here:
> https://github.com/t
Ola Bini writes:
> Hi,
Here are some more comments to the latest version of the proposal, as seen here:
https://github.com/twstrike/torspec
> Filename: 259-guard-selection.txt
> Title: New Guard Selection Behaviour
> Author: Isis Lovecruft, George Kadianakis, [Ola Bini]
> Created: 2015-10-28
>
