don't think so. Benny has the right idea. What should be the default
perms on the db files? some are ug+r, some are ugo+r
On Wed, Jan 7, 2009 at 8:16 AM, Jérôme <romjerome@...> wrote:
> Is it related to bug #2233 (Note:~6710) ?
>
> http://www.gramps-project.org/bugs/view.php?id=2233
>
>
> Benny Malengier a écrit :
>> Everyone, the short of this mail:
>> Do find on the .open( function in dbdir.py, only in the function
>> __open_table the mode 0666 is passed, and things become readable for
>> other in grampsdb dirs. In the other places open is used, the default of
>> 0660 is used.
>> This is not a good setting, we should have 0666 everywhere, or 0660
>> everywhere.
>> Which one however? I would take 0660. If 0660 you depend on the umask
>> setting to degrade 0666 to the normal 0644
>>
>> LOnger version:
>> No idea Gerald. But as the db contains private data, I would rather want
>> it to be not world readable in all cases. No need for another user on
>> the pc to be able to read the data.
>>
>> Looking into it, one can pass a mode setting with the database opening:
>> http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_open.html
>>
>> and the file gen/db/dbdir gives in the open routine a mode of 0666
>> (default is 0660), which is changed by the umask value of the process so
>> goes to what you see normally of 0644.
>> Hence, the tables that are not 'read for other' are those opened
>> directly in GRAMPS in load routine of dbdir and not via the open_table
>> function, so those use the default value of 0660, with no permissions
>> for other.
>>
>> Anybody know why 0666 was chosen in the first place?
>> It makes it possible to play with the umask and get the protection you
>> want, but aunt martha has no use for this.
>>
>> Benny
>>
>> 2009/1/6 Gerald Britton <gerald.britton@...
>> <mailto:gerald.britton@...>>
>>
>> HI -- I noticed that, in my .gramps/grampsdb/<database> directory,
>> some files have world-read set but these do not:
>>
>> event_id.db
>> family_id.db
>> media_id.db
>> name_group.db
>> note_id.db
>> person_id.db
>> place_id.db
>> primary_map.db
>> referenced_map.db
>> repo_id.db
>> source_id.db
>> surnames.db
>>
>> Is this a bug or a feature? Why, for example, does person.db have
>> world-read set but person_id.db does not? This causes me a little
>> hardship when rsyncing between different machines since the userids
>> differ between the machines.
>>
>> ------------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It is the best place to buy or sell services for
>> just about anything Open Source.
>> http://p.sf.net/sfu/Xq1LFB
>> _______________________________________________
>> Gramps-devel mailing list
>> Gramps-devel@...
>> <mailto:Gramps-devel@...>
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It is the best place to buy or sell services for
>> just about anything Open Source.
>> http://p.sf.net/sfu/Xq1LFB
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Gramps-devel mailing list
>> Gramps-devel@...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
>
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Gramps-devel mailing list
> Gramps-devel@...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
|