> -----Original Message-----
> From: Dan Seguin [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 25, 1999 5:26 PM
> To: Brian F. Feldman
> Cc: FreeBSD Hackers
> Subject: Re: Connect and so on..
>
> As I said earlier in this post, I need to open a connection to the
> outside
> (presumably) from the KERNEL. The reason for this is that the calling
> process has no knowledge of the connection, and the connection,
> communication, response from other end, and closing of connection must
> be
> one atomic, discreet event that will not get interrupted. I assumed
> that
> this would have to be done from the KERNEL but maybe I'm wrong here.
> If I
> could use an external (userland) daemon with shared space, the KERNEL
> could write to it and the daemon would do the rest, but how do I keep
> ALL
> other processes (except system processes) from running? The latter
> didn't
> seem feasible to me.
[ML] From your original mail it is not obvious why this has to
happen from the kernel, but I assume that you need to have the UID of
the caller and the safest way would be to get it from the kernel. If
that is the case, you could take a look at the way nfssvc(?) works going
back into user space for authentication. There are, however, other
authentication schemes which can be implemented keeping everything in
user space--take a look at the secure RPC implementation (Bill Paul was
working on that some time ago, IIRC).
If you can tell a bit more about the problem grounds, perhaps an
easier solution can be found.
/Marino
> Thanks!
>
>
> Dan Seguin
>
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
