4 ms·

Nitpick about the website, but please don't use PGP short fingerprints like 0x46EBCD72F08E6717. They can be brute forced [0] very fast to get a different privat

Nitpick about the website, but please don't use PGP short fingerprints like 0x46EBCD72F08E6717. They can be brute forced [0] very fast to get a different private key with the same fingerprint. You can also use them to generate keys with vanity fingerprints, which is pretty funny [1]. [0] https://github.com/lachesis/scallion https://github.com/lachesis/scallion [1] I have 0xDE4444AAAAAAAAAA, took me 5 minutes of bruteforcing on a laptop.

deleted 5y ago
[deleted]
rhn_mk1 5y ago
What fingerprints should be used?
- ninjin 5y ago
  According to this guide (outdated though, but this still applies) [1], `--with-fingerprint`, as even the long ID can be spoofed. [1]: https://riseup.net/en/security/message-security/openpgp/best-practices#dont-rely-on-the-key-id https://riseup.net/en/security/message-security/openpgp/best...
jwilk 5y ago
How come? The fastest GPU in scallion's README has hash rate 11646 MH/s. To brute-force a 64-bit key ID at this rate you would need, on average, 50 GPU-years.
- arsome 5y ago
  50 GPU-years is fairly cheap, certainly within the realm of days for a 3 letter agency or a botnet.
  - someonewhocar3s 5y ago
    Kind of pushing it if you want to use it for regular cases though! Funny to think in GPU-years given more's law. Payloads like this (stochastic) have an expected time, not an actual time. It's pretty rare that you can buy 'enough processing power', usually have to go through figuring out and perhaps adjusting the payload to the computational platform yourself. (computing market is not per ops, it's per actual minute of computer time - rare to see it offered with 'compute this before')
- p-e-w 5y ago
  To brute-force a specific 64-bit ID, sure. But if your only requirement is that the ID consist of two random characters, then a run of one character, then a run of another character, the time can be cut dramatically, since there are tens of thousands of 8-byte sequences that fit this pattern, and you can simply stop as soon as you find one of them.

deleted 5y ago

[deleted]

rhn_mk1 5y ago

What fingerprints should be used?

ninjin 5y ago
According to this guide (outdated though, but this still applies) [1], `--with-fingerprint`, as even the long ID can be spoofed. [1]: https://riseup.net/en/security/message-security/openpgp/best-practices#dont-rely-on-the-key-id https://riseup.net/en/security/message-security/openpgp/best...

jwilk 5y ago

How come? The fastest GPU in scallion's README has hash rate 11646 MH/s. To brute-force a 64-bit key ID at this rate you would need, on average, 50 GPU-years.

arsome 5y ago
50 GPU-years is fairly cheap, certainly within the realm of days for a 3 letter agency or a botnet.
- someonewhocar3s 5y ago
  Kind of pushing it if you want to use it for regular cases though! Funny to think in GPU-years given more's law. Payloads like this (stochastic) have an expected time, not an actual time. It's pretty rare that you can buy 'enough processing power', usually have to go through figuring out and perhaps adjusting the payload to the computational platform yourself. (computing market is not per ops, it's per actual minute of computer time - rare to see it offered with 'compute this before')
p-e-w 5y ago
To brute-force a specific 64-bit ID, sure. But if your only requirement is that the ID consist of two random characters, then a run of one character, then a run of another character, the time can be cut dramatically, since there are tens of thousands of 8-byte sequences that fit this pattern, and you can simply stop as soon as you find one of them.