$argon2id$v=19$m=512,t=256,p=1$wCQYS+4N8q5iKLigIZ22gQ$V/fqDkL++GTiMe0Acyk1RbjNr7loyJlppLecbNk93ec

  • 8 Posts
  • 42 Comments
Joined 3 年前
cake
Cake day: 2023年6月14日

help-circle

  • I appreciate you taking the time to implement this and answering some questions! I have a follow up question- What’s the benefit of using asymmetric encryption here? You’re not signing the message ( you probably should imo ) and you don’t appear to support sharing encrypted notes ( i.e a user provides one or more additional public keys that a note is encrypted for ). You’re basically doing symmetric encryption with the pain of key management

    It’d be simpler ( from a user and code perspective )to use symmetric encryption ( something like aes-256-gcm or ChaCha20-Poly1305 for example ) and use key wrapping to avoid encrypting user data directly and you’d have stronger crypto as a result

    You’re right that PGP is a valid encryption method but it’s not very popular in the modern day because it’s very hard to get right. Latacora has a great post on the PGP Problemand the Soatok blogs that u/litchralee linked are well worth a read too








  • I used to run PFSense ( pretty much the same as Opensense ) and really liked it but moved over to Ubiquity in the last year or so. Here’s my 2 cents…

    Go with Ubiquity if you want a single unified interface for managing all your devices. You’ll have “soft vendor lock in”, their kit will work just fine with a mix of hardware but it’s best if everything is Ubiquity

    Go with Opensense if you want complete flexibility in the kit you’re using. I feel likeI had more fine grained control with PFSense than I do with Ubiquity but I think that’s a symptom of how the UI/UX rather than the features

    You can do the same stuff with both options. I’m very happy with my Ubiquity set up, I don’t see myself changing anything anytime soon




  • The CAB Forum only govern public CAs and certificates and the use of certs on the public internet. Your private PKI will be unaffected by the new changes. On top of that the change will be introduced gradually, the first reduction is in March 2026 and will limit certs issued after March 2026 to 200 days so even if you saw some impact for some reason you’d still have a couple of months to put a fix in place

    Freshman need to accept the cert once (hopefully after checking the fingerprint)

    Nobody is checking the fingerprint, nobody





  • irq0tolinuxmemes@lemmy.worldWhat if...
    link
    fedilink
    arrow-up
    4
    arrow-down
    3
    ·
    1 年前

    Take it as a ranty blog interspaced with some furry art.

    You can just ignore the furry art if it’s not your style because helpfully all of the important content is in the text.

    Soatok links to the same Latacora blog on the first line and says that they’re only really going to reword what’s said there.

    I’m not here to litigate the demerits of PGP. The Latacora article I linked above makes the same arguments I would make today, and is a more entertaining read.

    PGP/GPG maintainers have had many years to fix the problems that have been identified but they haven’t. Is it safe when used “properly”? Yes! It’s absolutely safe when used properly but the problem is it’s hard to use full stop.

    I’m not saying modern solutions are perfect, because they’re not but the alternates that Latacora ( and Soatok ) suggest are better. Do you want to encrypt a file? Use age. Use minisign/signify for signing. They do do one thing and do it well. Signal is easy to use and sorts all of the key management for you. Most people don’t know what a private key is. They just know they want encrypted messaging because of the NSA or Snowden or whatever his name was on the news, they can’t remember and they don’t really care.

    PGP has legitimate use cases but the vast majority of people don’t have those cases and should just use Signal. Signal and the Signal protocol is the centralised tool you’re looking for.




  • I feel like I’m missing something here…

    Who’s going to be fingerprinting DHCP messages on your home network?

    Outside of that, fingerprinting or tracking any DHCP info would be the least of my concerns. You have 0 control over any data the moment your devices connect to a public network. What use is DHCP info when you can person-in-the middle all the traffic anyway?

    And anyway, what info are you concerned about? Having had a VERY quick browse of RFC2131 the worst thing would be “leaking” the device MAC address which can be discovered via several other means anyway


  • irq0toMicroblog Memes@lemmy.worldOutstanding idea.
    link
    fedilink
    English
    arrow-up
    25
    ·
    2 年前

    Pretty sure they meant Boeing Starliner, which is currently docked to the ISS but whose return to earth is delayed because of several hydrogen leaks and faulty manoeuvring thrusters. They’ve tested the thrusters since docking and only 4 of the 5 worked.

    SpaceX Starship on the other hand is a test vehicle. It’s not meant to explode of course but these things are expected from time to time. SpaceX go for more of a “throw things at the wall and see what sticks” approach. It looks like they don’t know what they’re doing but they really do, Falcon9 is the most successful rocket ever built after all