Remote

Darakian

@darakian@fosstodon.org

mastodon 4.7.3

The mastodon appendage of https://github.com/darakian/

66 Followers

78 Following

5 Posts

Joined May 24, 2022

GitHub:

https://github.com/darakian/

Codeberg:

https://codeberg.org/darakian

Darakian @darakian@fosstodon.org

· 2mo ago

Replying to

@adulau@infosec.exchange Huh, I see. Perhaps it will prove to be academic but I do wonder what the downstream reader is supposed to do when two or more publishers disagree in part or in whole on some advisory. @westonsteimel@hachyderm.io @gcve@social.circl.lu

Darakian @darakian@fosstodon.org

· 2mo ago

Replying to

@adulau@infosec.exchange

Is there any GNA* that is acting as a first mover and demonstrating what “good” looks like? I suspect that this sort of effort will run into disputes relatively quickly and disputes tend to require judgement and grace to resolve. My thinking is that the only records people will bother to “fix” will be ones the publisher did poorly on.

I’m assume GNA is roughly analogous to a CNA from the cve system. Please correct me if I’m wrong.

@westonsteimel@hachyderm.io @gcve@social.circl.lu

Darakian @darakian@fosstodon.org

· 2mo ago

Replying to

@adulau@infosec.exchange @westonsteimel@hachyderm.io @gcve@social.circl.lu The looks great, but where does this validation and conflict resolution take place?

Darakian @darakian@fosstodon.org

· 5mo ago

Replying to

@gregkh@social.kernel.org I spy some rust books back there 👀 Very cool machine. Which model(s) are you running on it?

Darakian @darakian@fosstodon.org

· 5mo ago

jefftk.com

AI is Breaking Two Vulnerability Cultures

A week ago the Copy Fail vulnerability came out, and Hyunwoo Kim immediately realized that the fixes were insufficient, sharing a patch the same day. In doing this he followed standard procedure for Linux, especially within networking: share the security impact with a closed list of Linux security engineers, while fixing the bug quietly and efficiently in the open. His goal was that with only the