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

help-circle



  • Yeah that was part of the brand reshuffling they did to obfuscate things. Lync was their shitty chat app they tried to convince businesses to use that everyone hated. They bought Skype, renamed it to Microsoft Teams, renamed Lync to Skype for Business, and killed MSN Messenger. When people still didn’t want to use LyncSkype for Business, then they killed that as well, and now it’s just MS Teams.




  • I was similar, used Linux for work/programming but Windows for gaming. I refuse to update to Win 11 though, and with 10 going EOL I was faced with a problem. I’ve been using Steam Deck for about a year now with no problems so I figured I’d try going 100% Linux again. Ran my Library through protondb and nearly every single game was supported. I made the cutover about a month ago (just in time as well as literally a week before I made the switch copilot got stealth installed on my system).

    So far I haven’t run into a single game that has failed or that I’ve even needed to change the options to get running. Now I don’t play LoL so I can’t speak to that specific game, and I have kept my Win 10 install if I do run into something that I can’t get running that I absolutely can’t live without, but so far I haven’t needed to boot into Windows since I made the switch. I think you might be surprised how few games won’t function in Linux these days.


  • While it’s true I haven’t personally tried more than about a dozen of my games I will point out that 1) that covers a wide swath of genres, publishers, and game engines, and 2) I ran my entire library of several thousand games through protondb before hand to have some idea of what I was in for and out of all those thousands less than 10 reported as not functioning. Of the ones that wouldn’t work most actually can run, but the publishers are banning people who play under Linux. The most notable from that list would be Destiny 2 and GTA 5. So yes greater than 90% of all games run fine in Linux these days either straight out of the box or with simple configuration tweaks.









  • That would run face first into proprietary info and corporate classified info.

    Behold all the fucks I do not give. If it’s that critical they lose all claim to being proprietary. It’s just like patent, there’s no such thing as a secret patent, so anything that safety critical doesn’t get to stay secret either.

    Regulation won’t detail what a company does to that level. They might say something like “fasteners shouldn’t come loose” but it wouldn’t have a torque spec.

    It doesn’t now but it’s utterly trivial to fix that. Just make the regulations say that components must meet the manufacturer specifications and require manufacturers to publish and maintain all the specifications of all safety critical components. If they want to keep it secret then that means it’s not safety critical and they’re responsible for any accidents resulting from its failure.



  • It’s because layering doesn’t really gain you anything so it only has downsides. It’s important to differentiate encryption and hashing from here on since the dangers are different.

    With hashing, layering different hashing algorithms can lead to increased collision chance and if done wrong a reduced entropy (for instance hashing a 256 bit hash with a 16 bit hashing algorithm). Done correctly it’s probably fine and in fact rehashing a hash with the same algorithm is standard practice, but care should be taken.

    With encryption things get much worse. When layering encryption algorithms a flaw in one can severely compromise them all. Presumably you’re using the same secret across them all. If the attacker has a known piece of input or can potentially control the input a variety of potential attack vectors open up. If there’s a flaw in one of the algorithms used that can make the process of extracting the encryption key much easier. Often times the key is more valuable than any single piece of input because keys are often shared across many encrypted files or data streams.


  • Banks usually have the absolute worst password policies. It’s typically because their backend is some crusty mainframe from the 80s that limits inputs to something absurdly insecure by today’s standards and they’ve kicked the upgrade can down the road for so long now that it’s a staggeringly monumental task to rewrite it all. Thankfully most of them have upgraded at this point, but every now and then you still find one that’s got ridiculous limits like a maximum password length of 8 and only alphanumeric characters (with no 2FA obviously).