home.social

#hashing — Public Fediverse posts

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

  1. «Security — 60% of MD5 password hashes are crackable in under an hour:
    Happy World Password Day! Maybe it's finally time to kill this holiday in favor of World No-More-Passwords Day?»

    I don't want to know where MD5 is still being used for services in the background. The dark side is certainly bigger than we assume.

    🔓 theregister.com/security/2026/

    #nomorepasswords #itsecurity #itsec #security #happyworldpolarbearday #md5 #hashing

  2. Matrix Hashing uses two hash functions and a 2D array to achieve O(1) lookups with minimal collisions and a small sorted overflow for scalable systems. hackernoon.com/matrix-hashing- #hashing

  3. Ever thought hashes could paint colors or shape avatars?
    In this new Quarkus tutorial, I explore creative uses of Apache Commons Codec — from deterministic color generation to distributed fingerprints.

    🔗 the-main-thread.com/p/creative

    #Java #Quarkus #ApacheCommons #Hashing #Coding

  4. Can there be a #password #hashing algorithm that considers the distance between each character key on a keyboard (of some specific layout, say QWERTY)? The difficulty of hitting the correct character on a small 26-key on-screen keyboard on my phone is making me think whether we should have a relaxed algorithm that gives some fault tolerance... (Surely it'll not be as secure, but it could allow longer passwords on phones.)

  5. New crate published: crates.io/crates/souphash

    SoupHash: an order-independent hash function. Designed to be used for hashing unordered collections, or hashing over multiple threads.

    This has not been extensively reviewed, so any kind of feedback is more than welcome!

    #RustLang #Crate #Hashing

  6. Hashing is an Integrity control that helps ensure data has not been tampered with. It provides a unique digital fingerprint for verification. #Hashing

  7. Ah yes, because the world was desperately incomplete without a way to hash a 25-byte string in merely 68 clock cycles. 😴🔧 Meanwhile, the rest of us are still waiting for the riveting sequel where we parallelize the #parallelization of parallelizing. 🚀💼
    controlpaths.com/2025/06/29/pa #hashing #innovation #tech #humor #developer #life #HackerNews #ngated

  8. 🎲 Oh, the joys of #hashing your way to oblivion! It's somehow "groundbreaking" that the #math behind hash collisions is akin to picking a random box 🤯. Who knew computer science could be distilled into a carnival game? 🎪📚
    kevingal.com/blog/collisions.h #hashcollisions #computerscience #carnivalgame #groundbreaking #HackerNews #ngated

  9. Hashes for the Masses: Finding What Matters in a Sea of Samples

    A short while back, I released a pair of tools for building MD5 hash sets — one targeting known-good gold builds, the other designed for scanning malware corpora. The goal was simple: generate hash sets that could be used in forensics tools like Axiom Cyber to flag IOC matches during case processing.

    Recently, I hit a familiar problem: I had a hash and wanted to know if that file existed in my malware library. Step one was updating my tooling to support SHA256 — the modern standard for hash sharing — and regenerating the hash sets. That part worked. I could search for a hash and confirm whether it appeared in my set.

    But what if I got a match?

    At that point, I realized: I had no way to correlate the match back to the original file. With ~30,000 samples in the library, “just eyeballing it” wasn’t an option.

    As I’ve been coding up new tools — or revisiting earlier ones — I’ve discovered that rabbit holes have rabbit holes.

    So I updated the SHA256 tool to not only generate a hash set, but also produce a .tsv lookup table mapping each hash to its full file path. This made the sets usable both in forensics platforms and for custom lookups in more ad hoc workflows. As they say: necessity is the mother of intention.

    Of course, that led to another realization. I now had four hashing tools — two for MD5 (MZ and non-MZ), and two for SHA256. The “Hashing Tools” section in MalChela was getting a bit crowded.

    Back to the drawing board.

    The Result: Three Unified Tools

    I consolidated and upgraded everything into three tools — all of which support both CLI and GUI usage.

    #️⃣ MZHash (replaces mzmd5)

    • Uses YARA to recursively scan for files with an MZ header (i.e., Windows executables and DLLs)

    • Generates one hash file per selected algorithm: MD5, SHA1, SHA256

    • Also creates a .tsv lookup file for each, mapping hashes to paths

    cargo run -p mzhash /directory/to/scan -- -a MD5 -a SHA1 -a SHA256

    Via GUI, you can browse to the folder and check boxes for each algorithm.

    🌐 XMZHash (replaces xmzmd5)

    • Uses YARA to skip over files with MZ, ZIP, or PDF headers

    • Hashes everything else — ideal for surfacing Linux, Mac, or unusual samples from a mixed malware corpus

    • Also supports .tsv lookup file generation

    cargo run -p xmzhash /directory/to/scan -- -a MD5 -a SHA1 -a SHA256

    The idea: hash what’s not obviously Windows, document-related, or un-extracted samples.

    XMZHash

    🔍 HashCheck

    Okay, so naming might not be my strong suit. But this tool’s direct.

    • Provide a hash value and a .txt or .tsv hash set

    • It checks for matches, and if you’re using a .tsv, it shows the file path of the match

    • Great for live triage, corpus hunting, or checking known-bads

    cargo run -p hashcheck ./hashes.tsv 44d88612fea8a8f36de82e1278abb02f
    Hash Check

    In Summary

    MalChela 2.2.1 expands its hashing toolkit with the introduction of HashCheck, MZHash, and XMZHash — giving analysts faster ways to flag known-good, isolate unknowns, and build actionable sets. In this release, we’ve also said goodbye to legacy tools, standardized output saving, and doubled down on clarity across both CLI and GUI workflows.

    Download: https://github.com/dwmetz/MalChela/releases

    User Guide: https://dwmetz.github.io/MalChela/

    #Axiom #DFIR #Forensics #hashing #Malware #Rust #yara

  10. Merkle-tree: Как проверить целостность данных без полного доступа?

    Хэширование — простой и надёжный способ проверить целостность данных. Но как быть, если нужно удостовериться, что часть данных принадлежит определённому набору ? Например, проверить отдельную транзакцию в блоке Bitcoin или чанк файла в BitTorrent? Для этого используется уникальная структура данных — Merkle-tree . В этой статье вы узнаете, как с её помощью решать задачи проверки данных без доступа к их полному объёму.

    habr.com/ru/articles/873718/

    #merkleproof #merkle_tree #merkle_patricia_tree #blockchain #bitcoin #bittorrent #hash #hashing #distributed_systems #guide

  11. @spmatich @ibk @phoebematich

    For medical records you can imagine we want to know, and show, that the record we see is the record that was made, all of it, and only it.

    This may be accomplished by passing the (element of the) record through a #trapdoor #function, or #hashing #algorithm such as SHA1 (secure hash algorithm 1) and sending the hash somewhere else.

    The hash is small, compared with the medical note, and tiny compared to a photograph.

  12. So ... due to an early obsession with historical BSD hashes ... I have significantly more bcrypt hashrate-per-watt cracking capacity than most solo shops. For bcrypt cost 12, it's about 34Kh/s straight wordlist -- the equivalent of about 17 4090s -- at only 1100W (these old Bitcoin FPGAs are very efficient for bcrypt specifically). And this capacity is intermittently idle, which is kinda a shame.

    I haven't really put it out there as something I can help with if needed (outside of the Hashcat team). So ... feel free to ping me if you need bcrypts cracked/audited!

    (Reasonable rates, but note that I do have a pretty firmly high bar for provenance / proof of authorization)

    (Rat's nest of USB has been cleaned up a bit 😅)

    #bcrypt #PasswordCracking #hashing

  13. 'Random measure priors in Bayesian recovery from sketches', by Mario Beraha, Stefano Favaro, Matteo Sesia.

    jmlr.org/papers/v25/23-1058.ht

    #hashing #priors #prior

  14. When a target hashlist has a significantly lower percentage of cracks than expected, I've started calling the remaining/missing cracks "dark matter".

    Some potential causes of cracking "dark matter":

    • Site changed methodologies later: switched to a nested hash, added a pepper, HSM, true encryption layer, etc.

    • High number of automatically random-ish passwords: defaults, resets, bots, randomized on account lock, etc.

    • Complexity requirements higher than expected: high minimum length, etc.

    • Attacker (me) is missing key info: language, encoding, demographics, etc.

    What could other causes be?

    #Hashing #PasswordCracking

  15. 🚀 Excited to share I Just published a new blog post on scaling strategies at Wix Engineering:
    🔹 When to switch to horizontal scaling?
    🔹 How to choose the perfect routing or sharding key?

    We'd love for you to check it out: medium.com/p/29ab44b2d5b4

  16. SSDeep и все-все-все

    Для систем класса анализа внешней поверхности атак (External Attack Surface Management, EASM), непрерывно перелопачивающих обширное пространство Интернета, способность эффективно выявлять повторяющийся или тесно связанный контент имеет важное значение. Для решения этой задачи мы в СайберОК интегрировали в СКИПА различные механизмы от тривиальных регэкспов до больших языковых моделей (LLM, Large Language Model). В этой статье мы рассмотрим один из подобных трюков – использование нечеткого хеширования (fuzzy-hashing aka similarity hashing).

    habr.com/ru/companies/cyberok/

    #ssdeep #easm #hashing #хеширование

  17. So @solardiz presented a talk on "Password cracking: past, present, future" at OffensiveCon last week. Definitely worth a read - bringing his usual disciplined thinking to a topic he knows very well.

    He includes both historical and taxonomical perspectives, both of which I appreciate. Apparently, one of the first password-cracking contests was in 1982? (This was a password cracker contest - seeking the best cracking software!)

    openwall.com/presentations/Off

    [Will update post if video of the talk itself appears.]

    #passwords #hashing
    #PasswordCracking

  18. Is someone else missing the "ad" parameter (optional secret data) at Argon2 command line tool?
    🤔 AFAIK also missing on all javascript bindings. Not the case for the active Rust binding that uses this secret parameter though

    #argon2 #hash #keyed_hashing #hashing #password_hashing #linux

  19. [Paper of the day][#18] How do you triage #malware? How do you tell two files are similar? An interesting static analysis approach is to use #similarity #hashing tools, such as #ssdeep and #sdhash. However, to be effective, their application can't be straightforward, but should follow a protocol. In this paper, we discuss how to efficiently apply these functions for malware family classification. We show that hashing only the instruction disassembly has a greater impact than hashing the entire file. Check this result and much more.

    Academic paper: sciencedirect.com/science/arti
    Archived version: secret.inf.ufpr.br/papers/marc

  20. @digitalcourage.de @digitalcourage

    Die Funk-Redaktion hat das Gespräch mit Sebastian Meineck nach dem Zerschneiden leider an einer Stelle falsch zusammengefügt und einen falschen Sinnzusammenhang hergestellt:

    #E2EE wird nicht durch #hashing umgangen, sondern durch #keylogging und #screenshotting.

    Eine Datenbank mit Medien-Hashes braucht ein solcher #Uploadfilter auch, aber das ist unabhängig davon, ob E2EE umgangen oder gebrochen wird.