4 ms·
You can't do that because that's not the way encryption works. The reason onion addresses are random looking is because they are a function of the hidden servi
by zensavona 8y ago
You can't do that because that's not the way encryption works.
The reason onion addresses are random looking is because they are a function of the hidden service's public key.
If you could generate a "private key" from the public key, anyone could use your "domain name". The reason tor doesn't require centralised domain name services is because we can trust that whoever owns the private key to the public key which we identify with the onion address, owns the onion address.
- DINKDINK 8y agoThe closest you could get to OP's idea is to have a human-readable, non-configurable (but minable) mnemonic that maps to a public key.
- kodablah 8y agoThis has been tried quite a bit ranging from proquint to random 32-bit phrases [0]. I just don't think we as humans are going to be able to make something both memorable and with enough size to hold, say, ed25519 keys (i.e. Tor v3 keys). KDFs leave a lot to be desired too, we're going to have to find a better way. Until then, obtuse names and lack of easy discovery will plague decentralized setups. 0 - https://blog.asana.com/2011/09/6-sad-squid-snuggle-softly/ https://blog.asana.com/2011/09/6-sad-squid-snuggle-softly/
- floatboth 8y agoOr just "mining" vanity addresses like facebookcorewwwi.onion
- jancsika 8y ago> If you could generate a "private key" from the public key, That's not what I wrote at all. I'm just talking about downgrading the onion addy generation to become a simple password authentication scheme. It's bad but no worse than logging into webmail without any 2FA. If you really don't understand what I'm talking about I can put together a PoC. But it's extremely straightforward so I'd rather not if you can just re-read what I wrote and grok the idea.