Any pronouns. 33.

Professional developer and amateur gardener located near Atlanta, GA in the USA.

I’m using a new phone keyboard, please forgive typos.

  • 16 Posts
  • 1.25K Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle



  • Don’t overthink the metaphor. These things are fragile and fall apart. The “door with a lock” is the “guarantee” (wink wink) that the operating system won’t let programs see memory they shouldn’t be allowed to. Putting your valuables in a safe instead of sitting in the floor would be encrypting the passwords in memory in the metaphor.

    Also, cyber security and physical security are very different. With cyber security you need to understand that there are orders of magnitude more people looking for simple problems. Like a criminal checking every door in the world automatically, just looking for ones that are unlocked. Someone not being a “target for master criminals” isn’t really applicable for this. Besides, that’s a critique of what level of security an individual should have, but pointing out the flaw in Edge is a critique of something that claims to be secure that isn’t.



  • I think the problem is, or at least one I see a lot, is that climate change is already happening, but because it’s gradual and there’s already so much unpredictability you can rarely just point at something specific and say “that’s because of climate change.” And the constant naming of it as “global warming” has done so much damage too, because now when the new weather is cold you still have skeptical conservatives saying things like “global warming my ass!”






  • From the email thread

    It’s just that instead of drowning in the CVE/CVSS noise, we need a high-quality signal for CVEs that matter the most. Things that would certainly have been CVEs even prior to Linux CNA setup. They may not score the highest per CVSS, but in many cases - like in this one - your team has the knowledge that an issue is to become high-profile, so a timely direct heads-up to linux-distros would be appreciated. Where by “timely” I mean, say, a week (and never more than 14 days) before planned full public disclosure. We don’t normally like to sit on semi-embargoed issues with public fixes, but we did introduce an exception for “Linux kernel issues concurrently or very recently handled by the Linux kernel security team” specifically to accommodate the way your team works.

    How does this sound to you?

    Nope, sorry, we are NOT allowed to notify anyone about anything “ahead of time” otherwise we will have to tell everyone about everything. That’s the only policy by which all the legal/governmental agencies have agreed to allow us to operate in, so we are stuck with it.

    From the policy

    As such, the kernel security team strongly recommends that as a reporter of a potential security issue you DO NOT contact the “linux-distros” mailing list UNTIL a fix is accepted by the affected code’s maintainers and you have read the distros wiki page above and you fully understand the requirements that contacting “linux-distros” will impose on you and the kernel community. This also means that in general it doesn’t make sense to Cc: both lists at once, except maybe for coordination if and while an accepted fix has not yet been merged. In other words, until a fix is accepted do not Cc: “linux-distros”, and after it’s merged do not Cc: the kernel security team.

    It sounds like what you’re describing and what the email thread are discussing are pretty different. The email thread was asking to know about things prior to disclosure. You seem to be saying that they should have directly notified the distros list when the fix was up instead of just posting the article or whatever on their site. Two very different discussions.