home.social

Search

59 results for “ryanc”

  1. The people who voted in this poll were mostly pessimistic, it seems. To be fair, my own guess was mid single digits.

    infosec.exchange/@ryanc/117479

  2. RE: infosec.exchange/@ryanc/117481

    Scan of 1..232 for P-384 complete, running on P-256 now. This is running about 3M/key per second against a set of 700M. Effectively double that, actually, because I'm checking negated keys as well.

    This just running on my laptop, not anything large scale.

  3. On the internet of 2026, everyone knows you're a dog. You won't shut up about it.

  4. I'm pretty sure I can build elliptic curve rainbow tables.

  5. advent calendar of certificate authority private keys

  6. Me: walks into hotel coffee shop
    Me: ordering
    Music: song changes
    Cashier: And your name, please?
    Me: ...
    Cashier: ...are you okay?
    Me: Is that a cover of "Never gonna give you up" playing?
    Cashier: What?
    Me: Ryan, my name is Ryan.

  7. If I were a chaotic overlord, I would strictly limit public playing of christmas music to the month of December. I know there's nothing chaotic about this, but there must be limits.

  8. At long last, we have created "Honest Achmed's Used Cars and Certificates" from the classic bugzilla shitpost "Don't Create Honest Achmed's Used Cars and Certificates".

    bugzilla.mozilla.org/show_bug.

  9. My laptop keyboard is labeled in Standard Galactic for one reason: it's a dramatically cooler flex than a blank one.

    The main design goal was "must not have any normal letters or numbers".

    Side benefits:

    • Hard to shoulder surf me.

    • Other people can't type on it.

    I also expected it to be a nice conversation starter, but mostly nobody notices.

  10. Last night at a work mixer someone assumed my personal laptop, which has a keyboard labeled in Standard Galactic, was corporate issued. 😭

  11. So I'm at an internal work conference for security and security-adjacent Principal Engineers. Yesterday I signed up for a lightning talk about cracking ECDSA keys from the CT logs - before I had results. As the lightning talks started, I was realizing that against my expectations, there were no other trivially small ECDSA keys in my dataset.

    Also I had no slides because I had been getting the cracker working.

    So, I walked up on stage and without bothering to introduce myself asked the room "how many fingers am I holding up" (4), then explained what I'd built, that I had found nothing, and that people should share null results more.

    Then I introduced myself.

  12. Sorry, I have jetlag induced insomnia and poor impulse control.

  13. Girl, if your data center is:

    • about the size of a single-car garage
    • in the hands of the Wiikwemkoong Unceded Territory
    • not owned by a big tech company
    • NOT used for LLM training

    That's not a data center.

    It's a server room.

    todon.nl/@schratze/11748395506

  14. Scan of 1..233 for 700M P-256 keys I pulled out of CT logs gave no hits.

    I am both disappointed and relieved.

  15. RE: infosec.exchange/@tychotithonu

    I've checked private keys 1 through 3,000,000,000 against about 100M P-384 keys from the CT logs, no hits yet. I am going to switch to P-256 in a few minutes.

  16. Now checking about 1.1M keys per second against a dump of ~100M P-384 unique public keys from CT logs. Nothing found yet. I'm going to focus on the P-256 keys once the data file finishes syncing.

  17. I am currently letting an LLM write cryptography code for me in assembly, which is fine because it's for cracking keys.

  18. Planned key searches - note that I am also checking each key for its field negation because this is free to do:

    • Keys with few bits set
    • Keys with repeated bit patterns
    • Small keys
    • Keys that look suspiciously like pointers

    Maybe, if I feel like it:

    • Keys from KDFs with low entropy inputs
    • PRNG stream output
    • CSPRNG stream output with weak seeds
  19. For the avoidance of doubt, keys with multiple users will only be counted once per unique key.

  20. How many ecc private keys will I crack from the certificate transparency logs by Friday?

  21. I personally find data compression moderately more intimidating, but I've done a fair amount of low level implementation of both.

  22. Which do you find more intimidating to implement, Cryptography or Data Compression? This is about perception, and please assume this is "from scratch" rather than plugging in a library.

  23. Today is a good day to wear my :(){ :|:&};: (forkbomb) tshirt.

  24. Someone: "Ryan, why do you need 128GB of RAM!?"
    Me: "Chrome. But also breaking cryptography."

  25. It's times like this I'm glad my computers have silly amounts of RAM. Sorting a billion x coordinates? No problem!

  26. Corporate travel portal: This hotel less than a kilometer from the office is cheaper than the other hotel we found 8 kilometers away which will require you to uber to/from every day, but is out of policy and you can't book it.

  27. Just to be clear, I am currently dumping elliptic curve keys from the tls certificate transparency logs, and will then be running an optimized mass-cracker tool that I'll use to check a few trillion weak private keys against the entire set simultaneously using sparse bloom filters.

    The scanner (which is being heavily cribbed from my mass cryptocurrency key cracker "brainflayer") should be able to scan hundreds of thousands if not millions of keys per curve per second per core.

    I am not aware of anyone else having previously done this, so hold on to your butts.

Share on Mastodon

Enter the server where you have an account.