Hi,
Key link implementation in filesys is actually using real symlinks.
That mean the key link
system/sw/xorg/current -> system/sw/xorg/mytest
is translated into :
/etc/kdb/system/sw/xorg/current -> /etc/kdb/system/sw/xorg/mytest
The problem appear when link source is owner by one user and link
target by another :
user:yl/sw/mysoft/current -> user:foo/sw/mysoft/take-this-one
translated into:
/home/yl/.kdb/user/sw/mysoft/current ->
/home/foo/.kdb/user/sw/mysoft/take-this-one
The difficulty is to be able to find the target key name from the
target file name. I see
two possibility :
* Loop for 0 to xxxxx getpwuid(loop) and compare home directory
against the start of the target filename (euurrrk) ;
* Consider key inside user folders _ALWAYS_ have their owner UID set
to its relative user. This way we could look the owner UID of the target
and then have its userDomain ; Not really reliable since on some systems
many different user names can have same UID.
So, if i'm not wrong there is only two true possibility :
* Forbid "cross user" key linking (keys targets will only be
"user/...." and "user:userDomain" not allowed)
* Change implementation of key link into filesys : remove usage of
real symlinks and put the link target as data into the key source file.
This way, key link's target are stored "as-is" with user domain and
there is no links resolving problem. This is the way i like the most,
but that mean
this filesys backend will not be compatible with previous ones.
Perhaps you'll have better idea ?
Regards,
Yannick.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list
