{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihizzliqb7lixjj5xmyjehyei6hlqthtyii3eqedcpxngrsvv45rm",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mldy7lhy6wt2"
  },
  "path": "/t/is-secureblue-linux-secureblue-dev-also-vulnerable-by-these-three-recent-linux-vulnerabilities-copy-fail-copy-fail-2-and-dirty-frag/37728?page=2#post_21",
  "publishedAt": "2026-05-08T14:49:10.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "@RoyalOughtness",
    "Features | secureblue"
  ],
  "textContent": "I have marked it as the solution.\n\nI would however still very much appreciate, if @RoyalOughtness provides his thoughts on this topic. Like was this something that could have been prevented for secureblue in particular by pre-hardening some features or things as preventive measure, similar to how secureblue pre-hardens other things as mentioned on their website. Features | secureblue",
  "title": "Is secureblue linux [ secureblue.dev ] also vulnerable by these three recent linux vulnerabilities - Copy Fail, Copy Fail 2 and Dirty Frag?"
}