In comparison, v2 onion addresses were only 16 characters long. This makes it harder to brute-force addresses. In the "new" v3 release onion addresses are 56 characters long. Sounds reasonable, ehh? All in all a welcoming change back then, which some software projects still struggle as of today with. Yes, keeping your code clean and easy to read is important to maintain it and keeping it secure. As a short explanation this just means "better crypto" (as in cryptography, not cryptocurrency). The change from version 2 to version 3 of the onion service protocol, but what exactly changed and what are the improvements? Glad you asked! V3 uses SHA3/ed25519/curve25519 Onion service protocol v2 vs v3įirst off, probably one of the most important updates in Tor's history (even though it's relatively old by now). While I'm not going to dig too deep into the past, I'll perhaps mention some changes which are rather subjectively important to me, as well as some other stuff I find interesting, stuff I'm speculating about and my wishes for Tor in the near future. But how have you grown and changed in all these years? Even though all different kinds of national services have tried to deanonymize your network, you mostly stood strong. So far you've been serving people all around the world really well that use your service and depend on your privacy design. As of the 20th September 2020 you're finally 18 years old.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |