Re: OmniWeb acting as a server and listening for connections?
"Greg Leffler" <[email protected]> Wed, 7 Nov 2007 16:41:42 -0500
| Newsgroups | gmane.comp.web.omniweb |
|---|---|
| Message-ID | <[email protected]> |
Did you attempt to connect to an FTP site? Active FTP requires that the client listen for an incoming connection from the server. On 11/7/07, Tim Pritlove <[email protected]> wrote: > > Hi, > > I have been running OmniWeb on Leopard now for a couple of days. I > have my system running with the new application firewall blocking all > incoming connections with the exception of a few server programs I am > running (like Nicecast). > > Today, the system presented me with the question if I want to allow > incoming connections for OmniWeb. > > My understanding of the new application firewall is that it is based > on TrustedBSD's Mandatory Access Control and can prevent programs from > receiving network traffic completely without the need to block > individual ports. It can simply shut down incoming network access. > Furthermore, Leopard signs the application's code at the time of > confirmation to prevent modified copies to inherit access rights given > to another version. > > So my impression is that OmniWeb has indeed requested a network socket > to listen on. This is something I would not expect from a web browser. > So the question is: why is this happening? > > I think this is highly suspicious. Unfortunately the firewall does not > come up with any further explanation why it thinks the program wants > to accept incoming connections. So I am mostly in the dark here. Can > anybody shed some light on this? > > Greetings > Tim > _______________________________________________ > OmniWeb-l mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/omniweb-l >