From: | Nuno Zimas <nzimas(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: user can't access own database after creation |
Date: | 2015-12-02 21:31:29 |
Message-ID: | BA07E4DA-025C-4DB2-8C8F-659668AFF4BF@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> On 2 Dec 2015, at 21:24, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>
> On 12/2/2015 1:00 PM, Nuno Zimas wrote:
>>>
>>> what does the pg_hba.conf file look like on the ubuntu server ?
>>
>>
>> You can see the file contents here:
>> http://pastebin.com/vYQMsP27 <http://pastebin.com/vYQMsP27>
>
> these three lines,
> host all all 78.47.104.116/32 trust
> host all all 62.210.69.197/32 trust
> host all all 10.10.10.99/32 trust
>
>
> they state that anyone on those 3 hosts can connect as any postgres user including the superuser 'postgres' without any authentication required at all
>
That’s pretty much the intended behaviour at this point.
As far as SSL goes, it really doesn’t make any difference.
I’ve tried adding ?ssl=true and ?ssl=false to the jdbc URL with no success.
> .
> Also, I see nothing in there about SSL.
>
> --
> john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2015-12-02 21:36:57 | Re: user can't access own database after creation |
Previous Message | Dave Cramer | 2015-12-02 21:25:59 | Re: user can't access own database after creation |