On Jul 21, 2017, at 11:16 AM, Stefan Paetow <Stefan.Paetow@jisc.ac.uk> wrote:
After an upgrade to FR 3.0.15 on a test system, I suddenly have an unknown attribute 'Attr-26.135.22.100' in the debug output. It appears that EAP-Channel-Binding-Message is no longer recognised as such in the debug output? When I downgrade to 3.0.14 the issue persists, but when I drop back to 3.0.10 it recovers itself to say 'EAP-Channel-Binding-Message' in the debug output... Can someone else reproduce this with 3.0.15?
I know this doesn't affect operations, but... it's irksome?
What is the raw data from that attribute? Perhaps it actually is malformed... EAP-Channel-Binding is a Ukerna attribute, of number 135. So if it *is* malformed, it should come across as: Attr-26.25622.135 = 0x.... I don't see any issue here... Alan DeKok.