Hi,
We just had a meeting to discuss the following tor proposals[0] in the #tor-dev
IRC channel[1].
Proposal 252: Single Onion Services
Proposal 260: Rendezvous Single Onion Services
Proposal 255: Controller features to allow for load-balancing hidden services
Proposal 246: Merging Hidden Servic
Ola Bini writes:
> Hey,
>
> Thanks- this is very helpful.
>
> When it comes to vanguards, I've already read through the
> proposal. I'm not exactly sure I understand how much different 259
> would need to be to support the 247 needs. It seems we should be able
> to just run the algorithm NUM_SECO
On 09 Feb (08:43:09), Tim Wilson-Brown - teor wrote:
>
> > On 9 Feb 2016, at 01:01, David Goulet wrote:
> >
> > ...
> > Our hope is to update that pad regurlarly as implementation moves forward
> > and
> > update tor-dev@ as well with relevant information for the community. You to
> > can help
> On 9 Feb 2016, at 01:01, David Goulet wrote:
>
> ...
> Our hope is to update that pad regurlarly as implementation moves forward and
> update tor-dev@ as well with relevant information for the community. You to
> can help with this huge effort, please come find us on #tor-dev! Code review,
> c
Ola Bini writes:
> Hi again,
>
> Two questions - first, hopefully I simple one. What are directory
> guards, exactly?
>
> Second, we found a weird behavior in the current code
> base. Specifically, when Tor first downloads the microdescriptors, it
> chooses 3 guards for this with the V2Dir flag.
> On 9 Feb 2016, at 02:56, Zhenfei Zhang wrote:
>
> Also in the discussion we were talking about the possibility of using
> non-product form
> polynomial version of NTRUEncrypt, as this version will become patent free by
> Aug 2017,
> while the patent for product form will last for another 4 y
> Hey,
>
> So - thinking through your comments and thoughts, I realized that the
> better way to proceed was to describe the algorithm, and then put it
> into a proposal format. The following is updated with most of your
> comments and should be a bit clearer. I decided to remove #241 again,
> sin
Hello list,
We had a very constructive discussion on this proposal last Thursday.
I have updated the feature request based on the feedback from the
discussion.
We also like to thank Roger for grammar fixes on the proposal.
The diff file is available at:
https://github.com/zhenfeizhang/ntru-tor/co
Hi everyone!
For a while now, we've had an idea on how to proceed for the engineering part
of proposal 224 (next generation hidden service). So, we've put up this pad
with *5* large milestones that will in theory happen one after the other.
Step 1 is shared randomness for which the code and propo
