Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Tom Lane
Peter Eisentraut writes: > On 10/25/14 2:52 PM, Tom Lane wrote: >> And a bit of experimentation later: it seems that on Yosemite (and >> probably earlier OS X versions), "localhost" maps to all three of these >> addresses: >> 127.0.0.1 >> ::1 >> fe80:1::1 >> Binding to 127.0.0.1 does not trigger t

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Peter Eisentraut
On 10/25/14 2:52 PM, Tom Lane wrote: > And a bit of experimentation later: it seems that on Yosemite (and > probably earlier OS X versions), "localhost" maps to all three of these > addresses: > 127.0.0.1 > ::1 > fe80:1::1 > Binding to 127.0.0.1 does not trigger the firewall popup

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Tom Lane
I wrote: > Peter Eisentraut writes: >> Have we dug deep enough into the firewall configuration to evaluate >> other options? Can we, for example, exclude a port range? > Not that I've been able to detect. Any simple way to do that would > presumably open up exactly the security hole Apple is tr

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Tom Lane
Peter Eisentraut writes: > Given that this doesn't affect "make check" anymore, I'm unsure about > this patch. There is a lot of magic in the configure change. I don't > know what to pass as the configure option argument, so can't really > evaluate that. I'd like to see an explanation for what

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Peter Eisentraut
On 10/24/14 9:39 AM, Tom Lane wrote: > Peter, Dave: maybe you have tweaked things to keep listen_addresses > empty and rely only on Unix-socket connections? I can confirm that I do get the popup when starting an installed postmaster with the default settings. Given that this doesn't affect "make

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-25 Thread Peter Eisentraut
On 10/24/14 10:27 AM, Tom Lane wrote: > Some clients (eg JDBC) don't support Unix-socket connections AFAIK, so > this seems like a rather restricted solution. While this is a valid point, they're actually working on fixing that. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-24 Thread Tom Lane
Michael Paquier writes: > On Fri, Oct 24, 2014 at 3:39 PM, Tom Lane wrote: >> Peter, Dave: maybe you have tweaked things to keep listen_addresses >> empty and rely only on Unix-socket connections? > Should be so. The target of this feature is development on OSX, right? > And most of the time dev

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-24 Thread Michael Paquier
On Fri, Oct 24, 2014 at 3:39 PM, Tom Lane wrote: > Peter, Dave: maybe you have tweaked things to keep listen_addresses > empty and rely only on Unix-socket connections? Should be so. The target of this feature is development on OSX, right? And most of the time development would be done only on the

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-24 Thread Tom Lane
Michael Paquier writes: > On Fri, Oct 24, 2014 at 8:26 AM, Dave Page wrote: >> On Fri, Oct 24, 2014 at 7:18 AM, Peter Eisentraut wrote: >>> On 10/21/14 1:16 PM, Tom Lane wrote: If you do any Postgres development on OS X, you've probably gotten seriously annoyed by the way that, every s

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-24 Thread Michael Paquier
On Fri, Oct 24, 2014 at 8:26 AM, Dave Page wrote: > On Fri, Oct 24, 2014 at 7:18 AM, Peter Eisentraut wrote: > > On 10/21/14 1:16 PM, Tom Lane wrote: > >> If you do any Postgres development on OS X, you've probably gotten > >> seriously annoyed by the way that, every single time you reinstall th

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-23 Thread Dave Page
On Fri, Oct 24, 2014 at 7:18 AM, Peter Eisentraut wrote: > On 10/21/14 1:16 PM, Tom Lane wrote: >> If you do any Postgres development on OS X, you've probably gotten >> seriously annoyed by the way that, every single time you reinstall the >> postmaster executable, you get a dialog box asking whet

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-23 Thread Peter Eisentraut
On 10/21/14 1:16 PM, Tom Lane wrote: > If you do any Postgres development on OS X, you've probably gotten > seriously annoyed by the way that, every single time you reinstall the > postmaster executable, you get a dialog box asking whether you'd like > to allow it to accept incoming network connect

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-22 Thread Tom Lane
Robert Haas writes: > On Tue, Oct 21, 2014 at 1:16 PM, Tom Lane wrote: >> If you do any Postgres development on OS X, you've probably gotten >> seriously annoyed by the way that, every single time you reinstall the >> postmaster executable, you get a dialog box asking whether you'd like >> to all

Re: [HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-22 Thread Robert Haas
On Tue, Oct 21, 2014 at 1:16 PM, Tom Lane wrote: > If you do any Postgres development on OS X, you've probably gotten > seriously annoyed by the way that, every single time you reinstall the > postmaster executable, you get a dialog box asking whether you'd like > to allow it to accept incoming ne

[HACKERS] Getting rid of "accept incoming network connections" prompts on OS X

2014-10-21 Thread Tom Lane
If you do any Postgres development on OS X, you've probably gotten seriously annoyed by the way that, every single time you reinstall the postmaster executable, you get a dialog box asking whether you'd like to allow it to accept incoming network connections. (At least, you do unless you disable t