#5 - Client Drive Mapping for UNIX apps
By Fat Bloke on Jan 30, 2007
Out of the box, SGD is pre-configured so that any remote apps you run cannot touch the drives on your client device, e.g. your Windows PC.
Reasons for this may be to protect against "contamination-in", where viruses, malware etc may be uploaded to your protected server-side apps.
Another reason may be to protect against "data leakage-out", where you don't want sensitive data leaking out of the internal network.
But at other times you really, really do want to open or save files to your local drives.
So it was great to see yet another cool feature appearing in the SGD 4.3 release, Client Drive Mapping for UNIX apps.
This means that I can run an app on a Solaris or Linux server, say StarOffice, and have that application "see" my local client's filesystem.
It works like this:
And here's how you set it up on the application server:
- Create a mount point:
chmod 755 /smb
- Export it:
On Solaris you can add a line like this to /etc/dfs/dfstab
share -F nfs -o rw -d "UNIX Drive Mapping" /smb
- Restart NFS
On Solaris 10:
svcadm enable network/nfs/server
- Install the SGD Enhancement Module (tem) on the Solaris server:
download it from http://yourservername/tarantella/cgi-bin/modules.cgi
- And start the drive mapping component:
The Administration Guide tells you how to set up the SGD server and how to control which users can/cannot use client drive mapping.
So the end result allows me to see something like this:
...which is me running StarOffice on Solaris 10 accessing files on my Mac OS X Desktop.
Pretty cool huh?
So it makes it into my Cool List at #5.