site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com http://developer.apple.com/SampleCode/BetterAuthorizationSample/index.html -josh On Apr 1, 2009, at 11:26 AM, Thomas Tempelmann wrote: By default, processes can't listen on ports < 1024 unless they're running as root, if I got it right. Is there some way to authorize an app to open a specific port for a user account? The particular app I'm writing is talking to a device in the LAN via UDP only, and that device is unfortunately using a hard-coded port number below 1024 for its reply. Since the app I'm writing shall be written quickly and only serves to configure the device once in a while, writing a two-tiered app with a deamon is kind of overkill, and debugging gets more difficult that way, too. That's why I'm looking for such an alternative solution. -- Thomas Tempelmann, http://www.tempel.org/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macnetworkprog/jgraessley%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists.... You'll want to write a helper tool that will pass back the opened and bound socket to your main process. I believe there's a good sample out there...BettherAuthorizationSample. This email sent to jgraessley@apple.com This email sent to site_archiver@lists.apple.com