• 1 Post
  • 91 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle











  • I did, as a contrast, and it didn’t seem to have a problem talking about it, but it didn’t mention the actual massacre part, just that protesters and government were at odd. Of course, I simply asked “What happened at Kent State?” And it knew exactly what I was referring to. I’d say it tried to sugar coat it on the state side. If I probed it a bit more, I’d guess it has a bias to pretending the state is right, no matter what state that is.



  • I agree with those that say Inkscape, it’s where I’ve designed all my logos. However, I’ve been tempted to try using FreeCAD to do it lately. I’m not sure if it can export as SVG, but the thought of have a proper parametric tool for designing logos sounds up my ally. I tend to try to treat Inkscape like one, by liberal use of construction lines, but at the end of the day, it really doesn’t like being that precise.






  • Effectively, the other option is passwords, and people are really, really, bad at passwords. Password managers help, but then you just need to compromise the password manager. Strong SSO, backed by hardware, at least makes the attack need to be either physical, or running on a hardware approved by the company. When you mix that with strong execution protections, an EDR, and general policy enforcement and compliance checking, you get protection that beats the pants off 30 different passwords to 30 different sites, or more realistically, 3 passwords to 30 different sites.


  • The modern direction is actually going the other way. Tying identity to hardware, preventing access on unapproved or uncompliant hardware. It has the advantage of allowing biometrics or things like simple pins. In an ideal world, SSO would ensure that every single account, across the many vendors, have these protections, although we are far from a perfect world.