Hi,
Thanks for your reply.
On 7/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > (1) Should we disable the overrding mechanism for SUID or SGID
> > processes ( e.g. substituting *__secure_getenv* for *getenv*).
>
> Good question actually. I've no idea :-(
>
> In theory, the user should n
Hi,
On Mon, Jul 23, 2007 at 09:05:14PM +0800, Wei Shen wrote:
> I made a try to implement a basic way of socket servers (pfinet and
> pflocal) overriding, as described below.
Great :-)
> (1) Should we disable the overrding mechanism for SUID or SGID
> processes ( e.g. substituting *__secure_ge
Hi,
I think the overriding mechanism should be disabled for suid processes, so
substituted *__secure_getenv* for *getenv*.
--- hurdsock.c 2007-07-25 11:24:46.0 +0800
+++ hurdsock2.c 2007-07-25 11:01:02.0 +0800
@@ -76,14 +76,40 @@
if (domain > max_domain || servers[domain] == M
Hi all,
I made a try to implement a basic way of socket servers (pfinet and
pflocal) overriding, as described below. Comments are solicited.
1) Add two new environment variables: SERVERS_SOCKET_LOCAL for the pf_local
socket server and SERVERS_SOCKET_INET for the pf_inet server. The value of
eac
At Wed, 20 Jun 2007 10:30:02 -0700,
Thomas Bushnell BSG wrote:
> On Wed, 2007-06-20 at 16:20 +0200, Neal H. Walfield wrote:
> > When we are just interested in
> > overriding a small parts of the environment and the rest represents a
> > reasonable default, this may be fine. Such an approach is, ho
On Wed, 2007-06-20 at 16:20 +0200, Neal H. Walfield wrote:
> What is a pseudo-chroot?
>
> I think what you are proposing is essentially filtering the global
> name space via some fancy translator.
Yes, just that.
> When we are just interested in
> overriding a small parts of the environment an
On 6/21/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
At Thu, 21 Jun 2007 00:09:45 +0800,
Wei Shen wrote:
> I still think there are ways to solve this problem. For example, the fs
> server can add an virtual root argument to the passive translator, and
the
> translator (which we trust) will la
At Thu, 21 Jun 2007 00:09:45 +0800,
Wei Shen wrote:
> I still think there are ways to solve this problem. For example, the fs
> server can add an virtual root argument to the passive translator, and the
> translator (which we trust) will later add this virtual root to any path
> argument provided b
On 6/20/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
At Wed, 20 Jun 2007 15:16:38 +0800,
Wei Shen wrote:
> I read the section. I am not quite clear about the storage of a file's
> translator attributes (I presume that a translator can not be associated
> with a file node via other ways than t
At Wed, 20 Jun 2007 15:16:38 +0800,
Wei Shen wrote:
> > A nice feature would be the option to use a file descriptor rather
> > than a symbolic name. This could take the form fd:X where X is some
> > number. This allows for selected access delegation (consider:
> > SERVERS_SOCKET_PFINET=fd:3 prog
At Tue, 19 Jun 2007 20:26:05 -0700,
Thomas Bushnell BSG wrote:
> > On 6/20/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
> >
> > > (1) Add a set of new environment variables, e.g.
> > PFINETSERVER for the pf_inet server and PFLOCALSERVER for the
> > pf_local server.
>
Hi,
On Tue, Jun 19, 2007 at 08:26:05PM -0700, Thomas Bushnell BSG wrote:
> What about a different strategy, one more "hurdish"? For example, run
> the program in a pseudo-chroot which overrides the behavior of nodes
> inside /servers?
I don't know how much you have read of my previous discussio
Hi,
On 6/20/07, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:
> On 6/20/07, Neal H. Walfield [EMAIL PROTECTED]> wrote:
We should have consistent naming between node names and
> environment variables. The default node names
> are /servers/socket/{2,pfinet}, etc. Perhaps have
> SERVERS_SO
On 6/20/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
A nice feature would be the option to use a file descriptor rather
than a symbolic name. This could take the form fd:X where X is some
number. This allows for selected access delegation (consider:
SERVERS_SOCKET_PFINET=fd:3 prog 3
I re
On Wed, 2007-06-20 at 11:11 +0800, Wei Shen wrote:
> Hi,
>
> On 6/20/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
>
> > (1) Add a set of new environment variables, e.g.
> PFINETSERVER for the pf_inet server and PFLOCALSERVER for the
> pf_local server.
>
>
Hi,
On 6/20/07, Neal H. Walfield <[EMAIL PROTECTED]> wrote:
> (1) Add a set of new environment variables, e.g. PFINETSERVER for
the pf_inet server and PFLOCALSERVER for the pf_local server.
We should have consistent naming between node names and environment
variables. The default node names
At Tue, 19 Jun 2007 23:20:27 +0800,
Wei Shen wrote:
> So I decide to narrow the range of the task to
> a small set of specific servers - socket servers - first as some of you
> suggest.
This is good.
> I list a straightforward approach below.
>
> (1) Add a set of new environment variables, e.g.
17 matches
Mail list logo
