One of the thing about encrypted virtual drive is that you have to declare its size when you create it for most packages which limits what you can do with it. It creates number of profound issues: It will contain un-used space which will take up space if it hosted in one of the foggy cloud's drive, and when you fill it up not much you can do about resizing it dynamically other than create a new larger one and copy data over. If it is hosted in cloud drive then it will also incur a lot of data going back-&-forth as file's metadata, like access timestamp, etc., are updated for which transport layer is at your ISP's whims. God forbid that the packages doesn't fall out favor and ceases as well is a concern too.
-----Original Message----- From: fromvendor <[email protected]> Sent: Monday, September 09, 2024 1:37 PM To: 'Gnucash Users' <[email protected]> Subject: Re: [GNC] Recommendations for hosting gnucash file - Google Drive, Microsoft 365, Local server? Regarding encryption, One thing I had done is install one of those virtual drive encryption software and created an encrypted disk (cryptainer) that I need to mount when I want to use its contents. I then backup up the drive-volume file when the software is closed for the backup. Give me encryption without much fuss. -g -----Original Message----- From: gnucash-user [mailto:[email protected]] On Behalf Of John Ralls Sent: Monday, September 09, 2024 12:27 PM To: David G. Pickett Cc: Gnucash Users Subject: Re: [GNC] Recommendations for hosting gnucash file - Google Drive, Microsoft 365, Local server? That said, if you use the SQL backend with a server, i.e. mariadb/mysql or Postgres, you get password protection and database locking with much less latency than any file-sharing mashup provides. You do need to learn about the care and feeding of the server including ensuring that it’s secure if it’s exposed to the Internet, configuring users, and arranging for backups. Regards, John Ralls > On Sep 9, 2024, at 07:16, Derek Atkins <[email protected]> wrote: > > The GnuCash team, historically, have explicitly decided that GnuCash > leave encryption and other password protection to external tools and > NOT perform it internally. GnuCash is a financial tool, not a security tool. > > -derek > > On Mon, September 9, 2024 9:59 am, David G. Pickett via gnucash-user wrote: >> The security concerns beg the question, should GnuCash files be >> password protected by the app? It'd slow save and open a bit, but >> then you are less worried about the files being snooped. >> >> There are also ways to encrypt local files, and back up the encrypted >> files to you network drive. Just make sure you do not lose the password! >> _______________________________________________ >> gnucash-user mailing list >> [email protected] >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> > > > -- > Derek Atkins 617-623-3745 > [email protected] www.ihtfp.com > Computer and Internet Security Consultant > > _______________________________________________ > gnucash-user mailing list > [email protected] > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
