On Mon, Oct 28, 2013 at 12:53:35PM -0400, Nick Mathewson wrote:
> On Mon, Oct 28, 2013 at 9:19 AM, Matthew Finkel
> wrote:
> > Hi everyone,
> >
> > This is a proposal I wrote to implement scalable hidden services. It's
> > by no means finished (there are some slight inconsistencies which I will
>
Christopher Baines writes:
> On 28/10/13 13:19, Matthew Finkel wrote:
>> This is a proposal I wrote to implement scalable hidden services. It's
>> by no means finished (there are some slight inconsistencies which I will
>> be correcting later today or tomorrow) but I want to make it public in
>>
On 28/10/13 13:19, Matthew Finkel wrote:
> This is a proposal I wrote to implement scalable hidden services. It's
> by no means finished (there are some slight inconsistencies which I will
> be correcting later today or tomorrow) but I want to make it public in
> the meantime. I'm also working on s
Ah yes, thanks. I will cross-reference the tor spec with openssl and
submit a patch for consideration.
On Mon, Oct 28, 2013 at 9:57 AM, Nick Mathewson wrote:
> On Mon, Oct 28, 2013 at 11:46 AM, Joshua Datko wrote:
> > Why is there a limited set of OpenSSL engine algorithms chosen in
> crypto.
Hi,
you good people do still have a VM on its own ipV4 sat twiddling its
thumbs. It is pencilled in to be a 2nd relay for beta testing on. If you'd
like to put it to a different use, please feel more than free to ask.
Regards,
Phill.
On 28 October 2013 16:53, Nick Mathewson wrote:
> On Mon,
On Mon, Oct 28, 2013 at 9:19 AM, Matthew Finkel
wrote:
> Hi everyone,
>
> This is a proposal I wrote to implement scalable hidden services. It's
> by no means finished (there are some slight inconsistencies which I will
> be correcting later today or tomorrow) but I want to make it public in
> the
Happy Monday,
This is your just-a-smidge-more-than-an-hour reminder that the final
Sponsor F year 3 meeting will be in #tor-dev at 1100h Pacific. Bring
true tales of your work, the final reports you've been preparing, and
-- probably -- snacks.
Sadly, I suspect that this meeting will last slightl
On Mon, Oct 28, 2013 at 11:46 AM, Joshua Datko wrote:
> Why is there a limited set of OpenSSL engine algorithms chosen in crypto.c
> (code below)?
>
> log_engine("RSA", ENGINE_get_default_RSA());
> log_engine("DH", ENGINE_get_default_DH());
> log_engine("RAND", ENGINE_get_default_RAND());
> log_en
Why is there a limited set of OpenSSL engine algorithms chosen in crypto.c
(code below)?
log_engine("RSA", ENGINE_get_default_RSA());
log_engine("DH", ENGINE_get_default_DH());
log_engine("RAND", ENGINE_get_default_RAND());
log_engine("SHA1", ENGINE_get_digest_engine(NID_sha1));
log_engine("3DES",
On 9/16/13 8:28 PM, Karsten Loesing wrote:
> Hi everyone,
>
> some of you may already know our new approach to estimating daily Tor users:
>
> https://metrics.torproject.org/users.html#userstats
>
> This new approach is in beta since April, and I'm quite happy with it.
> I trust the new numbers
Hi everyone,
This is a proposal I wrote to implement scalable hidden services. It's
by no means finished (there are some slight inconsistencies which I will
be correcting later today or tomorrow) but I want to make it public in
the meantime. I'm also working on some additional security measures th
11 matches
Mail list logo
