public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred <fred@arkansaswebs.com>
To: joe.mathewson@btinternet.com,
	Joseph Mathewson <joe@mathewson.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [OFFTOPIC] Secure network fileserving Linux <-> Linux
Date: Wed, 5 Sep 2001 14:30:57 -0500	[thread overview]
Message-ID: <200109051931.f85JVUf11156@srvr201.castmark.com> (raw)
In-Reply-To: <200109051913.f85JD2K01304@ambassador.mathewson.int>
In-Reply-To: <200109051913.f85JD2K01304@ambassador.mathewson.int>

One possible solution might be samba, but I'd be lying if I asserted anything 
about its security, I do know that it can be configured to operate entirely 
over SSL though.

Fred

__________________________________________________ 
On Wednesday 05 September 2001 02:13 pm, Joseph Mathewson wrote:
> Sorry to ask another annoying question so quickly after my SCSI problems,
> but
>
> Does anyone know of/use a secure network filesharing system on a Linux
> network?  We currently have a room of about 10 machines, mostly Linux
> clients (some MacOS X, soon to come Sun and HP-UX boxes) and servers (all
> running Linux).
>
> For some time now, we've been using NFS for filesharing /home and have been
> extremely concerned about security.  All the clients in theory run the same
> uids/gids, thanks to LDAP, but that doesn't stop someone plugging in an
> unauthorized machine and merrily destroying everyone's home directories.
>
> Apparently some work was done to Kerberize various bits of NFS, and Sun
> have a secure(r) implementation in Solaris.
>
> Does anyone know of a free (preferably easy :) way of secure Linux <->
> Linux filesharing?  Apologies if that seems like a flame, maybe I've missed
> the obvious solution.  (Preferably a solution that doesn't involve editing
> /etc/exports to only allow connections from specified IPs, because if
> someone was going to go to the length of destroying our data, they could
> fake that.  Similarly, MAC addresses.)
>
> Joe.
>
> +-------------------------------------------------+
>
> | Joseph Mathewson <joe@mathewson.co.uk>          |
>
> +-------------------------------------------------+
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-09-05 19:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 19:13 [OFFTOPIC] Secure network fileserving Linux <-> Linux Joseph Mathewson
2001-09-05 19:30 ` Fred [this message]
2001-09-05 20:17 ` Frank Schneider
2001-09-05 22:12 ` Jesse Pollard
2001-09-05 22:54   ` Dax Kelson
2001-09-06  1:17   ` John Jasen
2001-09-06  1:54     ` Kain
2001-09-06  3:37     ` Bernd Eckenfels
2001-09-06 12:39       ` Jesse Pollard
2001-09-06  9:20   ` Dominik Kubla
  -- strict thread matches above, loose matches on Subject: below --
2001-09-06 12:28 Jesse Pollard
2001-09-06 16:41 ` Mike Fedyk
2001-09-06 12:46 Jesse Pollard
2001-09-07  1:53 ` Jamie Lokier
2001-09-07 15:34 Jesse Pollard
2001-09-07 15:58 ` Jamie Lokier
     [not found] <linux.kernel.20010907025336.D7329@kushida.degree2.com>
2001-09-07 15:41 ` Aaron Denney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200109051931.f85JVUf11156@srvr201.castmark.com \
    --to=fred@arkansaswebs.com \
    --cc=joe.mathewson@btinternet.com \
    --cc=joe@mathewson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox