Bug#141507: sntop: 32 char hostname limit is wrong/evil

2025-01-21 Thread Petter Reinholdtsen
[Mark Eichin] > For a time-boxed effort, I believe 256 is better than 128 (RFC-1035 > defines the limit in terms of wire-encoding of the DNS message rather > than the user-visible values (section 3.1, "To simplify > implementations") - there's also a 63 byte limit for "labels" but that's > just a s

Bug#141507: sntop: 32 char hostname limit is wrong/evil

2025-01-20 Thread Mark Eichin
For a time-boxed effort, I believe 256 is better than 128 (RFC-1035 defines the limit in terms of wire-encoding of the DNS message rather than the user-visible values (section 3.1, "To simplify implementations") - there's also a 63 byte limit for "labels" but that's just a single name-part and does

Bug#141507: sntop: 32 char hostname limit is wrong/evil

2025-01-19 Thread Petter Reinholdtsen
[Mark W. Eichin 2002-08-06] > I list a hostname of > krb5-verify-init-creds-opt-set-ap-req-nofail.krbtest.com > in my .sntoprc. strace shows that sntop silently trucates this, and > fails, running I do not know the code, but had a look and suspect the limit is set using the IN_BUF define. Here