{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib3qx7tt7j3fmcvjg27vcya6kzosx754vjrys2dulyb57giubxena",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkbeilupomr2"
  },
  "path": "/t/veracrypt-concerns/37344#post_3",
  "publishedAt": "2026-04-24T19:51:22.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "old thread:"
  ],
  "textContent": "DailyChems:\n\n> **TLDR** : It’s just more work and licenses can be complicated.\n>\n> I found this in an old thread:\n>\n>> Building specific distribution packages for each Linux family (mainly rpm and deb) adds some extra work but it will a good thing for the future.\n>>\n>> As for PPA on Launchpad, there could be a licensing issue because we are obliged to stick with the TrueCrypt license and even if it is an open source , there are those who think that it is incompatible with open source.\n>  I’m not a lawyer, but my personal opinion is that the TrueCrypt license is a valid open source license so I don’t see any problem in this side.\n\nI don’t know what you mean with license issues?\nYou just need fill the metadata field with the correct license.\n\nAnd you also don’t need to package for every platform, just make a Flatpak, then you package ones and it runs everywhere",
  "title": "VeraCrypt concerns"
}