Conversation

Notices

1. Embed this notice
   Rob Landley (landley@mstdn.jp)'s status on Monday, 22-Jul-2024 12:33:03 JST Rob Landley

   I haven't commented on crowdstrike because it confirms too many of my priors.

   Monoculture bad. CI/CD instead of cutting releases is playing a game with no checkpoints. Adding complexity to "improve security" has a silent "through obscurity" with a net loss of any other kind. If you can't remember the last time you recovered from backup over a fresh install on virgin hardware, you don't have a backup. Supply chains full of nonfungible vendors...

   • Haelwenn /элвэн/ :triskell: likes this.
   • Blaise Pabón - controlpl4n3 repeated this.
   • Embed this notice
     Rob Landley (landley@mstdn.jp)'s status on Monday, 22-Jul-2024 12:34:29 JST Rob Landley

     in reply to

     Just the Dunning-Kruger implications of outsourcing your core competency to a black box. Losing the in-house ability to perform the task means losing the in-house ability to evaluate the performance of the task, but selecting a vendor who treats the performance of the task as a trade secret?

     I have nothing to say to these people. I cannot help. I do not have a frame of reference that intersects with that stuff being a good idea.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Rob Landley (landley@mstdn.jp)'s status on Monday, 22-Jul-2024 12:35:17 JST Rob Landley

     in reply to

     The comment about confirming too many of my priors is because this kind of situation makes me nervous. It is so obvious to me that they should have done (list of other things) that the social, cultural, economic, and legal reasons they did what they did should probably dominate the discussion.

     "Dude, you horked the tech in a way visible from space and it's turtles all the way down..." I expect they know. And will go right back to building a house on a floodplain until insurance renewals stop.

   • Embed this notice
     Rob Landley (landley@mstdn.jp)'s status on Monday, 22-Jul-2024 12:35:17 JST Rob Landley

     in reply to

     And maybe there is a good reason. "I don't know why you did that" is never a reason to be smug or complacent. I do not know. Finding out new information may change my mind. If it can't, the problem is me.

     "So this bitlocker thing: you made it so you can't access your own locally stored data without talking to a Microsoft cloud server first. You did this to make it 'safer'."

     I don't even know what questions to ask about that. (Is this a multiple launch keys situation? How toxic is your data?)

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Rob Landley (landley@mstdn.jp)'s status on Monday, 22-Jul-2024 12:35:59 JST Rob Landley

     in reply to

     Ah, Windows users don't have to _choose_ bitlocker, Microsoft is turning it on by default during a system update like "microsoft recall" or the recent Mozilla adware tracker.

     https://youtu.be/6GBUFgZ0mHg

     Yup, there's usually a reason if you dig. [Backs slowly away, not breaking eye contact...]

     Haelwenn /элвэн/ :triskell: likes this.