I suggest you ...

Allow the database to be secured by way of a password

Corresponding bugzilla item: https://bugzilla.gnome.org/show_bug.cgi?id=700803

The aim is not absolute security but would prevent casual access to the information held. (Windows ACLs go some way towards this but any administrator could view the information.)
If this would be better done by securing the files outside the application, could someone tell me how?

102 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    David DenholmDavid Denholm shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared a merged idea: Add password protection  ·   · 

    7 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • WillynuxWillynux commented  ·   ·  Flag as inappropriate

        I'm surprised this is not the first feature implemented in a software that handles sensitive data.

      • John AntolakJohn Antolak commented  ·   ·  Flag as inappropriate

        Easy - Create a Trucecrypt volume when Mounting use your own Password
        Save your ???????.gnucash account in the now mounted drive
        Hey Presto!!!! whenever you dismount the drive the data is seamlesly encrypted

      • Nila AkashNila Akash commented  ·   ·  Flag as inappropriate

        See feature request "Prevent accidental changes by locking a fiscal period". If any type of password is implemented, perhaps there could be different levels or types of password protection:

        1) Prevent all access
        2) Print cheques
        3) Modify data in a previous period, etc.

      • MitchMitch commented  ·   ·  Flag as inappropriate

        I would like to add what i hope is not "unhelpful".
        I think what most would like to see is "application access" security. not data security. so allowing sql to provide security (user/pass) used by GnuCash to access/login to SQL would provide what most people need... also this would be part of foundation for multi user and internal ACL who can print checks delete transactions...
        example you might have a part time person that you want to enter data but you don't want them printing checks or trying to import bank data...

        just to be clear this would not "ENCRYPT" any data or provide any read data security... just a basic level and access controls...

      • cstimAdmincstim (Core Developer, GnuCash) commented  ·   ·  Flag as inappropriate

        [Somebody gave the following description of the use case:] In the real world, mom, pop and the kids all use the same account on the same computer. Might not be very security conscious, but that's the way it is. A simple password feature might not defeat 1337 hackers, but it would be more than enough to discourage casual snooping by curious fellow users.

      • GnuFanGnuFan commented  ·   ·  Flag as inappropriate

        cstim, I have read the FAQ, but am still struck by the need to implement password protection. The arguments put forth in the wiki ignore the business realities of those who use Gnucash. Users do not necessarily have the access / ability to implement a separate security layer.

        This feature alone would do more to drive adoption of Gnucash than any other listed here. I am tired of meeting people who refuse to use this solely on this objection.

      Feedback and Knowledge Base