11–20 of 35 posts
> The kill switch is implemented in the firewall and routing table, not in software. As far as I know, both of these are in the kernel (not hardware). It's odd that so much of the README is dedicated to describing this relatively simple firewall rule, but the whole thing smells like generated slop.
Earlier quoted context omitted.
That's where VPN obfuscation is the play, imo. A lot of people nowadays are leaving streaming platforms or watch YT on smart TVs, so it does have a place. You can always exclude a device from the VPN coverage too.
Obfuscation only protects you from your own ISP messing with VPN connections. Streaming services (etc.) can't see what protocol you're using between yourself and the VPN in any case, they just see the VPN's exit IP address. Which is likely on their list of known VPN IPs.
> Hardware kill switch - Firewall-level failsafe, not software I think that firewalling/filtering and routing are software (though they can be accelerated in hardware). "Hardware kill switch" is a useful pre-existing term, which I've only seen used to mean a user-controlled mechanical switch that physically opens or closes one or more electrical circuit conductor paths necessary for whatever is to be "killed" (electr…
> Hardware kill switch - Firewall-level failsafe, not software I think that firewalling/filtering and routing are software (though they can be accelerated in hardware). "Hardware kill switch" is a useful pre-existing term, which I've only seen used to mean a user-controlled mechanical switch that physically opens or closes one or more electrical circuit conductor paths necessary for whatever is to be "killed" (electr…
You're probably right lol. It does have that connotation. I'll change it.
Earlier quoted context omitted.
You're probably right lol. It does have that connotation. I'll change it.
Was this AI-generated?
If (I’m speculating here) that’s the real question you wanted to ask, it’s perfectly okay to ask that.
> The kill switch is implemented in the firewall and routing table, not in software. As far as I know, both of these are in the kernel (not hardware). It's odd that so much of the README is dedicated to describing this relatively simple firewall rule, but the whole thing smells like generated slop.
You're right that iptables rules execute in kernel space, not dedicated hardware. "Hardware kill switch" in VPN contexts typically means the protection is implemented at the network appliance level (router) rather than a software client on each device. The distinction matters because a) client-side kill switch: App crashes → traffic leaks until you notice, and b) router-level kill switch :Default DROP policy persists…
> The kill switch is implemented in the firewall and routing table, not in software. As far as I know, both of these are in the kernel (not hardware). It's odd that so much of the README is dedicated to describing this relatively simple firewall rule, but the whole thing smells like generated slop.
You're right that iptables rules execute in kernel space, not dedicated hardware. "Hardware kill switch" in VPN contexts typically means the protection is implemented at the network appliance level (router) rather than a software client on each device. The distinction matters because a) client-side kill switch: App crashes → traffic leaks until you notice, and b) router-level kill switch :Default DROP policy persists…
Earlier quoted context omitted.
You're right that iptables rules execute in kernel space, not dedicated hardware. "Hardware kill switch" in VPN contexts typically means the protection is implemented at the network appliance level (router) rather than a software client on each device. The distinction matters because a) client-side kill switch: App crashes → traffic leaks until you notice, and b) router-level kill switch :Default DROP policy persists…
But this isn't a simple explanation, it's just... wrong? Could you share where else it's referred to as such.
Earlier quoted context omitted.
Was this AI-generated?
I’m curious why you’re asking this. Are you concerned the author didn’t review what was generated? If (I’m speculating here) that’s the real question you wanted to ask, it’s perfectly okay to ask that.