Attr-26.135.22.100?

[Alan DeKok]

On Jul 21, 2017, at 12:23 PM, Stefan Paetow <Stefan.Paetow at jisc.ac.uk> wrote:
> 3.0.14:
> 
> (15)         update {
> (15)           &outer.session-state::Attr-26.135.22.100 += &reply:Attr-26.135.22.100[*] -> 0x02001101a406686f7374a50b6c6f63616c686f7374

  Huh?

  If you have EAP-Channel-Binding-Message in the config files, that's what should get printed out here.

  The "Attr-26..." format is really only used when sending and receiving packets.  Having it here is... weird.

> The value of EAP-Channel-Binding-Message and 'Attr-26.135.22.100' are identical. In 3.0.14, the session-state copy unlang strips out EAP-Message and Message-Authenticator (which is correct, because the unlang in inner-tunnel explicitly strips it).
> 
> So. What's happened to 'EAP-Channel-Binding-Message' and why is it either mangled or being misinterpreted by radiusd as attribute 26.135.22.100?

  Hmm... the issue would seem to be when the attribute is *created*.   

  I've pushed a fix.

  Alan DeKok.