(no title)
devops99 | 1 year ago
- a client (company I do contract work for) sees a different source address that is different than the source address I use for casual browsing+posting.
- two SaaS used for purposes of servicing agreement with "client" don't see the same source IP address as used for other clients.
- a bank I use, and PayPal, always sees the same source IP address dedicated to my VPN account only and for this purpose.
- the tunnel (VPN) provider I use for casual browsing+posting does not see the destination IP address of my client's VPN.
- whatever first-hop ISP I use sees one single Wireguard tunnel and nothing else ever.
- the first-hop Wireguard tunnel is paid for with a pre-paid debit card, but any outbound TOR traffic is encapsulated by a secondary tunnel paid for with crypto.
- the TOR circuit used for browsing purpose A is not also shared by browsing purpose B.
- any arbitrary outbound tunnel is specific to the container or VM I intended to use but doesn't carry, nor has any risk of carrying, any of my other traffic.
Tor is important to me because I have a right to read.There is no crime within Common Law for any of the above. Nor is there any violation of any statute for which any of the above is, per doctrine of minimum contact (such as with a pre-paid debit card), within jurisdiction of statute.
Perhaps some users do operate with some concern of being "busted", but most users that do outbound network path management do not operate with this concern.
No comments yet.