This is an automated email from the ASF dual-hosted git repository. sjanc pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/mynewt-nimble.git
commit 7616be771600e02e67c88094e5d8479f042c501f Author: Szymon Janc <[email protected]> AuthorDate: Tue Oct 6 19:25:42 2026 +0200 THREAT_MODEL: Refer to mcumgr in apache-mynewt-core mcumgr was moved into apache-mynewt-core and is modelled in its THREAT_MODEL.md. Assisted-by: Claude:claude-opus-5-5 --- THREAT_MODEL.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/THREAT_MODEL.md b/THREAT_MODEL.md index 49f9cc841..fa3da667f 100644 --- a/THREAT_MODEL.md +++ b/THREAT_MODEL.md @@ -39,9 +39,9 @@ - **Drafted:** 2026-06-13, ASF Security team (v0 draft from public artefacts). - **Companion repos this round:** `apache/mynewt-core` (the RTOS NimBLE runs on, and which provides the management transport that may sit *on - top of* a BLE L2CAP channel) and `apache/mynewt-mcumgr` (uses a BLE - connection as one SMP transport โ so NimBLE is the carrier, mcumgr the - payload). + top of* a BLE L2CAP channel), including mcumgr (`mgmt/mcumgr/`, formerly + `apache/mynewt-mcumgr`; uses a BLE connection as one SMP transport โ so + NimBLE is the carrier, mcumgr the payload). - **What triggers a revision:** a new Bluetooth spec feature (new PDU types, a new pairing method, a new LL control procedure); a change to the Security Manager's supported association models; a @@ -98,7 +98,7 @@ host). *(documented: `nimble/{host,controller,transport}` layout; ยง14 Q1)* in `apache/mynewt-core` / the porting layer. 5. **mcumgr / newtmgr management payloads** that *ride on top of* a BLE L2CAP channel โ NimBLE is the carrier; the SMP server is modelled in - `apache/mynewt-mcumgr` and `apache/mynewt-core`'s `mgmt/`. + `apache/mynewt-core`'s `THREAT_MODEL.md`. 6. **Physical / invasive and side-channel attacks** on the device. 7. **Supply-chain / build hygiene.**
