From: Frank Cusack <fcusack@fcusack.com>
To: Scott Leerssen <scott@leerssen.com>
Cc: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net
Subject: Re: nfs root directory security
Date: Wed, 18 Jun 2003 14:16:15 -0700 [thread overview]
Message-ID: <20030618141615.A22386@google.com> (raw)
In-Reply-To: <1055946469.16259.81.camel@sleerssen.racemi.com>; from scott@leerssen.com on Wed, Jun 18, 2003 at 10:27:50AM -0400
On Wed, Jun 18, 2003 at 10:27:50AM -0400, Scott Leerssen wrote:
> I agree with everything you say here, and in a controlled and fairly
> unchanging environment with clients you trust, exporting to specific
> clients is a perfectly acceptable solution.
The only solution.
What you need to do is automate, not obfuscate.
/fc
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-06-18 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 22:28 nfs root directory security Scott Leerssen
2003-06-17 23:36 ` Neil Brown
2003-06-18 2:54 ` Scott Leerssen
2003-06-18 3:47 ` Neil Brown
2003-06-18 3:38 ` Scott Leerssen
2003-06-18 9:30 ` Bogdan Costescu
2003-06-18 12:36 ` Scott Leerssen
2003-06-18 13:55 ` Bogdan Costescu
2003-06-18 14:27 ` Scott Leerssen
2003-06-18 21:16 ` Frank Cusack [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 15:27 Heflin, Roger A.
2003-06-18 15:59 ` Scott Leerssen
2003-06-18 15:34 Heflin, Roger A.
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=20030618141615.A22386@google.com \
--to=fcusack@fcusack.com \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=scott@leerssen.com \
/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