• 0 Posts
  • 36 Comments
Joined 1 year ago
Cake day: July 2nd, 2023
  • Hasherm0n@lemmy.worldtoAsklemmy@lemmy.ml•What was the worst book you’ve ever read?
    3·
    16 days ago

    That was the beginning of the end for me. I think by the time I got to that part the series had already been going downhill but I remember that being a really sharp turning point.

    I tried to press on a little further. The introduction of the straw man nation with the innocent child king who’s only existence was to be blown the fuck out by the brilliance of objectivism is when I finally decided I just couldn’t go on.

  • Hasherm0n@lemmy.worldtoAsklemmy@lemmy.ml•What was the worst book you’ve ever read?
    3·
    16 days ago

    Ooo, I was trying to think of what to answer in this thread and you just reminded me of another Orson Scott Card book, Empire.

    Absolute trash. Prior to that I had read all of the Ender and Bean series and loved them. Didn’t know much about Card personally, but picked up this book because it was supposed to be tied in with a video game I was looking forward too.

    Reading this book is how I found out what a shitty person he really is. It was basically all him hitting you over the head with his shitty fascist ideology while jerking off to a bunch of military porn like a dollar store version of Tom Clancy. I never did play the game.

  • Hasherm0n@lemmy.worldtomemes@lemmy.world•I am going to violate the Geneva convention
    9·
    3 months ago

    What you want is NIST 800-63b https://pages.nist.gov/800-63-3/sp800-63b.html#memsecret

    Specifically sections 5.1.1.1 and 5.1.1.2.

    Excerpt from 5.1.1.2 pertaining to complexity and rotation requirements:

    Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

    Appendix A of the document contains their reasoning for changing from the previous common wisdom.

    The tl;dr of their changes boil down to length is more important than any other factor when it comes to password security.

    Edit to add:

    In my personal opinion, organizations should be trying to move away from passwords as much as possible. If your IT team seems to think this system is so important that they need to rotate passwords every month, they should probably be transitioning to hardware security tokens, passkeys, or worst case, password with non-sms MFA.

    Now I know nothing about the actual circumstances and I know there are plenty of reasons why that may not be possible in this specific case, but I’d feel remiss if I didn’t mention it.

  • Hasherm0n@lemmy.worldtomemes@lemmy.world•I am going to violate the Geneva convention
    28·
    3 months ago

    Any organization still doing this is a decade behind best practices. NIST published new recommendations years ago that specified getting rid of the practice of regular forced password resets specifically because they encourage bad practices that make passwords weaker.

    Of course it doesn’t help that there are some industry compliance standards that have refused to update their requirements, but I don’t know of any that would require monthly password changes.