http://rutrackerripnext.onion Not only Facebook can get

secure tripcodes are for jerks

>>60207897
if its so easy to get long vanity hashes, doesn't that mean that tor addressing is cryptographically broken

>>60207945
> so easy
They haven't said anything about how easy it was. The only comment I can find is that that destination is controlled by Rutracker admins and not a third party.

>Rutracker RIP next
Nice

>>60207945
It probably took years, or a shitton of luck
There's really few nice vanity addresses out there

File: 91jOMpI.gif (2MB, 320x240px) Image search: [Google]

2MB, 320x240px

>>60207897
>http://rutrackerripnext.onion
>http
>not https

nigga wut

File: x.png (171KB, 744x463px) Image search: [Google]

171KB, 744x463px

>>60210863
> we put encrypted tunnel into your encrypted tunel

nigga wut

>>60210930
Exit nodes will throw out unencrypted traffic.
Making tor somewhat pointless.

>>60212185
Hidden services (i.e. .onion addresses) don't go through exit nodes.

>>60208633
>>Rutracker RIP next
>Nice
Russians shutting down bittorrent trackers...
kek'd at your stupidity.

File: 1378590935548.jpg (8KB, 222x216px) Image search: [Google]

8KB, 222x216px

IPT > RUT

>>60212185
>Being unironically retarded

Poor, poor pajeet

>>60210863
>tor

>>60210863
https://facebookcorewwwi.onion/

facebooks forces https

>>60213730
Yes, but they have HTTPS *over* Tor which is encrypted twice. There isn't a lot of point to that, it's just decoration really as people are used to seeing HTTPS (like you).

There's a specific CABForum-approved way you can get OV-validated certs including .onion addresses (campaigned for mainly by the Facebook engineers wanting to put it in their certificate for discoverability).

That said, these .onion addresses are the old ones. The new ones are much, much more secure cryptographically - the old stuff is a little on the old side and I'm not that comfortable with it. It'll do, however I'm afraid they're much longer and you'll only be able to precompute a prefix.

You may, however, eventually be able to register short names, i2p-style: the consensus protocol has all the properties they need to be able to do that (without any blockchain crap).

>>60213730
Facebook has switched to HTTPS as a single entry point 4 god damn years ago, it is very likely that they have optimized the crypto frontend, made tests to ensure no unsecure content is included, no cookies are leaked, and no XSS attacks against HTTP calls exist. HTTP is treated as a fallback for specific old clients, and is probably routed trough the main codebase.

You are just saving one inescapable redirect.

>>60213934
>like me
you're thinking I'm a different anon. That was my first post in this thread and I know more about their TLS1.2 than you do
don't assume, faggot.

>>60215407
>uses p256
facebook is trash security, like banks