Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
VPN sure, but if he's using a VPN then all visible torrent activity should be terminated at the VPN server correct? Assuming they aren't installing management software on whatever endpoint device OP is using, how would they be able to view the specific traffic between him and whatever VPN server he is using?
In any case, I would agree with another poster that Linux ISO's and cars to a seedbox and then transfer via SFTP would be the best route.
They don't need to see the traffic inside the VPN. They only need to see that there's a VPN at all.
I get that - I was just confused at your "torrents would be detected" comment. I understand using a VPN would be visible and may be against whatever TOS they have.
Yeah, torrents without a VPN will be detected. Torrents inside a VPN won't be detected, but the VPN itself will.
What if VPN traffic is on a non-standard port?
It's still VPN traffic and will be detected as such.
Not really, if it's on TCP 443 it will look no different than a typical HTTPS traffic.
That's where you're wrong, bucko. A true tunnel over HTTPS, yes, but if you use IPSec on 443 it will still look like IPSec.
And if the org requires a CA cert or agent installation as part of their AUP, they can decrypt the HTTPS tunnel and see it as a VPN.
Typically schools and universities have acceptable use policies for student VPNs. It is not very difficult to detect VPN setup on a network and universities almost always have at least some form of network monitoring happening.
That said, VPNs are often times blocked and so is SFTP. Most universities I've done work with have a requirement that the traffic will be blocked unless you can make a case to IT as to why you need that access.
There are few legitimate use cases for student VPNs and IT staff are usually not idiots and understand what you are up to.
I get that part, and it all makes total sense. I was only confused on the "torrents will be detected" part of the original comment.