Add basics users "Rights" into xnview.ini file

[oops66]

Hello,

Request: Add basics users "Rights" into xnview.ini file for a basic security/safety_mode.

It would be very interesting if XnViewMP (and xnview) could manage some basic users rigths and permissions.
So an hidden option (not easy accessible, into the xnview.ini file for example --- and/or --- via the GUI: toggle on/off with a password as option) to give the ability to protect data (images, videos, etc..) for a particular user (useful into a child profile, for example) even if, of course, it can be also usually done with/via the system.

Code: Select all

... into the .ini file of the user
... user "rights"
allow delete operations = 0
allow write operations = 0
allow move operations = 0
allow copy operations =0
allow lossless operation = 0
etc...

[m.Th.]

even if, of course, it can be also usually done with/via the system.

This.

Everything else is a false security wrt to files.
In fact, Pierre should duplicate the most part of the OS rights engine (account management, passwords, propagation of rights, management of rights etc.) without a decisive result because the other "user" can easily overcome / bypass the XnView by using so many viewing and on-disk management options available today, including the ones from OSes itself. Do a specific user for this purpose. Especially if it is a child you can configure many other things behind file access: internet, allowed programs etc.

Wrt to on-database management, (keywords, rating/coloring, metadata etc.) IMHO isn't worth it (yet).

[oops66]

...because the other "user" can easily overcome / bypass the XnView by using so many viewing and on-disk management options available today...

Yes, it's that why I said "basic" ... even if it is interesting only for specific usages ... and even if it is only a basic security/safety_mode
(very useful into a child profile account, for example & not easily accessible, into the xnview.ini file for example for shared photo folders)

Do a specific user for this purpose.

...It's already done ... but not very user friendly to manage the chown -R, and chmod -R, groups, etc ... for only fews shared images folders frequently updated/filed.