root

@ro0ot.bsky.social

Non-descriptive.

Trouble cracking password hashes? Remember that #hashcat can stack (combine) rules. Just use: ▪️-r 1.rule -r 2.rule You can even add more rules, but it will quickly use a lot of memory. Save the rules that cracked a hash with: ▪️--debug-mode=1 --debug-file=found.rule

Shows the contents of 123.rule, that adds the number 1, 2 and 3 after a word and abc.rule, that adds a, b and c after a word. 
The third command shows hashcat being used with 123.rule and abc.rule used with the word hashcat as wordlist. The output generates hashcat1a, hashcat2a etc until hashcat3c as final output on the last line.

I'm watching some folks reverse engineer the xz backdoor, sharing some *preliminary* analysis with permission. The hooked RSA_public_decrypt verifies a signature on the server's host key by a fixed Ed448 key, and then passes a payload to system(). It's RCE, not auth bypass, and gated/unreplayable.

Filippo Valsorda@filippo.abyssdomain.expert · 2y ago

This might be the best executed supply chain attack we've seen described in the open, and it's a nightmare scenario: malicious, competent, authorized upstream in a widely used library. Looks like this got caught by chance. Wonder how long it would have taken otherwise.