3 ms·
I was not connected to work via tor. My ip was listed on the tor network as a bridge. IT simply got all the tor IPs and cross checked it against IPs connected t
by flatiron 5y ago
I was not connected to work via tor. My ip was listed on the tor network as a bridge. IT simply got all the tor IPs and cross checked it against IPs connected to their VPN and I came up.
On another note a coworker downloaded a bollywood movie on BitTorrent and forgot to stop sharing and connected to the work VPN and IT got a dmca notice. They then went on a huge investigation about BitTorrent. Some people got nasty emails their IP was listed on public trackers. Their kids were using BitTorrent and they were getting nasty emails about it. That was a bit big brother for me even though I didn’t get sucked up into that thankfully.
- 3np 5y ago> My ip was listed on the tor network as a bridge Seems like you're mixing up the terminology (which is understandable, I've done it myself a couple of times in the past). https://support.torproject.org/censorship/censorship-7/ https://support.torproject.org/censorship/censorship-7/ Bridge relays are Tor relays that are not listed in the public Tor directory. There are still ways to get and detect bridge addresses but I'd be surprised if the kind of IT department that would give you trouble for running one would also go through the effort of doing so? > On another note a coworker downloaded a bollywood movie on BitTorrent and forgot to stop sharing and connected to the work VPN and IT got a dmca notice. They then went on a huge investigation about BitTorrent. Some people got nasty emails their IP was listed on public trackers. If they were listed as seeds illegally sharing copyright-protected content (and the kids weren't just downloading Debian ISOs), that's par for course.
- flatiron 5y agoYep yer right I was a relay.