[plug] KDE / DCOP vs SMBFS home path.....? (long post, adv. topic)

[Craig Ringer]

> But, Windows != POSIX. Windows filesystems just don't provide everything
> that POSIX expects, and filesystems for POSIX operating systems usually
> don't provide everything that Windows expects. These problems can arise
> from things that UNIX and Windows users believe to be incredibly plain
> and ordinary (such as file ownership and locks), not limited to
> ostensibly special problems like UNIX-domain sockets.

An excellent example is your .ssh/authorized_keys, .ssh/id_rsa{,.pub} . 
You WANT your .ssh/authorized_keys to be world-readable so that sshd can 
authenticate with it. However, you ABSOLUTELY do not want your 
.ssh/id_rsa world readable, or your public key is fair game to anybody 
with a decent password cracker and some computing power. You /do/ have 
an SSH key password, right?!?

These things cannot both be accomplished at the same time using a home 
directory that does not support POSIX permissions.

POSIX is quite a bit (!!) older than NT, so why MS doesn't at least 
support storing POSIX permssions and mapping them to NT ACLs is beyond 
me. Especially given that NT also supports named pipes etc, but 
apparently a "special" verion. Hell, NTFS supports _macintosh_ file 
information in a separate "Stream" and I'm pretty sure it supports POSIX 
file attributes - just not over SMB for some reason. *sigh*.

Craig Ringer