wireguard-tools VS 800-63-3

Oh, this is cool. I'm a huge proponent of CLI tools supporting sensible JSON output, and things like https://github.com/WireGuard/wireguard-tools/blob/master/con... and PowerShell's |ConvertTo-Json are a huge part of my management/monitoring automation efforts.

But, unfortunately, sensible is doing some heavy lifting here and reality is... well, reality. While the output of things like the LSI/Broadcom StorCLI 'suffix the command with J' approach and some of PowerShell's COM-hiding wrappers (which are depressingly common) is technically JSON, the end result is so mindbogglingly complex-slash-useless, that you're quickly forced to revert to 'OK, just run some regexes on the plain-text output' kludges anyway.

Having said that, I'll definitely check this out. If the first example given, parsing dig output, is indeed representative of what this can reliably do, it should be interesting...

> Possible? Maybe. Easy? No. Especially the “testable” part.

a testable shell script? Never seen one.

Thinking about scirpts I've read in the past, I remember seeing Jason Donenfeld's bash script for wireguard-wg and thinking how productive and readable it was,

https://github.com/WireGuard/wireguard-tools/blob/master/src...

I see this when my equipment roams back into my private network and the wireguard server is inside that LAN. It can be solved by NAT'ing packets arriving on your edge router's inside interface, destinated to your outside IP, back to the inside wireguard server IP.

Alternatively if your client is Linux, there is:

https://github.com/WireGuard/wireguard-tools/tree/master/con...

you have a copy here that you can edit: https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh

You could adapt this script for it. What this one does is re-resolve the domain of the endpoint for when it's a dynamic dns. You run it on a timer from cron, and when your dynamic dns changes it will update the endpoint IP with wg set. You could adapt this script to update your AllowedIPs instead of the endpoint.

I found the GitHub Repository to wireguard-tools however, I cannot read the exact commands required to connect to a certain VPN! I've created a .conf file and was wondering how you could use that with WireGuard-tools to establish a VPN tunnel to my network?

I see you got your regex, but please consider reading the nist guidelines https://pages.nist.gov/800-63-3/ It is an excellent resource in password policies that isn't shared nearly enough.

Even NIST outright recommends against SMS/phone 2FA.

ID.me is the first NIST 800-63-3 approved company. https://www.businesswire.com/news/home/20180816005147/en/ID.me-Becomes-First-Identity-Provider-to-Be-Approved-as-NIST-800-63-3-Conformant & https://insights.id.me/article/what-are-the-nist-800-63-digital-identity-guidelines/

NIST has made a series of sensible guidelines:

https://pages.nist.gov/800-63-3/

They now need to be made enforceable, whether by government requiring them in government contracts, or indirectly by insurers excluding coverage if they are not met.

I just tell our customer's compliance systems and vendors (there's usually a space to explain why you're not doing a given thing) that we'll start rotating passwords as soon as NIST recommends it (again) , and no sooner. Nobody has ever failed a test nor have I even been asked about this stance. Flies right under the radar.

Several hundred pages if you want to read it all - https://pages.nist.gov/800-63-3/.