Privacy matters more now than it did in the 1980's, and in todays age, having every website operator see your IP address isn't really cool.
Privacy matters more now than it did in the 1980's, and in todays age, having every website operator see your IP address isn't really cool.
I wouldn't want that kind of traffic flowing through my IP address, even if it was only for legal reasons.
If you are just a relay, the content is encrypted and your chances of liability are low. Same goes if you are promoted to a guard node.
How did the bank block you? By blocking your ip or your user account?
Cox is also very prone to turning off your internet at random times due to botnet traffic looking like it's originating from inside your network.
It's not just liability, for me it's also ethics. It gives me piece of mind that I am not contributing towards these practices.
Sometimes you have to look at the big picture when making ethical decisions.
Paying tax is mandatory, unlike installing a tor node on your modem.
Back when I was a Comcast customer I did find it useful when I was in an area with no - or too slow - mobile-data connections.
I assume that traffic on that network is always qossed to lowest priority, but I've never used it (I don't use a BT router)
They never disabled my account - I not get worldwide FON roaming for free forever - yay!
https://nakedsecurity.sophos.com/2015/08/03/can-you-trust-to...
> Cable Haunt is exploited in two steps. First, access to the vulnerable endpoint is gained through a client on the local network, such as a browser. (emphasis mine)
This issue is based on WebSockets where the software on the modem:
a) Doesn't verify any of the origin headers sent, so any origin works (rebinding is designed to beat origin checks)
b) Copies an uploaded message straight onto the stack without doing any size checks
Edit: or you could get them to click on a link