Julian Yon writes:
> On 05/11/11 03:21, George Kadianakis wrote:
>> There are some things in these HTTP solutions that make me nervous.
>>
>> In the "GET /?q=correct+horse+battery+staple\r\n\r\n" client-side case
>> we will have to build HTTP header spoofing into the tor client, which
>> is not
I improved the original proposal based on the comments of Robert.
Inlining:
Filename: 189-authorize-cell.txt
Title: AUTHORIZE and AUTHORIZED cells
Author: George Kadianakis
Created: 04 Nov 2011
Status: Open
1. Overview
Proposal 187 introduced the concept of the AUTHORIZE cell, a cell
whose
On 05/11/11 04:35, Marsh Ray wrote:
> I love this line of thinking. But what if the MitM calls your bluff and
> returns his own cookie, ETag header and a 302 Redirect to the same page?
> What would the client do then? If the client did observe the redirect as
> a browser would, he may be unable to
On 05/11/11 03:21, George Kadianakis wrote:
> There are some things in these HTTP solutions that make me nervous.
>
> In the "GET /?q=correct+horse+battery+staple\r\n\r\n" client-side case
> we will have to build HTTP header spoofing into the tor client, which
> is not fun since modern browsers se
