> Not encrypted, hashed. I'm sure you know this, but to provide some context for others - this is one of the few spots where ambiguity between [password] encry

> Not encrypted, hashed. I'm sure you know this, but to provide some context for others - this is one of the few spots where ambiguity between [password] encryption and hashing may have played a role. OP stated they used crack(1) shortly before L0pth was founded. That puts the timeline somewhere between 1989 and 1992. Although salted MD5 passwords had already become a known thing by then, there would have been legacy setups where some of the password database entries were indeed outputs from ancient implementations of crypt(3). Which implies DES. To this day, if anyone wants to take a look at the crack sources[0], or download a prebuilt package[1], the default mode of operation is "I want to run passwords through crypt(3)". According to crypt(5) manpage, the legacy DES mode is still supported - just look for the string "descrypt". 0: https://alecmuffett.com/alecm/software/crack/ https://alecmuffett.com/alecm/software/crack/ 1: https://packages.debian.org/sid/crack https://packages.debian.org/sid/crack (has a link to "crack-md5" package; description states: "This package provides the runtime files for the crypt() version.")