public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] shairport-sync: Update to version 5.6.2
Date: Mon, 26 Oct 2026 16:59:41 +0100	[thread overview]
Message-ID: <20261026155942.2122609-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261026155942.2122609-1-adolf.belka@ipfire.org>

- Update from version 5.6.1 to 5.6.2
- No change in rootfile
- Changelog
5.6.2
Security-Related Bug Fix
    Malformed DACP TLV (Tag-Length-Value) tokens could generate out-of-bounds (OOB)
	reads in Shairport Sync. The bug fix was to improve checking of DACP TLV
	payloads. Thanks to memoriaru for their report.
Enhancement
    This enhancement changes how frames of audio are referenced, so that long sessions
	(greater than about 12.5 hours) do not go silent due to signed 32-bit integer
	sign overflow.
    Background: AirPlay associates a 32-bit RTP timestamp, a timing reference number,
	with every audio frame. After playing 2^31 - 1 frames of buffered audio --
	about 12.5 hours at 48,000 frames per second -- the total number of frames
	played exceeds 2^31 -1 and goes negative due to sign overflow. Timing
	calculations fail, causing frames to be dropped and the player to go silent.
    The enhancement develops 64-bit timestamps from RTP timestamps of the frames as
	they are processed in preparation for playing. Many thanks to Martin Man for
	their patient troubleshooting, PR and initial report.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/shairport-sync | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/shairport-sync b/lfs/shairport-sync
index 04a468754..af68ab0b4 100644
--- a/lfs/shairport-sync
+++ b/lfs/shairport-sync
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = An AirPlay audio player
 
-VER        = 5.6.1
+VER        = 5.6.2
 
 THISAPP    = shairport-sync-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = shairport-sync
-PAK_VER    = 21
+PAK_VER    = 22
 
 DEPS       = alsa avahi ffmpeg libdaemon libplist nqptp soxr
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 7761d774d99b0d0c3adcd10a439aabbf365151676b2e831d60130328566daade09b00055736e6e65e8174f7c150fca5fd7cd6d1c39291d605cc323c20419b0a6
+$(DL_FILE)_BLAKE2 = 6017dd15818ae3f561d8f2a6572bf9368f970d29ec394e7e3041726474e8fb66a9a421aac36159ee8287c03ddb06a185688b913602dbef969eb3906f7654aaa5
 
 install : $(TARGET)
 
-- 
2.56.0



      parent reply	other threads:[~2026-10-26 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 15:59 [PATCH] core206: Ship openldap Adolf Belka
2026-10-26 15:59 ` [PATCH] core206: Ship patch Adolf Belka
2026-10-26 15:59 ` [PATCH] openldap: Update to version 2.7.2 Adolf Belka
2026-10-26 15:59 ` [PATCH] patch: Update to version 2.8.1 Adolf Belka
2026-10-26 15:59 ` Adolf Belka [this message]

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=20261026155942.2122609-5-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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