{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiakdlgtx734ky5mckzmjcpfhri232ahqofdtqwrptednn2yavvave",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mldyakc7yvs2"
  },
  "path": "/t/is-secureblue-linux-secureblue-dev-also-vulnerable-by-these-three-recent-linux-vulnerabilities-copy-fail-copy-fail-2-and-dirty-frag/37728#post_16",
  "publishedAt": "2026-05-08T14:27:16.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "VeryRandomUser:\n\n> Can you please provide a source?\n\nDid you even look into their Github repo? Or their public dev channel on Discord? Either would have been enough to validate it, instead of repeating your own statements.\n\nVeryRandomUser:\n\n> similar to how I provided one to explain how it’s ( CVE-2026-43284 (Dirty Frag – ESP Component) ) still unpatched.\n\nNo, you provided a source which did not mention secureblue at all.",
  "title": "Is secureblue linux [ secureblue.dev ] also vulnerable by these three recent linux vulnerabilities - Copy Fail, Copy Fail 2 and Dirty Frag?"
}