Ugh.
-
Ugh. One of the things I fucking hate about the ai -crap- being foisted on us these days is the enumerated lists that discuss vague warnings of dangers without -any- citation as to why that would be a thing.
Look at this shit.
Yeah, you fuck up TTL, your network might act a bit strange, but -legal- consequences?
-Where-.
What jurisdiction is going to have -legal- or -ethical- threat surfaces for changing TTL, and what -exactly- would those be?
Much less vague threats about 'security'; what possible security implications could there be other than the ones that I'm investigating on my end here which is the whole reason I'm digging into this damned codebase in the first place.
So this horseshit crowds out all the -legitimate- information, making it much fucking harder for me to do my job.
-
@munin I've read that some US mobile providers detect tethering through TTL value (and throttle tethered connections accordingly). Workaround is to set your PC's TTL to 65, which in theory could go against mobile provider's TOS.
-
Changing the TTL itself is not the violation of the TOS; using the access point to tether without permission is the violation of the TOS.
If changing the TTL itself were a violation of the TOS, then traceroute would be a crime, which is patently ridiculous.
-
P [email protected] shared this topic
-
@[email protected] @[email protected] me going to jail because i used ping and it set ttl to 56
