Re: Why don't we allow DNS names in pg_hba.conf? - Mailing list pgsql-hackers

From Mark Woodward
Subject Re: Why don't we allow DNS names in pg_hba.conf?
Date
Msg-id 16562.24.91.171.78.1139859518.squirrel@mail.mohawksoft.com
Whole thread Raw
In response to Re: Why don't we allow DNS names in pg_hba.conf?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Why don't we allow DNS names in pg_hba.conf?
List pgsql-hackers
> Mark Woodward wrote:
>
>>>If I am a road warrior I want to be able to connect, run my dynamic dns
>>>client, and go.
>>>
>>>
>>>
>>In your scenario of working as a road warrior, you are almost
>>certainly not going to be able to have a workable DNS host name unless
>> you
>>have a raw internet IP address. More than likely you will have an IP
>>address (known to your laptop) as a 192 or 10 address.
>>
>
>
> Nonsense. There is a dynamic DNS client that is quite smart enough to
> find out and use the gateway address. See:
> http://ddclient.sourceforge.net/
>
> I'm sure there are others, including some for Windows.
>

But then, there is another problem, if you don't have a real and true IP
address, if you are on anonymous 192 or 10 net (most likely the case),
then your dynamic DNS entry allows EVERYONE on your network the same
access.

I still say an SSH tunnel with port forwarding is more secure, besides you
can even compress the data stream.




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: psql & readline & win32
Next
From: Thomas Hallgren
Date:
Subject: Re: User Defined Types in Java