You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-c, --case-sensitive case sensitive match (default false)
25
-
-t, --threads int threads (default 4)
25
+
-t, --threads int threads (defaults to all available cores minus 1)
26
26
-l, --limit int limit results to n (exists after) (default 1)
27
27
```
28
28
@@ -51,7 +51,7 @@ private 8IdcNsman/ZRGvqWzw1e5cRfhhdtAAmk02X9TkQxhHI= public pC1/N8coOcXmcwO09Q
51
51
## Installing
52
52
53
53
Download the [latest binary release](https://github.com/axllent/wireguard-vanity-keygen/releases/latest) for your system,
54
-
or build from source `go get -u github.com/axllent/wireguard-vanity-keygen`(go >= 1.11 required)
54
+
or build from source `go install github.com/axllent/wireguard-vanity-keygen`.
55
55
56
56
57
57
## FAQ
@@ -68,9 +68,9 @@ With case-insensitive searches (default), a-z have the chance of matching both u
68
68
69
69
### How accurate are the estimated times?
70
70
71
-
They are not and cannot be accurate. Keys are completely randomly generated, and the estimate is based on a law of averages. For instance, you could find a match for a one in a billion chance on the very first hit, or it could take you 5 billion attempts. It will however give you an indication based on word count, case sensitivity, and use of numbers or characters.
71
+
They are not (and cannot be) accurate. Keys are completely randomly generated, and the estimate is based on a law of averages. For instance, you could find a match for a one in a billion chance on the very first hit, or it could take you 5 billion attempts. It will however give you an indication based on your CPU speed, word count, case sensitivity, and use of numbers or characters.
72
72
73
73
74
74
### Why do I need this?
75
75
76
-
You don't. I wrote it because I run a WireGuard server, which does not provide any reference as to who the key belongs to (`wg` on the server). Using vanity keys, I can at least identify connections. I also wanted to learn more about multi-coe processing in Golang.
76
+
You don't. I wrote it because I run a WireGuard server, which does not provide any reference as to who the key belongs to (`wg` on the server). Using vanity keys, I can at least identify connections. I also wanted to learn more about multi-core processing in Golang.
0 commit comments