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

help-circle
  • The drop-down text menu with dense options was good design. Adding the quick toolbar for more common tasks was also good design.

    Moving everything from the text menu to the quick toolbar was bad design.

    Just like the evolution of their search functionality. Started as an explorer feature (good), added to the start menu with a focus on program names (good), then they mixed web results from Bing and it’s unclear if a program I’m searching for is installed and it found that or if it exists and the result is a link to some website (bad, if I wanted to search the fucking internet, I’d launch a fucking browser), also insisting on using their browser (wtf, they should have been broken up 20 fucking years ago, instead the courts decided to just fucking ignore them doing the same shit they lost the lawsuit for only much worse now).








  • It’s like so many programmers never evolve past the “playing around with web dev stuff” days. The fact that JavaScript is one of the most used languages is appalling.

    The whole 1+1 = 11 meme made me laugh and then avoid JavaScript whenever possible, but I wonder if many others saw it and thought, “now I’ve gained more experience in JavaScript!”






  • With the hash one, it doesn’t look like that could be exploited by an attacker doing the bad hashing themselves, since any collisions they do find will only be relevant to the extra hashing they do on their end.

    But that encryption one still sounds like it could be exploited by an attacker applying more encryption themselves. Though I’m assuming there’s a public key the attacker has access to and if more layers of encryption make it easier to determine the associated private key, then just do that?

    Though when you say they share the same secret, my assumption is that a public key for one algorithm doesn’t map to the same private key as another algorithm, so wouldn’t cracking one layer still be uncorrelated with cracking the other layers? Assuming it’s not reusing a one time pad or something like that, so I guess context matters here.




  • I remember hearing to not layer encryptions or hashes on top of themselves. It didn’t make any sense to me at the time. It was presented as if that weakened the encryption somehow, though wasn’t elaborated on (it was a security focused class, not encryption focused, so didn’t go heavy into the math).

    Like my thought was, if doing more encryption weakened the encryption that was already there, couldn’t an attacker just do more encryption themselves to reduce entropy?

    The class was overall good, but this was still a university level CS course and I really wish I had pressed on that bit of “advice” more. Best guess at this point is that I misunderstood what was really being said because it just never made any sense at all to me.