home.social

Search

1000 results for “ezcrypt”

  1. Encrypted messaging straight from the terminal! 💯

    🔐 **XMTP** — TUI chat client for E2E messaging

    🗨 MLS-based encryption, DMs/groups, streaming + profile-based CLI

    🦀 Written in Rust & built with @ratatui_rs

    ⭐ GitHub: github.com/qntx/xmtp

  2. #encryptionist refers to technologists and developers who prioritise cryptographic security and technical control as an end in itself - replacing human trust and open social relationships with code-enforced systems, embodying the #geekproblem tendency to solve political and social problems with technical fixes rather than addressing any underlying social dynamics.

    hamishcampbell.com/?s=Encrypti

  3. Encryption ≠ permanent protection.
    “Encryption is treated as final when it’s temporary.” - Garfield Jones
    • Capture now, decrypt later risk
    • Legacy crypto still active
    • Visibility gaps persist

    technadu.com/why-encrypted-dat

    #QuantumSecurity #PostQuantum #Encryption #CyberSecurity

  4. Encryption ≠ permanent protection.
    “Encryption is treated as final when it’s temporary.” - Garfield Jones
    • Capture now, decrypt later risk
    • Legacy crypto still active
    • Visibility gaps persist

    technadu.com/why-encrypted-dat

    #QuantumSecurity #PostQuantum #Encryption #CyberSecurity

  5. Encryption ≠ permanent protection.
    “Encryption is treated as final when it’s temporary.” - Garfield Jones
    • Capture now, decrypt later risk
    • Legacy crypto still active
    • Visibility gaps persist

    technadu.com/why-encrypted-dat

    #QuantumSecurity #PostQuantum #Encryption #CyberSecurity

  6. Encryption ≠ permanent protection.
    “Encryption is treated as final when it’s temporary.” - Garfield Jones
    • Capture now, decrypt later risk
    • Legacy crypto still active
    • Visibility gaps persist

    technadu.com/why-encrypted-dat

    #QuantumSecurity #PostQuantum #Encryption #CyberSecurity

  7. Setting up email #encryption is a great first #UserFreedom step for everyone: u.fsf.org/1bq

  8. It has been in the news lately that quantum computers might break asymmetric encryption much sooner an easier than previously thought.

    Passkeys has been recommended for a while now instead of passwords, but does this not change that?

    If I'm using a randomly generated password with 256+ bits of entropy, would that not be more sure than a passkey?
    (I'm not taking into account that passkeys has other advantages like that they can't be grabbed in a phishing attack).

    #Infosec #Security #Passkeys #Passwords #QuantumComputers #Encryption
  9. It has been in the news lately that quantum computers might break asymmetric encryption much sooner an easier than previously thought.

    Passkeys has been recommended for a while now instead of passwords, but does this not change that?

    If I'm using a randomly generated password with 256+ bits of entropy, would that not be more sure than a passkey?
    (I'm not taking into account that passkeys has other advantages like that they can't be grabbed in a phishing attack).

    #Infosec #Security #Passkeys #Passwords #QuantumComputers #Encryption
  10. WTF?
    What kind of notification is this, and what am I suuposed to do with it?
    I guess all one has to do is to skip #encryption.

    #matrix #schildi

  11. @scottymace Signal’s database #encryption wasn’t the problem in this instance, it was the amount of detail in the content of push notifications (and it’s persistence) in the iOS ̶A̶P̶N̶ ̶ notifications database

    choosing to use a #Signal fork like #Molly instead of the official client brings its own set of risks and trade-offs to be weighed in the context of your specific threat model

  12. @scottymace Signal’s database #encryption wasn’t the problem in this instance, it was the amount of detail in the content of push notifications (and it’s persistence) in the iOS ̶A̶P̶N̶ ̶ notifications database

    choosing to use a #Signal fork like #Molly instead of the official client brings its own set of risks and trade-offs to be weighed in the context of your specific threat model

  13. @scottymace Signal’s database #encryption wasn’t the problem in this instance, it was the amount of detail in the content of push notifications (and it’s persistence) in the iOS ̶A̶P̶N̶ ̶ notifications database

    choosing to use a #Signal fork like #Molly instead of the official client brings its own set of risks and trade-offs to be weighed in the context of your specific threat model

  14. @scottymace Signal’s database #encryption wasn’t the problem in this instance, it was the amount of detail in the content of push notifications (and it’s persistence) in the iOS ̶A̶P̶N̶ ̶ notifications database

    choosing to use a #Signal fork like #Molly instead of the official client brings its own set of risks and trade-offs to be weighed in the context of your specific threat model

  15. @matrss @mahlzahn I am still running on this system here (which has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  16. @matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.