Skip to contentSkip to conversation

Secure network fileserving Linux <-> Linux

OFFTOPIC Jesse Pollard 2 participants 2 messages Sep 7, 2001

lore
Share & tools
lore
#0 lore raw

Jamie Lokier <[email protected]>:

Quoted 5 lines
Quoted 4 lines · Jesse Pollard
Quoted 3 lines

Kerberos won't help either - The only parts of NFS that were kerberized was the initial mount. Everything else uses filehandles/UDP. Encryption doesn't help either - slows the entire network down too much.

Quoted 7 lines
Quoted 3 lines

I disagree! First of all you can always use NFS over TCP, so much for "every thing else uses filehandles/UDP". (No that this improves security, but it can improve reliability!)

It can improve security if you use NFS over TCP over SSL...

That may be easier to configure than IPSec in some environments.

I've never seen that used. I assume the procedure is something like:

1. login on client (requires home directory be local)
2. ssh to server (local window for password)
3. user mode mount to another directory (assuming not mounting working directory - marked busy, though that might be allowed)
4. use another window for local usage.

mountd port has to be redirected
nfsd port(s) have to be redirected (I think, might not apply to server) biod port(s) have to be redirected
lockd port(s) have to be redirected (unless nolocking) statd port(s) have to be redirected (not sure)

And only a single user per host (not unreasonable).

Would it also work for windows/Macs?

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]

Any opinions expressed are solely my own.

#1 lore raw
Quoted 7 lines · Jesse Pollard
Quoted 2 lines

It can improve security if you use NFS over TCP over SSL... That may be easier to configure than IPSec in some environments.

I've never seen that used. I assume the procedure is something like:

1. login on client (requires home directory be local)
2. ssh to server (local window for password)

Or you can use the `openssl' program.

Quoted 6 lines

3. user mode mount to another directory (assuming not mounting working directory - marked busy, though that might be allowed)
4. use another window for local usage.

mountd port has to be redirected
nfsd port(s) have to be redirected (I think, might not apply to server)

Really, the only critical one if you're worried about people reading/writing your data is nfsd. mountd is second most important, but not really if you're using the user-space NFS server.

Quoted 1 line

biod port(s) have to be redirected

No need for biod.

Quoted 2 lines

lockd port(s) have to be redirected (unless nolocking) statd port(s) have to be redirected (not sure)

I'm not sure about statd either. It would be safest to run this over SSL.

Quoted 1 line

And only a single user per host (not unreasonable).

You could have multiple users per host, with appropriate funky mounts so each user can only access their own secure mounts. Either mount in a subdirectory of a user-private directory, or use the Plan9-style per-user mount trees (experimental patches from Al Viro).

Quoted 1 line

Would it also work for windows/Macs?

If you put a Linux box in between to implement the SSL part :-)

It's pretty complicated, but then even a simple port-based firewall is rather complicated with NFS.

Now, if somebody were to fix the portmapper and RPC libraries to use sensible fixed ports, so we could sensibly firewall RPC services, they might be tempted to implement automatic SSL tunnelling while they're there...

-- Jamie