: zones-discuss@opensolaris.org
Date: Fri, 04 May 2007 07:04:14 EDT
Subject: Re: [zones-discuss] pidentd
That's a real pain as that prevent us to use zones as hosting
servers for
users :
- we are a school and we just want to identify connections.
Starting with mail
sending.
Zones would br
James Carlson wrote:
[EMAIL PROTECTED] writes:
I would like to have users on a zone, but we use pidentd to control some
network connections.
It seems that pidentd doesn not work on zones as it can't open kmem.
Is there any way to make it work ?
Essentially, no.
Opening /dev/kmem in the zone
Le 4 mai 07 à 19:34, [EMAIL PROTECTED] a écrit :
Oh. I though that pidentd was supposed to resolve UIDs locally.
That's one of the features of the protocol; it provides "here's who
*I* think the user is" information back to the requester.
Of course, that's why I thought IDENT was a fairly
[EMAIL PROTECTED] writes:
> > Oh. I though that pidentd was supposed to resolve UIDs locally.
> > That's one of the features of the protocol; it provides "here's who
> > *I* think the user is" information back to the requester.
>
> Of course, that's why I thought IDENT was a fairly bogus mechanis
>> Oh. I though that pidentd was supposed to resolve UIDs locally.
>> That's one of the features of the protocol; it provides "here's who
>> *I* think the user is" information back to the requester.
>
>Of course, that's why I thought IDENT was a fairly bogus mechanism
>since you're asking the rem
Oh. I though that pidentd was supposed to resolve UIDs locally.
That's one of the features of the protocol; it provides "here's who
*I* think the user is" information back to the requester.
Of course, that's why I thought IDENT was a fairly bogus mechanism
since you're asking the remote system
>[EMAIL PROTECTED] writes:
>> >I'd sort of like to know how it does that reliably ... does it fork
>> >and enter the zone?
>>
>> It does not resolve names local to the local zones; but it can easily
>> find all the appropriate uids and processes. No different from traditional
>> Solaris with mul
[EMAIL PROTECTED] writes:
> >I'd sort of like to know how it does that reliably ... does it fork
> >and enter the zone?
>
> It does not resolve names local to the local zones; but it can easily
> find all the appropriate uids and processes. No different from traditional
> Solaris with multiple in
>Not sure about the socket option (should still work ... ?), but IP
>Instances did nuke the symbols that pidentd was reading out of the
>kernel, so that utility is now broken.
I also have no idea about that option and how it is affected by the
IP instances project. I am assuming it is now "per-
[EMAIL PROTECTED] writes:
> I've done some work on pidentd prior to the new IP instances code using the
> ability to intercept calls for all zones in the global zone with the
> SO_ALLZONES socket option (which may not work anymore after the IP
> instances putback)
Nifty!
Not sure about the socke
>
>That's a real pain as that prevent us to use zones as hosting servers for
>users :
>- we are a school and we just want to identify connections. Starting with mail
>sending.
>Zones would break our identification model.
>It would be real nice if some solution could be found.
I've done some
James Carlson <[EMAIL PROTECTED]>
> Cc: zones-discuss@opensolaris.org
> Date: Fri, 04 May 2007 07:04:14 EDT
> Subject: Re: [zones-discuss] pidentd
>[EMAIL PROTECTED] writes:
>> I would like to have users on a zone, but we use pidentd to control some
>> network
[EMAIL PROTECTED] writes:
> I would like to have users on a zone, but we use pidentd to control some
> network connections.
> It seems that pidentd doesn not work on zones as it can't open kmem.
>
> Is there any way to make it work ?
Essentially, no.
Opening /dev/kmem in the zone wouldn't be a
Hello,
I would like to have users on a zone, but we use pidentd to control some
network connections.
It seems that pidentd doesn not work on zones as it can't open kmem.
Is there any way to make it work ?
f.g.
___
zones-discuss mailing list
zones-d
14 matches
Mail list logo
