Search Postgresql Archives

Re: Heartbleed Impact

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Albe Laurenz <laurenz.albe@xxxxxxxxxx>
Subject: Re: Heartbleed Impact
From: Dev Kumkar <devdas.kumkar@xxxxxxxxx>
Date: Wed, 16 Apr 2014 17:30:11 +0530
Cc: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <A737B7A37273E048B164557ADEF4A58B17CF0DEC@ntex2010i.host.magwien.gv.at>

On Wed, Apr 16, 2014 at 3:18 PM, Albe Laurenz <laurenz.albe@xxxxxxxxxx> wrote:

Unless somebody changes the setting to ssl=on, there should be no problem.

Yours,
Laurenz Albe

Thanks also please help to understand - does changing this postgresql.conf setting enough to be vulnerable here?

Regards...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Heartbleed Impact
  - From: Albe Laurenz

References:
- Heartbleed Impact
  - From: Dev Kumkar
- Re: Heartbleed Impact
  - From: Albe Laurenz

Prev by Date: Re: Heartbleed Impact
Next by Date: Grants where grantor = grantee?
Previous by thread: Re: Heartbleed Impact
Next by thread: Re: Heartbleed Impact
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux