Ok, let's try to distill your comments down into some action items for
the proposal.
Thus spake Robert Ransom (rransom.8...@gmail.com):
> On 2012-03-26, Mike Perry wrote:
>> 3. Provide information about bridge sources to users
>>
>>BridgeFinder MUST provide complete information about how
On 3/27/12 12:09 PM, Robert Ransom wrote:
> It's not a typo. Those BridgeFinderHelpers MUST NOT be installed
> unless the user has explicitly permitted that they be installed. Even
> if the user has explicitly permitted that a BridgeFinderHelper be
> installed and write data to disk, it SHOULD NO
On 2012-03-26, Mike Perry wrote:
> Thus spake Robert Ransom (rransom.8...@gmail.com):
>> 3. Provide information about bridge sources to users
>>
>> BridgeFinder MUST provide complete information about how each
>> bridge was obtained (who provided the bridge data, where the
>> par
Thus spake Robert Ransom (rransom.8...@gmail.com):
> I rewrote most of the ‘Security Concerns’ section for
> BridgeFinder/Helper. Please merge:
> https://git.torproject.org/rransom/torspec.git bridgefinder2
>
> Security Concerns: BridgeFinder and BridgeFinderHelper
>
> 1. Do not allow
On 2012-03-22, Mike Perry wrote:
> Thus spake Robert Ransom (rransom.8...@gmail.com):
>
>> [ snip ]
>
> Ok, attempt #2. This time I tried to get at the core of your concerns
> about attacker controlled input by requring some form of authentication
> on all bridge information that is to be automati
Thus spake Robert Ransom (rransom.8...@gmail.com):
> [ snip ]
Ok, attempt #2. This time I tried to get at the core of your concerns
about attacker controlled input by requring some form of authentication
on all bridge information that is to be automatically configured.
I also added a requirement
On 03/21/2012 06:28 PM, Mike Perry wrote:
> Thus spake Robert Ransom (rransom.8...@gmail.com):
>
>> [ snip ]
>
> I've updated the proposal to address your concerns at mikeperry/bridgefinder2.
When you and Robert finish hashing this out, please let me know and I'll
merge your final commits with t
On 2012-03-22, Mike Perry wrote:
> Thus spake Robert Ransom (rransom.8...@gmail.com):
>
>> [ snip ]
>
> I've updated the proposal to address your concerns at
> mikeperry/bridgefinder2.
>
> I've relaxed some of the requirements a little, but I think I still
> properly cover everything you mentioned
On 2012-03-22, Mike Perry wrote:
> Thus spake Robert Ransom (rransom.8...@gmail.com):
>
>> [ snip ]
>
> I've updated the proposal to address your concerns at
> mikeperry/bridgefinder2.
>
> I've relaxed some of the requirements a little, but I think I still
> properly cover everything you mentioned
Thus spake Robert Ransom (rransom.8...@gmail.com):
> [ snip ]
I've updated the proposal to address your concerns at mikeperry/bridgefinder2.
I've relaxed some of the requirements a little, but I think I still
properly cover everything you mentioned.
Here's the updated proposal inline for more c
On 2012-03-21, Mike Perry wrote:
> The following proposal should complete SponsorF tickets #5010-5012.
>
> I've pushed the proposal to my torspec.git branch
> mikeperry/bridgefinder, since the POSTMESSAGE Proposal ended up with
> some garbling at somewhere along the cut and paste chain. That branc
On 03/20/2012 06:23 PM, Mike Perry wrote:
> The following proposal should complete SponsorF tickets #5010-5012.
>
> I've pushed the proposal to my torspec.git branch
> mikeperry/bridgefinder, since the POSTMESSAGE Proposal ended up with
> some garbling at somewhere along the cut and paste chain. T
The following proposal should complete SponsorF tickets #5010-5012.
I've pushed the proposal to my torspec.git branch
mikeperry/bridgefinder, since the POSTMESSAGE Proposal ended up with
some garbling at somewhere along the cut and paste chain. That branch
also contains fixes for the POSTMESSAGE p
13 matches
Mail list logo
