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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting rid of "accept incoming network connections" prompts on OS X
Date: 2014-10-26 02:02:05
Message-ID: 544C561D.4040204@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. Binding
> to ::1 doesn't, either. But binding to fe80:1::1 does. So the
> easy fix, for a default installation, is to keep the postmaster
> from binding to that last address.
>
> I'm not sufficiently up on my IPv6 to be sure exactly what that third
> address does. Perhaps it is a bug in the firewall logic that it
> considers that address external?

I think that's exactly it. I have filed a bug with Apple about it.

For the time begin, I think it's a reasonable workaround to comment out
the line in /etc/hosts.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-10-26 02:40:12 Re: Getting rid of "accept incoming network connections" prompts on OS X
Previous Message Haribabu Kommi 2014-10-26 01:51:12 Re: Possible problem with shm_mq spin lock