Re: Apple-approved way to listen on well known ports?
Re: Apple-approved way to listen on well known ports?
- Subject: Re: Apple-approved way to listen on well known ports?
- From: Doug Hill <email@hidden>
- Date: Thu, 25 Sep 2003 17:20:45 -0400
Thanks for the information Meeroh. I had looked at that sample and it makes
sense for quick one-time things like creating folders in special places,
changing configuration settings, etc. but not for things like listening on a
socket.
Are you saying that I could/should have a separate chunk code in a tool that
runs with privs. that listens on the socket that somehow passes accepted
calls to the non-priv. application? I'm still using OpenTransport here too
so that complicates this as well.
[One step at a time - I just got this thing running on OS X. Next is to move
to BSD sockets for the network I/O....]
I have a suspicion that I am just screwed for the time being until I break
up my application into two pieces - an engine that runs headless with privs
and the U/I. It's currently factored that way internally but it's still one
binary].
-d
>
From: Miro Jurisic <email@hidden>
>
Date: Thu, 25 Sep 2003 15:54:44 -0400
>
To: Doug Hill <email@hidden>, <email@hidden>
>
Subject: Re: Apple-approved way to listen on well known ports?
>
>
> What are my options to get my product listening on port 21 w/o being logged
>
> in as root? What is the Apple-approved [tm] way?
>
>
Your options are the same as for any other privileged operation,
>
which means that you should look at MoreAuthSample
>
<
http://developer.apple.com/samplecode/Sample_Code/Security/MoreAuthSample.htm>
>
>
>
hth
>
>
meeroh
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.