We have a Tiger server (10.4.7) box that is “Connected to a Directory System” – our OD server. This box is specifically for serving group shares via AFP, SMB, and SCP/SFTP. Everything works well until we get to SCP/SFTP. 😕 Users connecting via those protocols (using WinSCP for example) get dumped at the root of the box.
I have looked at the option of employing a CHROOT jail. Doesn’t look like fun. Currently I have tried setting the NFSHomeDiretory attribute on the box to a static value – #/Volumes/mySharedDevice. This works GREAT to direct SCP/SFTP users to the right place when connecting. Unfortunately, it also appears to cause “mySharedDevice” to show as an available volume when connecting via AFP even though AFP sharing is NOT enabled on the volume in WGM.
Is this a bug, or the way it is supposed to be for some strange reason? I really need this to NOT work this way and I’m wondering if I can change some other attribute mapping to stop it.
Tim
UCLA GSEIS
.
.
Comments are closed