public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jered Floyd <jered@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/trafficserver] trafficserver-9.2.14-1: Update to upstream 9.2.3
Date: Wed, 15 Jul 2026 17:21:19 GMT	[thread overview]
Message-ID: <178413607959.1.18234572274033538108.rpms-trafficserver-d1a41acd919d@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/trafficserver
            Branch : trafficserver-9.2.14-1
            Commit : d1a41acd919d61017c4eda0982cf29dc0a656180
            Author : Jered Floyd <jered@redhat.com>
            Date   : 2023-10-11T15:55:29+00:00
            Stats  : +8/-4 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/trafficserver/c/d1a41acd919d61017c4eda0982cf29dc0a656180?branch=trafficserver-9.2.14-1

            Log:
            Update to upstream 9.2.3

Resolves CVE-2023-44487, CVE-2023-41752, CVE-2023-39456

---
diff --git a/sources b/sources
index aca09d1..f2faa3d 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (trafficserver-9.2.2.tar.bz2) = 1d00a3b9207648a16e0043f714c931bb5f30978ca329e0897d8d08b8d70d38a52bbe37ffe89884e98d5e7db09ad2762a90c3dc9654c70c0a979690a1fc342b72
-SHA512 (trafficserver-9.2.2.tar.bz2.asc) = 392fdde3d59cd1a595943a4fe965199ed158649e70944e3f5e537d4672568b44bd38c7b90789ce5ddeb213133de7c0d270ab1481b973343448a18406d91980ff
+SHA512 (trafficserver-9.2.3.tar.bz2) = acb511873a051c2cdfddccabf420be79cba01ae241470738658a89bcf636074bf41cda62552e01f41b9549295f817c566a1696aec057509a8c93f3b22ae9e90e
+SHA512 (trafficserver-9.2.3.tar.bz2.asc) = 9d71d79ecd2a1feb0a652992ec201d479462b2ab68a66875e536597ee9dcaf8b1de807d44ab0627f6bf94301e3ac2c7fbd500660ac8746e31f07ff861fa51985

diff --git a/trafficserver.spec b/trafficserver.spec
index 29e4a8c..2365631 100644
--- a/trafficserver.spec
+++ b/trafficserver.spec
@@ -3,8 +3,8 @@
 %global selinuxtype targeted
 
 Name:           trafficserver
-Version:        9.2.2
-Release:        2%{?dist}
+Version:        9.2.3
+Release:        1%{?dist}
 Summary:        Fast, scalable and extensible HTTP/1.1 and HTTP/2 caching proxy server
 
 License:        ASL 2.0
@@ -307,6 +307,10 @@ fi
 
 
 %changelog
+* Wed Oct 11 2023 Jered Floyd <jered@redhat.com> 9.2.3-1
+- Update to upstream 9.2.3
+- Resolves CVE-2023-44487, CVE-2023-41752, CVE-2023-39456
+
 * Wed Oct 4 2023 Jered Floyd <jered@redhat.com> 9.2.2-2
 - Use OpenSSL 1.1.x from EPEL on RHEL 7 to fix Chrome 117+ bugs
 

                 reply	other threads:[~2026-07-15 17:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178413607959.1.18234572274033538108.rpms-trafficserver-d1a41acd919d@fedoraproject.org \
    --to=jered@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox