| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
| Date: | 2024-04-04 07:59:08 |
| Message-ID: | FE01778E-1F24-4C13-9BC0-F9759B0B867C@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 4 Apr 2024, at 01:50, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> That's a shame. But it sounds like the developer burden isn't so
> different from 1.1.1 to 3.x, so maybe it's not such a big deal from
> our point of view.
It isn't as of now since OpenSSL still supply the deprecated API's we use, but
there is no guarantee that they will do that for 5 more years.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2024-04-04 08:01:30 | Re: Introduce XID age and inactive timeout based replication slot invalidation |
| Previous Message | Daniel Gustafsson | 2024-04-04 07:56:22 | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |