home.social

#cryptographic — Public Fediverse posts

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

  1. 🎉 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

  2. @berniethewordsmith The main way to respect is to avoid , end-to-end encrypted content at scale. Focus on:
    - and opt-in tools for local scanning.

    - checks only for data that’s already leaving the private domain.

    - that verify matches without exposing the rest of users’ data.

  3. 🚀✨ Behold, a *groundbreaking* innovation: a "fast" #GUID #generator for Go! Because clearly, generating #random #numbers wasn't #fast enough without #cryptographic #safety. 😅 But hey, who needs actual #software #development when you can fiddle with GUIDs and call it a day! 🔒🎉
    github.com/sdrapkin/guid #groundbreaking #innovation #Go #HackerNews #ngated

  4. Scientists in #China use #quantum computers to crack military-grade #encryption — quantum attack poses a "real and substantial threat" to #RSA and #AES. According to a report published by the SCMP, the researchers utilized a #DWave #quantumcomputer to mount the first successful quantum attack on widely used #cryptographic algorithms.
    tomshardware.com/tech-industry

  5. #PuTTY #SSH client flaw allows recovery of #cryptographic #privatekeys
    The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates #ECDSA nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
    bleepingcomputer.com/news/secu

  6. #PuTTY #SSH client flaw allows recovery of #cryptographic #privatekeys
    The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates #ECDSA nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
    bleepingcomputer.com/news/secu

  7. client flaw allows recovery of
    The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
    bleepingcomputer.com/news/secu

  8. #PuTTY #SSH client flaw allows recovery of #cryptographic #privatekeys
    The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates #ECDSA nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
    bleepingcomputer.com/news/secu

  9. #PuTTY #SSH client flaw allows recovery of #cryptographic #privatekeys
    The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates #ECDSA nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
    bleepingcomputer.com/news/secu

  10. Does anyone have suggestions that can do #cryptographic signature verification of streaming data (as in a pipe)? The problem with #gpg in this case is that it will emit all the data out the pipe, only indicating with an exit code if the signature was good - at which point most of the data may have been processed. #SequoiaPGP is slightly better, withholding the last 25MB until things are fully verified.

    I suspect I need something that signs blocks of the input. Does it exist? #askFedi

  11. @Juro With #single-#use #cryptographic #hashes, we could still enable somewhat strong #anonymity together with strong human id #verification.

    Learning from India’s Aadhar system, it is clear that a single #token isn’t good enough.

    Perhaps something similar to blockchain, where you can mine some tokens that identify you. And you can throw away like wallets to escape tracking when you need to.