Re: Authenticated communication between KEXT and a userland client
Re: Authenticated communication between KEXT and a userland client
- Subject: Re: Authenticated communication between KEXT and a userland client
- From: <email@hidden>
- Date: Thu, 20 Aug 2009 03:13:14 -0700
- Acceptlanguage: en, en-US
- Thread-topic: Authenticated communication between KEXT and a userland client
It is possible to restrict socket access only to user land client running in root’s context. Is that what you are looking for ?
-Sudarshan
On 19/08/09 8:42 PM, "Michael Smith" <email@hidden> wrote:
On Aug 19, 2009, at 6:10 AM, Andreas Guðmundsson wrote:
Hi, I have a kext and a userland client communicating with sockets.
Now I'd like to be sure that I'm communicating with the correct client
so I want the kext to authenticate the client. How can this be done
properly?
Andreas,
Before it's possible to give you a useful answer, you need to explain what you mean by the "correct client".
Do you want to prevent an accidental wrong client, or are you trying to ensure that a deliberate wrong client won't be able to use your interface?
= Mike
--
Ars longa, vita brevis, occasio praeceps, experimentum periculosum, iudicium difficile -- Hippocrates
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden