[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/main] Clarify behavior on bad address length in NETINFO
commit b962a3003808fb940101f5f49c5b3ead2eeaf3e5
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Mon Aug 16 11:17:23 2021 -0400
Clarify behavior on bad address length in NETINFO
---
tor-spec.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tor-spec.txt b/tor-spec.txt
index 7e76562..dce264f 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -887,7 +887,8 @@ see tor-design.pdf.
[06] IPv6.
ALEN MUST be 4 when ATYPE is 0x04 (IPv4) and 16 when ATYPE is 0x06
- (IPv6).
+ (IPv6). If the ALEN value is wrong for the given ATYPE value, then
+ the provided address should be ignored.
The timestamp is a big-endian unsigned integer number of seconds
since the Unix epoch. Implementations MUST ignore unexpected bytes
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits