• 0 Posts
  • 17 Comments
Joined 2 months ago
cake
Cake day: July 29th, 2026

help-circle

  • His defense of SHA-1:

    Mathematically, for SHA-1’s 160-bit output, the birthday bound means that you would need about 1.4 septillion random files (1.4 quadrillion billion files - 1,400,000,000,000,000 billion - it’s impossible to effectively describe) in a single project to have file hashes accidentally collide.

    For the most part the article mostly talks about collision attacks, which quite frankly i think is silly.

    He also talks about hashes pointing to other (older) projects using a different hashing algorithm, but can’t the software just detect if its a SHA-1 hash or SHA-256, and fetch it accordingly? He acts like its the end of the world when in my mind most everything can (and probably will) be compensated for pretty easily. It’s reminiscent of the IPv6 fear-mongering.

    The thing that gets me is he doesn’t say if the current hashing algorithm or the new one has any support for when hashes do collide. Since that can theoretically happen with both, to me that sounds like a problem worth tackling.









  • Back when rooting was all the rage I tinkered with hosting various services. It just didn’t make much sense for such an underpowered device, amongst other reasons (battery swelling).

    I did use an old phone to “host” a game automation. One of those “idle clicker” / RPG games since I’m so lazy. After about 2 months the battery swelled and popped the back cover off. That was the end to that idea…







  • Signal allows just 1 device at a time, and you need to register by phone number. Unless you use their tablet mode which stores data on server… Maybe check out other projects without such requirement?

    Even with rooting (to the dismay of GrapheneOS PR team, so sad), Signal will not backup or restore properly since it uses Strongbox, so you cannot clone it amongst profiles or users. Thank the Titan chip for that. Legit a good thing, except it your case.

    Just don’t use Signal.