Cover the guarded address writers, and cut what the code already says

2026-09-21 08:08:42 +02:00
parent c1e0407942
commit f870b7530f
8 changed files with 68 additions and 45 deletions
@@ -10,7 +10,8 @@
  `source_addr` of `Kaffeé` previously reached the application as `Kaffei`, because the codec wrote
  the octet and then masked bit 7 reading it back; `destination_addr`, `system_id`, `message_id`,
  `service_type` and the C-Octet String TLVs were affected the same way. A character past `U+00FF`
-  in one of those fields is now refused, where it used to go out as its low octet.
+  in one of those fields is now refused, where it used to go out as its low octet — which for `一`,
+  `　` and most emoji is `0x00`, ending the field there.
 - A `U+0000` inside a C-Octet String — `source_addr`, `message_id`, `system_id` and the rest — is
  refused. The peer reads such a field to its first NULL, so one sent inside the value shifted every
  mandatory field behind it while `command_length` still counted the whole string. An Octet String