251 karma · joined July 21, 2020
From this I derive the motivation to work hard at what I do and ultimately try to contribute to the problems we face as a species before I pass. It also makes me appreciate the raw human connection that we can all experience: love, passion, friendship.
I may not be the one to light the altar of discovery that allows us to say, cure cancer or become a spacefaring species, but I will proudly carry the torch and pass it on.
However, that issue was only present in v2 hidden services. v2 has been depreciated in favor of the new v3 hidden service protocol (56 character long onion addresses) which is not vulnerable to this issue. This new protocol contains a full ed2559 elliptic curve public key in the onion address. The key in the onion address is used to derive what are called "blind keys". These "blinded keys" are then announced to the Tor network in such a way that nobody can recover the original public key without prior knowledge of the it, leaving them unable to establish a connection with the hidden service.
I have only briefly elaborated on how v3 hidden services work. If you are interested in a more in depth and technical explanation I encourage you to read:
[0] - https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.... [1] - https://gitlab.torproject.org/legacy/trac/-/wikis/doc/NextGe...
You can scan the entire internet for open ports, you can't scan the Tor network for hidden services to connect to unless you already have the hidden services onion addresses.
If you keep your onion address private then nobody can connect to your hidden service or even know that it exists. Simple as that.
I like your initial explanation sp332, I thought it was good so I elaborated on it.
Tor works by ensuring that there is three Tor relays between the Tor client (the software that connects to the Tor network) and the destination the Tor client is connecting to.
However, what happens when you want to establish a connection between two hosts who are both using Tor through the Tor network? Well, in that case both Tor programs establish a path through three Tor relays and link the last Tor relays in each of their separate chains together (if you are interested in learning about how each Tor program knows the others end point look up "Tor hidden service directory"). Now with both ends of their Tor relay chains linked, both hosts can communicate with each other securely and anonymously over the Tor network. (For example: you are using Tor browser to connect to a hidden service. Both Tor browser and the hidden service make a chain of three Tor relays each and connect the chains together through the last node of each chain. The Tor browser only knows the relays that it uses for its chain + the end of the hidden services chain. The hidden service only knows the relays in its chain + the last relay in your chain. Thus keeping you both anonymous.)
I hope this helps!
Also, Tor Project has had v2 address depreciation on it's roadmap for 2 years now, they have given hidden service operators plenty of time to prime their community for the v2 --> v3 switch. This gradual change is way better than scrambling to depreciate v2 addresses in response to some state actor publicly breaking the RSA keys of v2 hidden services.
> I thought I owned my tor domain
You may now, but if v2 is kept around soon you won't be the only one with the domains private key.
I feel as though the general message that the tweet threads author is trying to convey isn’t very clear. I wish they would clarify what they mean.
https://web.archive.org/web/20210829234321/https://community...
C was designed for a now obsolete computer architecture model and over the years this old model has essentially become an abstraction that sits between C and the CPU. As such, C programmers aren’t really programming in their CPU’s domain anymore and C, by default, lacks the commands necessary to effectively utilize these new developments. It is left up to the compiler to translate C code from the old architecture abstraction into efficient machine code for our new machines.
For a more in depth look into this topic I recommend you check out (0).
Edit - I just opened your website and I think I found a mistake.
> Quantum Computers - It won't affect Bitcoin in either a positive or negative manner
Bitcoin wallet addresses are based on the Ed25519 elliptic curve, and to my understanding, a quantum computer is able to break the current major forms of public cryptography that we use to date (RSA, EC). A quantum computer can be used to break wallets private keys and steal bitcoins. So a quantum computer would be pretty bad for Bitcoin in its current state.
For more information you can visit u/shrine’s original post here —> https://old.reddit.com/r/seedboxes/comments/e129yi/charitabl...