[flagged]
No you didn't
WireGuard vanity keygen
21–30 of 32 posts
Re: WireGuard vanity keygen
#22Re: WireGuard vanity keygen
#23I love that the app has ARM64 builds for Windows. I use a Windows ARM64 laptop daily, and every native ARM64 build I come across brings me joy. Take note, Discord.
Discord is the worst app on Windows ARM64 right now. Even win32 games run better and faster it's crazy.
Re: WireGuard vanity keygen
#24Would this run faster on a gpu?
Yes, I've generated crypto wallet vanity keys on GPUs (OpenCL) and I'd say it's about 10-20x faster than a CPU depending on which kind of key and how the code's written.
Re: WireGuard vanity keygen
#25Earlier quoted context omitted.
Key IDs are based on fingerprints and fingerprints are calculated by SHA-1 hashing the primary key's public key and the creation timestamp. A computationally easy way to influence the fingerprint is to tweak the creation timestamp which is a 32 bit Unix epoch value. Of course it needs to be in the past so the range is limited but it's faster to do it this way instead of recomputing the cryptographic key.
> the creation timestamp which is a 32 bit Unix epoch value. GPG keys aren't 2038-safe?
It's a 32-bit unsigned integer, so that should give us until Feb 2106.
> A time field is an unsigned 4-octet number containing the number of seconds elapsed since midnight, 1 January 1970 UTC.
Re: WireGuard vanity keygen
#26[dead]
Re: WireGuard vanity keygen
#27Given a situation in which you have a decent way to guess user names, such as ‘first-initial-lastname’ how much entropy does this take away? It seems like I’ve seen several of these over the years when a patch to parse comments would probably be simpler and less of an anti-pattern. What am I missing here? Edit: or a config dir that allows multiple key files.
I’m not a crypto expert at all, but surely it takes away no entropy because the fixed prefix is on the public key not the private key? My reasoning is that the full public key could be seen as a 256 bit fixed prefix, but knowing the public key is meant to give no information about the private key by design.
That may be true, but I don't think that it is obviously so.
If it were, then public keys could be shorter by the same amount and still provide the same level of protection.
But by design they are not.
Re: WireGuard vanity keygen
#28I love that the app has ARM64 builds for Windows. I use a Windows ARM64 laptop daily, and every native ARM64 build I come across brings me joy. Take note, Discord.
Discord? Why use the native app instead of just the browser version? Use e.g. Ferdium ( https://ferdium.org/ ) to have all your messaging apps in one place.
How do you keep the browser version "in tray"?
Re: WireGuard vanity keygen
#29I love that the app has ARM64 builds for Windows. I use a Windows ARM64 laptop daily, and every native ARM64 build I come across brings me joy. Take note, Discord.
> Take note, Discord.
I highly recommend Legcord[1] - it's a alternative, open-source client that has very good ARM builds
Re: WireGuard vanity keygen
#30Earlier quoted context omitted.
I’m not a crypto expert at all, but surely it takes away no entropy because the fixed prefix is on the public key not the private key? My reasoning is that the full public key could be seen as a 256 bit fixed prefix, but knowing the public key is meant to give no information about the private key by design.
That may be true, but I don't think that it is obviously so. If it were, then public keys could be shorter by the same amount and still provide the same level of protection. But by design they are not.
I still think my reasoning holds.
Let's say that I magically manage to find a private key whose public key has a chosen prefix that is the entire length of the key - i.e. the entire key is vanity. Something like myveryveryveryverylongvanitypublickey. Is that equivalent to a 0 length public key in terms of security? I'd say obviously not - there is still no way to get started when it comes to finding the private key.