Re: Listening on the port
Re: Listening on the port
- Subject: Re: Listening on the port
- From: Igor garnov <email@hidden>
- Date: Fri, 7 May 2004 21:53:14 +0400
On Friday, May 7, 2004, at 16:39 Europe/Moscow, Quinn wrote:
At 2:45 +0400 4/5/04, Igor garnov wrote:
My Carbon CFM application using Open Transport creates an endpoint
for UDP protocol and then binds it to port 137 (to listen to
broadcasts in network neighborhood).
I presume you're running the Carbon application on Mac OS X. If so,
this is going to be tricky. On Mac OS X, TCP and UDP ports below 1024
are privileged; you can't bind to them unless you're running as root
(that is, your EUID is 0). There are techniques to solve this problem
(for example, the descriptor passing technique supported by
MoreSecurity; see MoreAuthSample for details) but they're difficult to
use from a CFM application and totally incompatible with Open
Transport.
Yes, this is in UNIX way. But my CFM app checks if it's launched in Mac
OS X or 9. If it feels it's running on 9, it tries to bind to port 137
to listen to broadcasts.
So, on Mac OS 9 and Classic mode on Mac OS X, am I entitled to bind to
port 137?
Thanks for your replies - they're always very precise. Honestly, after
I learnt that most Apple folks are forced to put all their efforts in
preparing 'Tiger' I did not expect quick answers.
Regards,
Igor
_______________________________________________
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.