gmr April 2026

gmr@lists.osmocom.org

3 participants
4 discussions

Does the Galaxy Project offer any specific workflows for analyzing high-frequency financial datasets or integrating real-time market data streams? I am looking to apply computational biological models to large-scale brokerage data.
by maxh65183＠gmail.com 16 Apr '26

16 Apr '26

2 1

[PATCH 0/2] l1/a5: document A5/x family and hardware cipher block
by Dominik Bay 16 Apr '26

16 Apr '26

Two documentation-only patches expanding the Doxygen \defgroup block in the public A5 header. No algorithmic or behavioral change. Patch 1/2 describes the A5/x variant family used by GMR-1 (A5/0, A5/1, n=2..7 reserved), cites the Driessen et al. IEEE S&P 2012 paper as the public algorithm reference, and adds a HYPOTHESIS paragraph noting a conjectured equivalence between gmr1_a5_1() and ETSI TETRA's TEA1 cipher (EN 300 392-7). Motivation: if the equivalence holds, TEA1 reference implementations become an independent cross-validation source for gmr1_a5_1() output on matching (key, fn) inputs. The conjecture is explicitly labelled. Patch 2/2 records the register layout typically observed in deployed GMR-1 hardware cipher peripherals (16-bit MMIO window, four parameter words, selector, auxiliary word, and mode / control word with start / direction / algorithm-family-selector bit fields), plus the observation that the peripheral is usually a multi-cipher accelerator with additional algorithm-family slots beyond A5-GMR-1. The intent is to give capture-side analysis tool builders a concrete interface reference. Independent of the earlier "l1/a5: harden dispatcher default and expand docs" series on the list; both apply on top of master in either order. Dominik Bay (2): l1/a5: document A5/x variants and note TEA1 equivalence hypothesis l1/a5: document hardware cipher-block register layout and mode enum include/osmocom/gmr1/l1/a5.h | 44 ++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) -- 2.53.0

1 2

Auto-Responder to ML - Unsubscribe *@autoshack.com
by Dominik Bay 16 Apr '26

16 Apr '26

Hi, when sending E-Mails to this ML, no-reply(a)autoshack.com sends auto responder e-mails from a ticket system. Please remove them from the ML. Kind regards, Dominik

1 0

[PATCH 0/2] l1/a5: harden dispatcher default and expand docs
by Dominik Bay 16 Apr '26

16 Apr '26

While reading src/l1/a5.c I noticed that gmr1_a5(n, ...) silently falls through its switch default for n >= 2, leaving the caller's dl/ul buffers untouched. The only in-tree caller, at src/gmr1_rx.c:518 (TCH3 decode), passes n as a data-driven value (cd->tch3_state.ciph) into an uninitialized stack buffer ciph[208], which is then fed to gmr1_tch3_decode() as a keystream. For any n outside {0, 1} this means uninitialized stack memory becomes the "keystream" that the decoder XORs against the burst. Patch 1/2 is the defensive fix: zero the output buffers in the default case, matching the n=0 "no ciphering" path so the function's postcondition (buffers are fully written whenever non-NULL) holds for every legal value of n. No algorithmic change to gmr1_a5_1 or the n=0 / n=1 paths. Patch 2/2 is cosmetic: it clarifies the Doxygen block on gmr1_a5() to document the accepted range of n and the behavior per case, and it adds a \see reference on gmr1_a5_1() to the public algorithm description by Driessen, Hund, Willems, Paar, Holz ("Don't Trust Satellite Phones", IEEE S&P 2012) which underpins the existing implementation credit. Both patches apply cleanly on top of master (2b98363, "avoid memory leaks in gsmtap error paths"). Dominik Bay (2): l1/a5: zero output buffers for unsupported A5 variants l1/a5: expand dispatcher doc and cite upstream reference src/l1/a5.c | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) -- 2.50.1 (Apple Git-155)

1 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

gmr April 2026