wireguard-tools
acme-tiny
wireguard-tools | acme-tiny | |
---|---|---|
12 | 5 | |
439 | 4,699 | |
2.1% | - | |
3.2 | 0.0 | |
11 days ago | over 1 year ago | |
C | Python | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wireguard-tools
-
jc: Converts the output of popular command-line tools to JSON
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...
-
Write Posix Shell
> 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...
- Accessing WireGuard VIA DDNS
- C# to C Struct
-
Identity Management for WireGuard
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...
-
wireguard-tools on FreeBSD (TrueNas), where do I find the reresolve-dns.sh script? (Or something similar)
you have a copy here that you can edit: https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh
- Dynamic DNS setting??
- wireguard-dns
-
Route only certain dynamic IPs through the WireGuard tunnel
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.
-
WireGuard MacOS DMG File
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?
acme-tiny
- Write Posix Shell
-
ZeroSSL: XSS to session hijacking, stealing a private key (and password hash)
Going to throw another hat into the ring here: I use acme-tiny [1], which is a single file ACME client written in Python in under 200 lines. The idea behind it is that you can fully read and understand everything it does without spending too much time on it. I really like this approach, so I went ahead and started using it, and have been for a few years now.
[1] https://github.com/diafygi/acme-tiny
- Uacme: ACMEv2 client written in plain C with minimal dependencies
-
Certs for SSL for internal devices
Let’s Encrypt with ACME-Tiny
-
Another free CA as an alternative to Let's Encrypt
Recommendation from me as well. Have been using this script for multiple years now without a single issue. The minimal code is awesome for avoiding unnecessary external dependencies and complexity.
Be sure to use the latest version from https://github.com/diafygi/acme-tiny though :-)
What are some alternatives?
wireguard-apple - Mirror only. Official repository is at https://git.zx2c4.com/wireguard-apple
acme.sh - A pure Unix shell script implementing ACME client protocol
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
CsWin32 - A source generator to add a user-defined set of Win32 P/Invoke methods and supporting types to a C# project.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
VxWireguard-Generator - Utility to generate VXLAN over Wireguard mesh SD-WAN configuration
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
textfsm - Python module for parsing semi-structured text into python tables.
acme-dns-server - Simple DNS server for serving TXT records written in Python
tailscale - The easiest, most secure way to use WireGuard and 2FA.
dehydrated-bigip-ansible - Ansible based hooks for dehydrated to enable ACME certificate automation for F5 BIG-IP systems