On Fri, 5 Mar 2004, Michael Bushkov wrote:
Some time ago there was a discussion concerning in-process vs. IPC
nsswitch implementation. We agreed that we should develop an example of
IPC implementation and ask for a discussion. We are glad to present you
sample implementation of the IPC
On Fri, 5 Mar 2004, Michael Bushkov wrote:
Some time ago there was a discussion concerning in-process vs. IPC
nsswitch implementation. We agreed that we should develop an example of
IPC implementation and ask for a discussion. We are glad to present you
sample implementation of the IPC
On Fri, 5 Mar 2004, Jordan K Hubbard wrote:
Why not use a UNIX domain socket as the transport and then use
credential passing to pass the credentials lookupd should use to do the
lookup?
that was my thought.. the credential information passing must be useful
for something :-)
On Mar
Hello!
What do you mean exactly by saying not as functional?
Michael Bushkov
Software Engineer,
Rostov State University
On Fri, 5 Mar 2004, Jordan K Hubbard wrote:
Sounds similar to, but not as functional as, the lookupd in Mac OS X. :)
On Mar 5, 2004, at 12:45 AM, Michael Bushkov wrote:
[We need to pick a list and stop cross-posting. I pick [EMAIL PROTECTED]'.]
On Fri, Mar 05, 2004 at 10:41:33PM +0300, Michael Bushkov wrote:
The problem of using Darwin's lookupd was discussed some time ago in the
freebsd-arch mailing list. It seems to me that the way to port Darwin's
lookupd
Sounds similar to, but not as functional as, the lookupd in Mac OS X. :)
On Mar 5, 2004, at 12:45 AM, Michael Bushkov wrote:
We want you to look at this lookupd. It would be great for us to know
if
you like or not the way we made it. And we also want to know if this
project can be added to
Hello!
Some time ago there was a discussion concerning in-process vs. IPC
nsswitch implementation. We agreed that we should develop an example of
IPC implementation and ask for a discussion. We are glad to present you
sample implementation of the IPC nsswitch model.
http://rsu.ru/~bushman/lookupd
The Mac OS X lookupd does aggressive caching with cache invalidation
support, supports the notion of flushing the cache on certain events
(like when you reconfigure your network interfaces or switch
authentication plugins), and quite a few other things. No surprise,
really, given that it's
The Mac OS X lookupd does aggressive caching with cache invalidation
support, supports the notion of flushing the cache on certain events
(like when you reconfigure your network interfaces or switch
authentication plugins), and quite a few other things. No surprise,
really, given that it's been
On Fri, Mar 05, 2004 at 10:41:33PM +0300, Michael Bushkov wrote:
Our implementation of lookupd is a demonstration
of the approach for the FreeBSD-specific IPC implementation
of nsswitch. Its architecture is
flexible enough to implement all the features you have mentioned.
The version that
I understand this. There are some problems in making current nss-modules
compatible with our implementation. The main problem is process euid. When
you're
using current nss-modules they work as part of your program - and geteuid
functions
work correctly. But when lookupd is used, euid of the
Why not use a UNIX domain socket as the transport and then use
credential passing to pass the credentials lookupd should use to do the
lookup?
On Mar 5, 2004, at 1:27 PM, Michael Bushkov wrote:
When you're
using current nss-modules they work as part of your program - and
geteuid functions
12 matches
Mail list logo
