Mostly a summary...
http://tools.ietf.org/html/rfc1751
http://en.wikipedia.org/wiki/S/KEY
http://en.wikipedia.org/wiki/OPIE_Authentication_System
http://en.wikipedia.org/wiki/OTPW
These still work well for simple OTP systems.
The words are also simple English.
Why not just collect onion addresses in an encrypted file? ...
On 2/24/2012 5:36 AM, Ahmed Hassan wrote:
Hello Folks,
I have a cool idea to make onion addresses memorable. That will have no
effect on its authenticity and security.
[snip]
___
and store that file where?
How that encrypted file will be updated?
On Sat, 2012-02-25 at 04:09 -0500, eliaz wrote:
Why not just collect onion addresses in an encrypted file? ...
On 2/24/2012 5:36 AM, Ahmed Hassan wrote:
Hello Folks,
I have a cool idea to make onion addresses
On Sat, Feb 25, 2012 at 04:09:24AM -0500, eliaz wrote:
Why not just collect onion addresses in an encrypted file? ...
You might want to look up how they did things before DNS
was invented.
P.S. You're top-posting.
On 2/24/2012 5:36 AM, Ahmed Hassan wrote:
Hello Folks,
I have a cool
OK, here are some real examples I got from a dictionary that has a 67843
words. I collected most of the words from the Bible and Gutenberg
project.
I used Python to convert to decimal from base 32.
DuckDuckGo
3g2upl4pq6kufc4m.onion = cowboys-slipt-pisanio-utgar-spinnt.onion
Official Tor
On Sat, Feb 25, 2012 at 06:34:02AM -0500, eliaz wrote:
Where all the other sensitive files are, and updated as needed. I'm do
see how the dictionary scheme might be helpful in some instances, though
for some users it might be another complication. But I'm no expert in
these matters, just a
Where all the other sensitive files are, and updated as needed. I'm do
see how the dictionary scheme might be helpful in some instances, though
for some users it might be another complication. But I'm no expert in
these matters, just a user.
On 2/25/2012 4:12 AM, Ahmed Hassan wrote:
and store
On 24.02.2012 15:03, Andreas Krey wrote:
Have you tried this using the actual dictionaries that you want us to
use? Are the resulting addresses really memorable?
goric-edema-Alces-rune-pan-coost
feign-crig-plane-tret-balli-chela
Please consider that not everyone's native language is
Il 24 febbraio 2012 11:36, Ahmed Hassan ah...@linuxism.com ha scritto:
Hello Folks,
I have a cool idea to make onion addresses memorable. That will have no
effect on its authenticity and security.
First, I need to define some terms I will use in this email.
Σ*_{e}: is any English (or any
On 2012-02-24, Ahmed Hassan ah...@linuxism.com wrote:
Hello Folks,
I have a cool idea to make onion addresses memorable. That will have no
effect on its authenticity and security.
First, I need to define some terms I will use in this email.
Σ*_{e}: is any English (or any other language)
On Fri, 24 Feb 2012 05:36:14 +, Ahmed Hassan wrote:
...
cat-rat-hat.onion.
More like granoblastic-Congoese-counterirritate-solifluctional-Adeona or
shameproof-paralogize-concutient-hypersophisticated-Actinomyxidiida. :-)
...
Users will not have an option to explicitly choose onion domain
On Fri, 24 Feb 2012 13:36:45 +, Robert Ransom wrote:
...
Which languages do you want us to ship a dictionary for in every Tor
client? (Please specify the exact dictionaries you want us to use as
well.)
Left as an exercise for later.
How large are these dictionaries (in bytes)?
The last
On Fri, Feb 24, 2012 at 04:10:48PM +, Robert Ransom wrote:
On 2012-02-24, Andreas Krey a.k...@gmx.de wrote:
Which node interprets the .onion names to hashes, anyway?
Tor clients themselves interpret hidden service hostnames, so every
Tor client would need to include every dictionary.
On 2012-02-24, Andreas Krey a.k...@gmx.de wrote:
Which node interprets the .onion names to hashes, anyway?
Tor clients themselves interpret hidden service hostnames, so every
Tor client would need to include every dictionary. (Dictionaries
couldn't be kept in an optional extra package, because
Well,..
The according to the onion wiki, the length of the onion address is 80
bits.
The largest number the onion address can get is:
1208925819614629174706175
That's because FF:FF:FF:FF:FF:FF:FF:FF:FF:FF is the largest number
(unsigned) in hex for 80 bits key length.
If we assume we have a
On Fri, 24 Feb 2012 17:47:30 +, Eugen Leitl wrote:
...
What's wrong with a P2P name resolution? E.g. namecoin?
Everything. :-) Primarily the fact that namecoin provides
name-ipaddr mapping, and the whole point of *.onion is
that the service addressed ist *not* identified by an
IP address.
Not correct; Namecoin supports mapping names to Tor hidden services, as
well as I2P and Freenet sites. Obviously you need to use a Namecoin
implementation that's a proxy instead of a DNS server, but that's not a
big deal (nmcsocks already implements this).
On 2/24/2012 3:22 PM, Andreas Krey
Similar ideas came up in the past. Last year I've implemented something
along those lines as part of my Bachelor's thesis, but I wasn't fully
satisfied with the results. Still, maybe my work is useful to you or
someone else: http://www.sinic.name/docs/bachelor.pdf
The most interesting part for
18 matches
Mail list logo
