[Digikam-devel] [Bug 145252] Umask settings used for album directory, not for image files

Achim Bohnet ach at mpe.mpg.de
Fri Oct 19 15:12:32 CEST 2007

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From ach mpe mpg de  2007-10-19 15:12 -------
> >So for new files, I would think that respecting the umask
> >should be ok. 
> Fine for me too...

 new files: I agreed.
 modified files: use same protection as the unmodified version had.

> >For thumbnails I do understand the problem that this might make
> >files visible to other users, which originally are not visible
> >(due to paths right settings etc.).
> >So the question is: what should we do?
> >Should this be made a configuration option for the thumbnails,
> <or better left as is? 
> No need a setting for thumb. This will bloat the config (:=))), and most users we don't care about...]
> Why not to replicate the same umask from original image to thumb files ?

Nope.  That's as I tried to explain before IMHO bad design.

IMHO a primitive but clean solution to sharing thumb problem could be
use something like LibraryPathAccess=[default|private|shared] (without
GUI until we properly support it ;)

If set to 'shared' search/create first


with thumb having the same protection as the image when created/updated.

Default == as it's right now.  Optional: For 'private'
~/.thumbnail is used and ~/Pictures/ (700) and digikam.db (600), with
as a start checking (changing after asking) protection ~/Picture and

How to realize write access is left as an excercise for the user for
now ;)  To make it possible digikam should use try use umask for
new stuff and keep protection when modifying files.


More information about the Digikam-devel mailing list