{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid4yyzjcnkpok6dc6svhywijjdg3mklwv5aqitl6eemidtx5iroty",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mjkaxodzj4n2"
  },
  "path": "/t/are-appimages-a-generel-security-risk/37077#post_14",
  "publishedAt": "2026-04-15T15:18:54.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "Volume Types | Cryptomator Documentation"
  ],
  "textContent": "seize:\n\n> As far as I can tell, no Cryptomator does not use _fuse2_ on Linux, and requires _fuse3_ instead.\n>\n> Reference: Volume Types | Cryptomator Documentation\n>\n>> ## **Linux-Based OS**\n>>\n>> ### FUSE\n>>\n>> **Requirements:** Linux, `fuse3` installed\n>>\n>> FUSE on Linux works only if the `fuse3` package is installed. Luckily, `fuse3` comes pre-installed on many Linux distributions.\n>\n> Note: this requirement is separate from the appimage requirement for _fuse2_ to be installed.\n\nany1:\n\n> seize:\n>\n>> unmaintained _fuse2_ library\n>\n> The newer appimage runtime does not use fuse2 anymore.\n\nSo does the Cryptomator .AppImage use outdated libraries or not?",
  "title": "Are AppImages a generel security risk?"
}