-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everyone,
Work on the Onion Name System (OnioNS) continues. As stated in the previous
status report, my primary focus now is separating the server components. In the
last release, a single name server handled everything, making it a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For this first status update on my SoP project (the Onion Name System), I'd
like to give a quick run-down of where the project currently is. I would
consider OnioNS ahead of schedule as I made significant progress on it for the
paper before the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What's to stop a sybil attack where the malicious relays try to occupy likely
site(s) for the next Quorum?
Is the consensus unpredictable enough to thwart this attack?
Even during quiet times? (Does Tor have quiet times?)
As you can see from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/20/2015 12:18 AM, tor-dev-requ...@lists.torproject.org wrote:
Furthermore, there is the question of time. As .tor-names are pinned (if you
have a name, you get to keep it 'forever', right?), an adversary may invest
into the required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/19/2015 03:20 AM, tor-dev-requ...@lists.torproject.org wrote:
Subject:
Re: [tor-dev] The Onion Name System (OnioNS)
From:
Christian Grothoff groth...@gnunet.org
Date:
05/19/2015 03:24 AM
To:
tor-dev@lists.torproject.org
Please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/19/2015 10:02 AM, Daniel Martà wrote:
I'm not familiar with Namecoin, but I thought I'd just point out
that someone will be working on OnioNS, the onion name system, as
part of the SoP in Tor. The person who will be working on it just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everyone,
I'm the one behind the Onion Name System (OnioNS), a Tor-powered distributed
DNS for Tor hidden services. It's been several weeks since my project was
selected for the SoP program, and I've finally got around to posting here
