Re: Allowing incoming connections.
Re: Allowing incoming connections.
- Subject: Re: Allowing incoming connections.
- From: Ken Thomases <email@hidden>
- Date: Wed, 24 Mar 2010 03:15:04 -0500
On Mar 24, 2010, at 2:50 AM, John C. Randolph wrote:
> So, I've got this app that connects to RTSP streams, and I'd rather not nag the user every time it's launched with that "Do you wan the application to accept incoming network connections?" dialog box. Anyway to have the user authorize it once and have that authorization stick, or is this a matter of security policy?
It should, in normal use, stick. This interacts with the application firewall feature of the OS. That, in turn, is based on apps being digitally signed. If an app isn't signed by the developer/producer/vendor, then the system computes an ad hoc signature for it. That signature is valid unless/until the app is modified internally in some way.
Obviously, while the app is under development, it will be changing all the time. So, you're constantly invalidating its signature.
You can work around this by signing your app properly as part of building it, but I'm not sure it's common to sign development builds. You can also just ignore the inconvenient prompt during development.
Or are you getting reports from users that this prompt is happening every time?
I'm a bit confused why an app that "connects to RTSP streams" would need to be listening for and accepting incoming connections, though. Is your app an RTSP server or client? Your description sounds like it's a client. In that case, it should be making outgoing connections, not accepting incoming connections.
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden