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
Download the [latest binary release](https://github.com/axllent/wireguard-vanity-keygen/releases/latest) for your system,
60
56
or build from source `go install github.com/axllent/wireguard-vanity-keygen@latest`.
61
57
62
-
63
58
## Timings
64
59
65
60
To give you a rough idea of how long it will take to generate keys, the following table lists
66
-
estimated timings to find a matching key on a system that reported "`Calculating speed: 230,000 calculations per second using 19 CPU cores`" when it started:
61
+
estimated timings to find a matching key on a system that reported
62
+
"`Calculating speed: 230,000 calculations per second using 19 CPU cores`" when it started:
67
63
68
64
| Length | Case-insensitive | Case-sensitive |
69
65
| :------ | :--------------- | :------------- |
@@ -84,7 +80,6 @@ If any search term contains numbers, the timings would fall somewhere between th
84
80
85
81
Of course, your mileage will differ, depending on the number, and speed, of your CPU cores.
86
82
87
-
88
83
## Regular Expressions
89
84
90
85
Since each additional letter in a search term increases the search time exponentially, searching using a regular expression may
@@ -105,8 +100,7 @@ On Windows, you must use double quotes. For example: `"^(a|b)"`.
105
100
106
101
NOTE: Complex regular expressions, such as those using escape sequences, flags, or character classes, may never match a key.
107
102
To avoid that, consider testing your regex using a tool such as [this one](https://go.dev/play/p/6LJy51Wd08O) on The Go Playground,
108
-
or the same tool on [goplay.tools](https://goplay.tools/snippet/6LJy51Wd08O).
109
-
103
+
or the same tool on [goplay.tools](https://goplay.tools/snippet/6LJy51Wd08O).
110
104
111
105
## FAQ
112
106
@@ -116,19 +110,16 @@ Valid characters include `A-Z`, `a-z`, `0-9`, `/` and `+`. There are no other ch
116
110
117
111
You can also use regex expressions to search.
118
112
119
-
120
113
### Why does `test` & `tes1` show different probabilities despite having 4 characters each?
121
114
122
115
With case-insensitive searches (default), a-z have the chance of matching both uppercase and lowercase. A search for "cat" can match `Cat`, `cAT` etc.
123
116
124
-
125
117
### How accurate are the estimated times?
126
118
127
119
They are not (and cannot be) accurate. Keys are completely randomly generated, and the estimate is based on a law of averages.
128
120
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.
129
121
It will however give you an indication based on your CPU speed, word count, case sensitivity, and use of numbers or characters.
130
122
131
-
132
123
### Why do I need this?
133
124
134
125
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).
0 commit comments