It’s not without drawback though. SSH tunnel consumes a lot more cpu compared to wireguard. If your vps has a weak cpu, it might not even able to fully saturate a 1gbps connection due to cpu bottleneck on certain ciphers. If you’re using a mobile device, it will drain your battery faster than wireguard.
I was talking to someone from the UAE in some thread on lemmy.blahaj.zone a month back. Apparently, because the UAE doesn’t like LGBT stuff, they block images hosted on that server.
I was seriously thinking there about what it would take to hide a VPN connection, and that BitTorrent Is actually not a terrible choice, as it generates a lot of bidirectional traffic.
IIRC I went looking and some guy did a prototype as his masters thesis some years back.
bit-smuggler might be the tool for you. keep those pesky internet censors off your back, get your tweets through and read your wikipedia in peace.
bit-smuggler is a tool designed to allow you to defeat internet censorship by tunneling your network traffic through what appears to be a genuine bittorrent peer connection, fooling censorship firewalls into thinking it’s harmless.
EDIT: Ah, now I remember. Wasn’t that they block images, but that they block the server. Gay UAE dude could use a permissable Threadiverse server and federation would let him talk to people on lemmy.blahaj.zone. However, the image-hosting is not federated. If someone put a post with an image up, he could view the text on another Threadiverse server, but couldn’t see the images, because the images don’t propagate to federated servers. The browser still tries to talk to the original server for that.
People in western countries use VPN to hide bittorrent traffics, while people living in an authoritarian countries uses bittorrent to hide VPN traffics. Life is sometimes stranger than fictions.
Very interesting project though. Thanks for mentioning it.
A partial fix: you can use lighter-weight ciphers in SSH then the default, if you aren’t super worried about security of the cipher. I remember that Blowfish or something can (or could, some years back) push more data per cycle than the default, which I think is normally AES these days.
It’s not without drawback though. SSH tunnel consumes a lot more cpu compared to wireguard. If your vps has a weak cpu, it might not even able to fully saturate a 1gbps connection due to cpu bottleneck on certain ciphers. If you’re using a mobile device, it will drain your battery faster than wireguard.
deleted by creator
True, it’s not like Russian need to use VPN to pirate stuff anyway.
Wait! You got it. We just encapsule https in the bittorrent protocol!
I was talking to someone from the UAE in some thread on lemmy.blahaj.zone a month back. Apparently, because the UAE doesn’t like LGBT stuff, they block images hosted on that server.
I was seriously thinking there about what it would take to hide a VPN connection, and that BitTorrent Is actually not a terrible choice, as it generates a lot of bidirectional traffic.
IIRC I went looking and some guy did a prototype as his masters thesis some years back.
Lemme see if I can find it.
googles
Yeah.
https://github.com/danoctavian/bit-smuggler
EDIT: Ah, now I remember. Wasn’t that they block images, but that they block the server. Gay UAE dude could use a permissable Threadiverse server and federation would let him talk to people on lemmy.blahaj.zone. However, the image-hosting is not federated. If someone put a post with an image up, he could view the text on another Threadiverse server, but couldn’t see the images, because the images don’t propagate to federated servers. The browser still tries to talk to the original server for that.
People in western countries use VPN to hide bittorrent traffics, while people living in an authoritarian countries uses bittorrent to hide VPN traffics. Life is sometimes stranger than fictions.
Very interesting project though. Thanks for mentioning it.
A partial fix: you can use lighter-weight ciphers in SSH then the default, if you aren’t super worried about security of the cipher. I remember that Blowfish or something can (or could, some years back) push more data per cycle than the default, which I think is normally AES these days.