home.social

#hashes — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hashes, aggregated by home.social.

  1. The Register: 60% of MD5 password hashes are crackable in under an hour. “Using a dataset of more than 231 million unique passwords sourced from dark web leaks – including 38 million added since its previous study – and hashing them with MD5, researchers at security firm Kaspersky found that, using a single Nvidia RTX 5090 graphics card, 60 percent of passwords could be cracked in less than an […]

    https://rbfirehose.com/2026/05/10/the-register-60-of-md5-password-hashes-are-crackable-in-under-an-hour/
  2. The Register: 60% of MD5 password hashes are crackable in under an hour. “Using a dataset of more than 231 million unique passwords sourced from dark web leaks – including 38 million added since its previous study – and hashing them with MD5, researchers at security firm Kaspersky found that, using a single Nvidia RTX 5090 graphics card, 60 percent of passwords could be cracked in less than an […]

    https://rbfirehose.com/2026/05/10/the-register-60-of-md5-password-hashes-are-crackable-in-under-an-hour/
  3. The Register: 60% of MD5 password hashes are crackable in under an hour. “Using a dataset of more than 231 million unique passwords sourced from dark web leaks – including 38 million added since its previous study – and hashing them with MD5, researchers at security firm Kaspersky found that, using a single Nvidia RTX 5090 graphics card, 60 percent of passwords could be cracked in less than an […]

    https://rbfirehose.com/2026/05/10/the-register-60-of-md5-password-hashes-are-crackable-in-under-an-hour/
  4. The Register: 60% of MD5 password hashes are crackable in under an hour. “Using a dataset of more than 231 million unique passwords sourced from dark web leaks – including 38 million added since its previous study – and hashing them with MD5, researchers at security firm Kaspersky found that, using a single Nvidia RTX 5090 graphics card, 60 percent of passwords could be cracked in less than an […]

    https://rbfirehose.com/2026/05/10/the-register-60-of-md5-password-hashes-are-crackable-in-under-an-hour/
  5. The Register: 60% of MD5 password hashes are crackable in under an hour. “Using a dataset of more than 231 million unique passwords sourced from dark web leaks – including 38 million added since its previous study – and hashing them with MD5, researchers at security firm Kaspersky found that, using a single Nvidia RTX 5090 graphics card, 60 percent of passwords could be cracked in less than an […]

    https://rbfirehose.com/2026/05/10/the-register-60-of-md5-password-hashes-are-crackable-in-under-an-hour/
  6. Ars Technica: Google bumps up Q Day deadline to 2029, far sooner than previously thought. “Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key cryptography algorithms that secure decades’ worth of secrets belonging to militaries, banks, governments, and nearly every individual on earth.”

    https://rbfirehose.com/2026/04/01/ars-technica-google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought/
  7. Ars Technica: Google bumps up Q Day deadline to 2029, far sooner than previously thought. “Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key cryptography algorithms that secure decades’ worth of secrets belonging to militaries, banks, governments, and nearly every individual on earth.”

    https://rbfirehose.com/2026/04/01/ars-technica-google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought/
  8. Ars Technica: Google bumps up Q Day deadline to 2029, far sooner than previously thought. “Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key cryptography algorithms that secure decades’ worth of secrets belonging to militaries, banks, governments, and nearly every individual on earth.”

    https://rbfirehose.com/2026/04/01/ars-technica-google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought/
  9. Ars Technica: Google bumps up Q Day deadline to 2029, far sooner than previously thought. “Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key cryptography algorithms that secure decades’ worth of secrets belonging to militaries, banks, governments, and nearly every individual on earth.”

    https://rbfirehose.com/2026/04/01/ars-technica-google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought/
  10. Ars Technica: Google bumps up Q Day deadline to 2029, far sooner than previously thought. “Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key cryptography algorithms that secure decades’ worth of secrets belonging to militaries, banks, governments, and nearly every individual on earth.”

    https://rbfirehose.com/2026/04/01/ars-technica-google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought/
  11. running malcom but the old malcolm - need to image and install latest - sort of dread going from debian to ubuntu but if i image i can revert easily. maybe they figured out updating, i don't want github only updates.

    anyways it is a good one to offer vs say security onion - they use the same components mostly, suricata, zeek, elastic, maybe he has a live iso like last time.

    i think the reason to go to ubuntu is better newer drivers, bigger dev base? as long as it works - that is my concern, avoid dependency hell and breakage.

    it is good with managing all the containers and space for /datastore #sigs #hashes #dpi #netflow #ntop-ng #tcp-replay #binaries #hashcat

  12. running malcom but the old malcolm - need to image and install latest - sort of dread going from debian to ubuntu but if i image i can revert easily. maybe they figured out updating, i don't want github only updates.

    anyways it is a good one to offer vs say security onion - they use the same components mostly, suricata, zeek, elastic, maybe he has a live iso like last time.

    i think the reason to go to ubuntu is better newer drivers, bigger dev base? as long as it works - that is my concern, avoid dependency hell and breakage.

    it is good with managing all the containers and space for /datastore #sigs #hashes #dpi #netflow #ntop-ng #tcp-replay #binaries #hashcat

  13. running malcom but the old malcolm - need to image and install latest - sort of dread going from debian to ubuntu but if i image i can revert easily. maybe they figured out updating, i don't want github only updates.

    anyways it is a good one to offer vs say security onion - they use the same components mostly, suricata, zeek, elastic, maybe he has a live iso like last time.

    i think the reason to go to ubuntu is better newer drivers, bigger dev base? as long as it works - that is my concern, avoid dependency hell and breakage.

    it is good with managing all the containers and space for /datastore #sigs #hashes #dpi #netflow #ntop-ng #tcp-replay #binaries #hashcat

  14. running malcom but the old malcolm - need to image and install latest - sort of dread going from debian to ubuntu but if i image i can revert easily. maybe they figured out updating, i don't want github only updates.

    anyways it is a good one to offer vs say security onion - they use the same components mostly, suricata, zeek, elastic, maybe he has a live iso like last time.

    i think the reason to go to ubuntu is better newer drivers, bigger dev base? as long as it works - that is my concern, avoid dependency hell and breakage.

    it is good with managing all the containers and space for /datastore #sigs #hashes #dpi #netflow #ntop-ng #tcp-replay #binaries #hashcat

  15. @Wrewdison tagging #hashes to filter out the timeline based on tags.

  16. @Wrewdison tagging #hashes to filter out the timeline based on tags.

  17. @Wrewdison tagging #hashes to filter out the timeline based on tags.

  18. @Wrewdison tagging #hashes to filter out the timeline based on tags.

  19. @Wrewdison tagging #hashes to filter out the timeline based on tags.

  20. 🎉 Wow, who knew #Kubernetes needed another layer of complexity? Enter #Flox, where you can now enjoy the thrill of pulling hash-pinned packages and living in fear of #cryptographic #hashes, all while pretending your deployments are suddenly faster. 🚀 Because nothing says "cutting-edge" like making your #DevOps life an even bigger nightmare. 😜
    flox.dev/kubernetes/ #complexity #HackerNews #ngated

  21. 🎉 Wow, who knew #Kubernetes needed another layer of complexity? Enter #Flox, where you can now enjoy the thrill of pulling hash-pinned packages and living in fear of #cryptographic #hashes, all while pretending your deployments are suddenly faster. 🚀 Because nothing says "cutting-edge" like making your #DevOps life an even bigger nightmare. 😜
    flox.dev/kubernetes/ #complexity #HackerNews #ngated

  22. 🎉 Wow, who knew #Kubernetes needed another layer of complexity? Enter #Flox, where you can now enjoy the thrill of pulling hash-pinned packages and living in fear of #cryptographic #hashes, all while pretending your deployments are suddenly faster. 🚀 Because nothing says "cutting-edge" like making your #DevOps life an even bigger nightmare. 😜
    flox.dev/kubernetes/ #complexity #HackerNews #ngated

  23. 🎉 Wow, who knew #Kubernetes needed another layer of complexity? Enter #Flox, where you can now enjoy the thrill of pulling hash-pinned packages and living in fear of #cryptographic #hashes, all while pretending your deployments are suddenly faster. 🚀 Because nothing says "cutting-edge" like making your #DevOps life an even bigger nightmare. 😜
    flox.dev/kubernetes/ #complexity #HackerNews #ngated

  24. 🎩🧐 Oh, brilliant! Let's #swap a relational #database with a #version #control system because, who needs sanity, right? 😂 Just imagine querying your data with #commit hashes—what could possibly go wrong? 🤦‍♂️
    devcenter.upsun.com/posts/why- #hashes #tech #humor #HackerNews #ngated

  25. 🎩🧐 Oh, brilliant! Let's #swap a relational #database with a #version #control system because, who needs sanity, right? 😂 Just imagine querying your data with #commit hashes—what could possibly go wrong? 🤦‍♂️
    devcenter.upsun.com/posts/why- #hashes #tech #humor #HackerNews #ngated

  26. 🎩🧐 Oh, brilliant! Let's #swap a relational #database with a #version #control system because, who needs sanity, right? 😂 Just imagine querying your data with #commit hashes—what could possibly go wrong? 🤦‍♂️
    devcenter.upsun.com/posts/why- #hashes #tech #humor #HackerNews #ngated

  27. 🎩🧐 Oh, brilliant! Let's #swap a relational #database with a #version #control system because, who needs sanity, right? 😂 Just imagine querying your data with #commit hashes—what could possibly go wrong? 🤦‍♂️
    devcenter.upsun.com/posts/why- #hashes #tech #humor #HackerNews #ngated

  28. 🎩🧐 Oh, brilliant! Let's #swap a relational #database with a #version #control system because, who needs sanity, right? 😂 Just imagine querying your data with #commit hashes—what could possibly go wrong? 🤦‍♂️
    devcenter.upsun.com/posts/why- #hashes #tech #humor #HackerNews #ngated