rakeshkumar464 writes:
> In PG 9.6 or PG 10, is there a way to force only SSL based connections coming
> from pgadmin or dbeaver.
I think you could set that up with a custom pg_hba.conf entry or two.
Something like
hostnossl ... pgadmin ... reject
before the line that would normally accept the
In PG 9.6 or PG 10, is there a way to force only SSL based connections coming
from pgadmin or dbeaver.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On Wed, Jul 10, 2013 at 3:04 AM, Muhammad Bashir Al-Noimi
wrote:
> On Tue, Jul 9, 2013 at 11:21 PM, Jeff Janes wrote:
>> From your original email:
>> db.setHostName("localhost");
>>
>> So localhost is probably matching "127.0.0.1/32" or "::1/128", which
>> are explicitly allowed.
>
> I'm using th
On 07/10/2013 03:20 AM, Muhammad Bashir Al-Noimi wrote:
On Wed, Jul 10, 2013 at 12:16 PM, Magnus Hagander wrote:
requiressl=0 doesn't mean what you think it means, and that's one
reason it has been deprecated since at least 8.2.
requiressl=0 means "negotiate. use ssl if the server asks for it,
On Wed, Jul 10, 2013 at 12:16 PM, Magnus Hagander wrote:
> requiressl=0 doesn't mean what you think it means, and that's one
> reason it has been deprecated since at least 8.2.
>
> requiressl=0 means "negotiate. use ssl if the server asks for it, but
> accept not using ssl". So this will connect w
On Wed, Jul 10, 2013 at 12:04 PM, Muhammad Bashir Al-Noimi
wrote:
> On Tue, Jul 9, 2013 at 11:21 PM, Jeff Janes wrote:
>> From your original email:
>> db.setHostName("localhost");
>>
>> So localhost is probably matching "127.0.0.1/32" or "::1/128", which
>> are explicitly allowed.
>
> I'm using t
On Tue, Jul 9, 2013 at 11:21 PM, Jeff Janes wrote:
> From your original email:
> db.setHostName("localhost");
>
> So localhost is probably matching "127.0.0.1/32" or "::1/128", which
> are explicitly allowed.
I'm using this and still able to connect without SSL
db.setHostName("192.168.0.74")
On Tue, Jul 9, 2013 at 11:16 PM, Adrian Klaver wrote:
> Where are you connecting from? If you are connecting locally using
> sockets(local above) or host(line 3,4,5 above) then you are bypassing ssl.
I'm connecting from 192.168.0.74 and I commented line5 as following:
local all pos
On Tue, Jul 9, 2013 at 1:55 PM, Muhammad Bashir Al-Noimi
wrote:
> On 07/09/2013 07:54 PM, Jeff Janes wrote:
>>
>> On Tue, Jul 9, 2013 at 10:02 AM, Muhammad Bashir Al-Noimi
>> wrote:
>>>
>>> So may you please be more specific, what's wrong in my configurations?
>>>
>>> My pg_hba.conf content is:
>
On 07/09/2013 01:55 PM, Muhammad Bashir Al-Noimi wrote:
On 07/09/2013 07:54 PM, Jeff Janes wrote:
On Tue, Jul 9, 2013 at 10:02 AM, Muhammad Bashir Al-Noimi
wrote:
So may you please be more specific, what's wrong in my configurations?
My pg_hba.conf content is:
local all postgre
On Tue, Jul 9, 2013 at 1:55 PM, Muhammad Bashir Al-Noimi
wrote:
> On 07/09/2013 07:54 PM, Jeff Janes wrote:
>>
>> On Tue, Jul 9, 2013 at 10:02 AM, Muhammad Bashir Al-Noimi
>> wrote:
>>>
>>> So may you please be more specific, what's wrong in my configurations?
>>>
>>> My pg_hba.conf content is:
>
On 07/09/2013 07:54 PM, Jeff Janes wrote:
On Tue, Jul 9, 2013 at 10:02 AM, Muhammad Bashir Al-Noimi
wrote:
So may you please be more specific, what's wrong in my configurations?
My pg_hba.conf content is:
local all postgrespeer
local all
On Tue, Jul 9, 2013 at 10:02 AM, Muhammad Bashir Al-Noimi
wrote:
>
> So may you please be more specific, what's wrong in my configurations?
>
> My pg_hba.conf content is:
>
> local all postgrespeer
> local all all
On Tue, Jul 9, 2013 at 2:46 AM, Adrian Klaver wrote:
> Also remember in pg_hba.conf first match wins, so if there is a more
> permissive entry before your restrictive one, the permissive one will take
> precedence.
Thanks for reply but you just quted some line from the documentation
which I alre
On 07/08/2013 05:32 PM, Muhammad Bashir Al-Noimi wrote:
Howdy,
I want to prevent any Postgresql database connection other than SSL but
it didn't work and my client can connect without SSL!
* How can fix this issue?
P.S. To force SSL connection I made the following steps:
On server side
Howdy,
I want to prevent any Postgresql database connection other than SSL but
it didn't work and my client can connect without SSL!
* How can fix this issue?
P.S. To force SSL connection I made the following steps:
On server side (ubuntu 12.10 x64 - Postgresql 9.1)
1) Created server.k
16 matches
Mail list logo
