News for hackers. Stuff that matters.

HvTfMhdTZ8Lths6

PS: I decided to go write up how I just use the same IPs everywhere with OpenVPN.

https://docs.google.com/document/d/1u9mGu7bv5JYL_Fvv0L7OX4_1...

Worth noting that I actually just use split-horizon DNS for my personal VPN though. Telling Unbound this is a lot easier (and still works with stuff that isn't SSH):

    local-zone: "mydomain.com." transparent  
    local-data: "foo.mydomain.com. A 10.0.0.4"
I don't think it's reasonable for clients to cache responses across disconnect/reconnect, especially when the network has observably changed (new default gateway, for example), and even more so when the resolver has changed.

Based on my own personal experience I'd also say that no (modern) clients do so although that could be wrong.

Well, setups using forced commands are relatively common with SSH (case in point: probably any Git server you've ever accessed over SSH); if one of those setups also allowed their user to specify ssh_config rules without realizing that Match can exec things there'd be a problem. I think that's a bit of a stretch though.
What is "SDN", how is it different from the thing that everyone else has called "VPN" for a few decades, and why not just have its resolver serve answers for the same TLD? Or better yet why not just route your home subnet over the VPN subnet (probably with a high metric, so that it doesn't override "real" routes) so you don't need a different IP?

Match is extremely useful though. It's in use on a few systems I control to allow password authentication from certain subnets.