VFS Permission Management

Weltall <[email protected]>
Newsgroups gmane.comp.graphics.crystalspace.devel
Message-ID <CAAR4zyRk+FUrm+cyuXocb4m48PtZ4A5-pTGiPnX98GAeUvQXWQ@mail.gmail.com>
Today the student working on VFSv2 (Eunsoo/touko) asked what to do if his
idea regarding a Set/GetPermission interface was ok.
I've discussed it a bit with jorrit and we wanted to see what others thing
about it.
Essentially touko suggested these signatures:
virtual bool GetPermission (const char *FileName, const char *User,
csFilePermission &oPerm) = 0;
virtual bool SetPermission (const char *FileName, const char *User, const
csFilePermission &iPerm) = 0;

for the interface.
csFilePermission should have something similar to the unix style (so r/w/x
or octals) and user would be the "numeric constants on unix, and security
tokens (user/group) on windows". Probably the x flag will have to be
emulated in windows by doing something (as jorrit noticed) like cygwin by
checking the extension and setting the +x depending on that.
I'm not so sure about the user having a different behaviour depending on
the os, probably would be better to abstract it more considering also that
it would be missing the group field on unix systems.

Any ideas? comments? screams?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Crystal-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-develop
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.