Six sided devops engineer and baseball fan

I am also @Quill7513@slrpnk.net, but this is my primary and more active account. The slrpnk.net account is for ecology and lemmy.world stuff

https://keyoxide.org/BAF9ACFBBA5B9A51A680D77CEF152DAE039C5CF5

  • 0 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle









  • The Cuuuuube@beehaw.orgtoLinux@lemmy.mlA word about systemd
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 month ago

    this is everything i see monitoring Linux boxes everyday. we’ve shifted mostly to OpenRC about it. i can’t imagine defending SystemD if you have experienced anything other than it and SysInitV. yeah compared to SysInitV, it’s really nice, but to say it’s good and stable? that’s like praising your landlord for all the work they do and the reason they haven’t fixed your broken dishwasher is because they’re so busy from what a good landlord they are


  • The Cuuuuube@beehaw.orgtoLinux@lemmy.mlA word about systemd
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    2 months ago

    In fact, the situation has gotten much worse. The coupling of SystemD’s components to each other has gotten tighter. The coupling of things that aren’t SystemD to SystemD has gotten tighter. SystemD itself has gotten less stable. The overall result? Our operating systems require more, not less, troubleshooting, and they’re less, not more, enjoyable to use and develop on


  • The Cuuuuube@beehaw.orgtoLinux@lemmy.mlA word about systemd
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    4
    ·
    2 months ago

    SystemD has been such a frustration the last couple years with the wonderful simplicity and stability it used to provide managing a system completely out the door as its main development company (RedHat) has stopped giving any kind of a shit about being a positive force in the world. We all shoulda listened 10 years ago when the greybeards were telling us not to fall for an init system trying to do too much.







  • Sure yeah. I think corpos suck, too. That’s why I don’t prefer 1password. But Firefox puts their passwords into a file, too (two actually). Key3.db and Logins.json, both with known locations, and encrypted using AES-256-GCM which is… Decent but I prefer to go a little more hardened. The thing with keepass is the following:

    1. Its open source, no corpo
    2. The file encryption you select can be as hardened as you want
    3. No one but you need know the location of your file
    4. It offers 2fa which Firefox password manager doesn’t
    5. Firefox password manager is more susceptible to social engineering attacks is mainly what I was worried about but it seems like you’ve got a good handle on it.
    6. You don’t have to integrate keepass with the browser to use it

    But I want to make it abundantly clear. @Dyskolos@lemmy.zip has not recommended storing your passwords in a file. They have suggested storing your passwords in a mechanism that can be as secure as your hardware is capable of securing and keeping the location of that up to your own decision making.

    But also. Promise me this. If you’re going to keep using Firefox as your password manager:

    1. Don’t use sync. That’s run by Firefox’s corporate arm, Mozilla PBC
    2. Use a primary password of at least 32 characters
    3. Consider rotating your password on a regular interval, like on your birthday