Of course you need to select an algorithm in a compatible library, of which
there are many. I was just responding to the idea that a unchanging common
password would be hard coded is open source, a very odd idea. If you used
triple DES, for example, all the open source would show is that you used triple
DES and got a password from the console.
I have coded things like this, and found several ways to keep the password out
of the code, like asking the user for it at the start. GnuCash would hold it
for use when it saved, so I suppose you might find it in a crash dump file, if
it crashed, and a core dump was generated, and that got shared into an
untrusted space, like with a shared folder as current working directory.
On Monday, September 9, 2024 at 09:34:38 PM EDT, David Carlson
<[email protected]> wrote:
Not just a pop-up. All the security stuff would have to be added too, and the
developers have made it abundantly clear that they do not want to do that when
a huge development effort would be required to do it right. From the rest of
this thread you can see that no size fits all anyway. They are confident that
we users can find a solution outside of their bailiwick.
On Mon, Sep 9, 2024 at 5:35 PM David G. Pickett via gnucash-user
<[email protected]> wrote:
Nobody suggested putting a password in gnucash, just a pop up dialog to ask the
user for it.
_______________________________________________
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.
--
David Carlson
_______________________________________________
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.
