Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEwgo-00AW65-4E for pgsql-general@arkaria.postgresql.org; Sat, 23 Nov 2024 20:25:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tEwgl-003kkU-O4 for pgsql-general@arkaria.postgresql.org; Sat, 23 Nov 2024 20:25:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEwgl-003kkC-CA for pgsql-general@lists.postgresql.org; Sat, 23 Nov 2024 20:25:07 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEwge-003Ubu-ID for pgsql-general@postgresql.org; Sat, 23 Nov 2024 20:25:06 +0000 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3e606cba08eso1588876b6e.0 for ; Sat, 23 Nov 2024 12:25:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732393498; x=1732998298; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=2SjGIjGFitABqXUJJhjF9VpI2A3Nkk9zAnxfvQpplxs=; b=QfkIihSGGo/HYUhKMu7gVqnSggWExFMvp7v09xsEDnP9mE9mor55TLHwnqLiFH8ozH +2HYw+mf/XBd0AxiAqXpoY0NU9uMVjwLWt/S05cN0cZtG085no+w6Q91hnozLTOOTwA0 EbyzHhNZEBg68wrU+9Q6PM2P/YyIcbCWSqhSO+Y7VmvjVcAnFmTVQb2tydwnFPjEOWBA 6m+FpTrVZJwx/P20Cm0Jcf5CBlUrWRTyp443tzmCNq6mnm+VoWXnsOWhcvGtvjIE4oo7 /zgmWhlsGnMPVRP902OARRKgWYBAJEALoW1LtvwsnGbXZDmYM8Y2F/Z/RbtxCPDLvaUv rCGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732393498; x=1732998298; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2SjGIjGFitABqXUJJhjF9VpI2A3Nkk9zAnxfvQpplxs=; b=bn8Wq9ch0uWRrD/pC56XXBZzB+h4jd79gdxWJAQT93s8Jf/Lg9Z39ge890Leh1ISO2 Okzv0AaJlIXSckzenVIJ/d3pWIE3rUPKdazWxYr5AmIBay/nBAeysoWhuYu5FQSeOl1f sGwDST5QEjTj1CxH1t7JT24wKOb/vLrvhwHyg4MkB8Ezr26pa9/nmIfKSPZZXTO+MNSg JJBb0Wcbp9K8Az3BTSoNAH2FBX8XX8h7pmy35MNZ5KjFtumpFu1v37VxtKQ4VyVXgqwK axIqwZBVyUAM5ItAqSahZLAgz14tzUz4fQBpDqptXwWap2HcEa3aaeCyvKU9zYSdQSub jqAw== X-Gm-Message-State: AOJu0YwOvs2zjY1SoVnTzGH1IQi8YZKIM4xLwsHWQWrI529oDRJ3beQz eGwd278FOMkO5cZAwHgamhqhY3IUjD2fwxU5vHurwLphjc0rofSLJhSSKz6CNzMlmkQMNvGrwd1 4kSHCAiASjSkPqvLTBzacMMT5MwUt7l4w X-Gm-Gg: ASbGncuavW3V6/K3c4P22zUh0vtyHqSZIHH3jOKEw6RMKsinReKFVX95mT807i2G3qC U7B17dVemdVQpVLh58ZjxtAVn0SMp2t5BKbyVjoi84kUEKALTzLWkHGDpHQNlkw== X-Google-Smtp-Source: AGHT+IF7HHVORaGl+Grjf7EAgl1F1v6mB/Ll1xS96aHWqr4vm3Qret3PD92EBmPC1URcvQJefYqi5ynMM92VEHjGywc= X-Received: by 2002:a05:6808:2e48:b0:3e8:1ed7:e6d9 with SMTP id 5614622812f47-3e9158776d7mr8220484b6e.23.1732393498233; Sat, 23 Nov 2024 12:24:58 -0800 (PST) MIME-Version: 1.0 References: <7b5846ac-c16e-48d3-b548-99a772a528c5@aklaver.com> <6c898e6499036ce70ac113b52df5c3ff06286a6a.camel@cybertec.at> In-Reply-To: From: Ron Johnson Date: Sat, 23 Nov 2024 15:24:47 -0500 Message-ID: Subject: Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10 To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000012e40e06279a4b3f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000012e40e06279a4b3f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 23, 2024 at 1:10=E2=80=AFPM Bruce Momjian wr= ote: [snip] > I have to admit, for this question, we just point people to: > > https://www.postgresql.org/support/versioning/ > > and say bounce the database server and install the binaries. What I > have never considered before, and I should have, is the complexity of > doing this for many remote servers. Can we improve our guidance for > these cases? > What guidance is needed? Even for us, where firewalls block our servers from https://download.postgresql.org, it's as simple as downloading the relevant RPM files *once* (and that done with a PowerShell script), then patching thusly: WinScp PG16.4_RHEL8 dir to each server, and on each server $ sudo -iu postgres pg_ctl stop -mfast -wt9999 -D /path/to/data $ sudo yum install PG16.4_RHEL8/*rpm $ sudo -iu postgres pg_ctl start -wt9999 -D /path/to/data Those three sudo commands take, at most, three minutes. -- Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000012e40e06279a4b3f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Nov 23, 2024 at 1:10=E2=80=AFPM B= ruce Momjian <bruce@momjian.us&g= t; wrote:
[snip]=C2=A0
I have to admit, for this question,= we just point people to:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.postgresql.org= /support/versioning/

and say bounce the database server and install the binaries.=C2=A0 What I have never considered before, and I should have, is the complexity of
doing this for many remote servers.=C2=A0 Can we improve our guidance for these cases?

What guidance is needed?= =C2=A0 Even for us, where firewalls block our servers from=C2=A0https://download.postgresql.org, it= 9;s as simple as downloading=C2=A0the relevant RPM files once=C2=A0(= and that done with a PowerShell script), then patching thusly:
WinScp PG16.4_RHEL8 dir to each server, and on each server
$ sudo -iu postgres pg_ctl stop -mfast -wt9999 -D /path/to/data
$ sudo yum install PG16.4_RHEL8/*rpm
$ sudo -iu postgr= es pg_ctl start -wt9999 -D /path/to/data

Tho= se three sudo commands take, at most, three minutes.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'= ;m still alive.
<Redacted> lobster!
--00000000000012e40e06279a4b3f--