notroot, 15 days ago

@bagder Blog post or it didn't happen ;)

bagder, 14 days ago

@notroot okay: https://daniel.haxx.se/blog/2024/05/17/curl-tor-dot-onion-and-socks/ 😁

spv, 15 days ago

@bagder alternatively, torsocks works fine, right?

bagder, 15 days ago

@spv such "hacks" can't work for normal TCP clients for .onion names for example. But sure, if you want to access a public site on "the other side" of Tor, then it works as well. Just a little pointless.

spv, 15 days ago

@bagder interesting. torsocks works fine for onion and clearnet. with regular curl, --proxy socks5://127.0.0.1:9050 clearnet works, but onion does not, and with --proxy socks5h://127.0.0.1:9050 both work

a000d4f7a91939d0e71df1646d7a48, 15 days ago

@spv @bagder that's because in curl, socks5 means "curl does dns resolution, then asks socks5 proxy to connect to an ip", while socks5h means "curl asks socks5 proxy to connect to domain name".
Using curl's socks5:// (no h) with Tor is essentially a DNS leak, always use socks5h for that purpose.

bagder, 15 days ago

@a000d4f7a91939d0e71df1646d7a48 @spv then how does torsocks work for curl with .onion?

spv, 15 days ago

@bagder @a000d4f7a91939d0e71df1646d7a48 i think it intercepts DNS, don't quote me on that though

bagder, 15 days ago

@spv @a000d4f7a91939d0e71df1646d7a48 oh right, of course. If torsocks itself can resolve the host, it can just intercept getaddrinfo() and return the suitable IP back to the tool it runs. Sorry, I was clearly not thinking all the way here!

rticks, 15 days ago (edited 15 days ago)

@bagder in the times to come mandatory