> On 19 Jun 2023, at 21:00, Jeffrey Walton wrote:
> On Mon, Jun 19, 2023 at 11:39 AM Daniel Gustafsson wrote:
>>
>>> On 19 Jun 2023, at 17:13, Sebastien Flaesch
>>> wrote:
>>> OpenSSL V1 goes end of support soon (see
>>> https://www.openssl.org/policies/releasestrat.html) with replacement sh
On 6/19/23 12:15, Peter J. Holzer wrote:
On 2023-06-19 07:49:49 -0500, Ron wrote:
On 6/19/23 05:33, Peter J. Holzer wrote:
As Francisco already pointed out, this can't work with nginx either. The
client resolves the alias and the TCP packets only contain the IP
address, not the alias which was
On Mon, Jun 19, 2023 at 11:39 AM Daniel Gustafsson wrote:
>
> > On 19 Jun 2023, at 17:13, Sebastien Flaesch
> > wrote:
>
> > OpenSSL V1 goes end of support soon (see
> > https://www.openssl.org/policies/releasestrat.html) with replacement should
> > be OpenSSL V3.
> >
> > What is the strategy
On 2023-06-19 07:49:49 -0500, Ron wrote:
> On 6/19/23 05:33, Peter J. Holzer wrote:
> > As Francisco already pointed out, this can't work with nginx either. The
> > client resolves the alias and the TCP packets only contain the IP
> > address, not the alias which was used to get that address. So ng
> On 19 Jun 2023, at 17:13, Sebastien Flaesch wrote:
> OpenSSL V1 goes end of support soon (see
> https://www.openssl.org/policies/releasestrat.html) with replacement should
> be OpenSSL V3.
>
> What is the strategy with PostgreSQL (regarding sources, and binary packages)?
>
> On the various
Hello,
OpenSSL V1 goes end of support soon (see
https://www.openssl.org/policies/releasestrat.html) with replacement should be
OpenSSL V3.
What is the strategy with PostgreSQL (regarding sources, and binary packages)?
On the various supported platforms?
Seb
On 6/19/23 05:33, Peter J. Holzer wrote:
[snip]
You cant setup firewall rules basedon dns names. firewall rules are based on
ip adresses and dns resolution happens on rule creation.
I dont have an example for nginx. As I remember nginx resolves dns names
only for variables. So setup a variable w
19. Juni 2023 13:17, "Dominique Devienne" schrieb:
> On Mon, Jun 19, 2023 at 1:01 PM Thomas Markus wrote:
>
>> Am 19.06.23 um 12:33 schrieb Peter J. Holzer:
>>> As Francisco already pointed out, this can't work with nginx either.
>> anyway, fw or nginx cant look into tcp streams
> Traefik can p
On Mon, Jun 19, 2023 at 1:01 PM Thomas Markus
wrote:
> Am 19.06.23 um 12:33 schrieb Peter J. Holzer:
> > As Francisco already pointed out, this can't work with nginx either.
> anyway, fw or nginx cant look into tcp streams
>
Traefik can proxy PostgreSQL, I've read, so maybe that's something you
Hi,
Am 19.06.23 um 12:33 schrieb Peter J. Holzer:
As Francisco already pointed out, this can't work with nginx either. The
client resolves the alias and the TCP packets only contain the IP
address, not the alias which was used to get that address. So nginx
simply doesn't have that information an
On 2023-06-19 06:06:33 +0200, Thomas Markus wrote:
> Am 16.06.23 um 13:53 schrieb Brainmue:
> > With firewall you mean an additional software, right?
> > Because with iptables or netfilter I can't forward TCP packets based on the
> > DNS alias name. Or is
> > that possible?
> >
> > I have the sam
There haven't been any updates posted to
https://www.postgresql.org/message-id/20230509040203.z6mvijumv7wxcuib%40awork3.anarazel.de
so I just wanted to check if there is any update on the status of the
patch? Can we expect it in PostgreSQL 15.4? Thanks.
Hi community,
When I read the postgres's code,I want to achieve a simple scanner_init, so I
decided to write a function to analyse the config(Use yacc && lex)
That's means,I need to:
Raw config file -> Buffer -> Parse(Lex && Yacc) -> Complete
Now I write the lex && yacc rule file, but the thin
13 matches
Mail list logo
