[freeradius-3.0.8] Error on elaborate detail file with CR chars

[Geaaru]

Some more informations:

case 1) If User-Name has only one CR then job send empty string on call
database

case 2) If User-Name has more of one CR (carridge-return char) job is
blocked and detail file is not processed.

G.

On Tue, 2016-10-11 at 16:09 +0200, Geaaru wrote:
> Hi,
> 
> > i'm currently use release 3.0.8 of freeradius and I'm not sure if
this issue is already been resolved.
> 
> > I currently configured my freeradius server with a buffered-sql
server.
> 
> > On my environment sometimes I receive a strange Username that write
wrong message on detail file like this:
> 
> Mon Oct 10 22:15:11 2016
>         Packet-Type = Accounting-Request
>         NAS-IP-Address = 192.168.12.10
>         NAS-Identifier = 'GGSN-XX1'
>         Called-Station-Id = 'apn.freeradius.org'
>         Framed-Protocol = GPRS-PDP-Context
>         Service-Type = Framed-User
>         NAS-Port-Type = Virtual
>         Calling-Station-Id = '22222222002222'
>         Acct-Status-Type = Start
>         Framed-IP-Address = 172.26.242.65
>         Acct-Session-Id = 'D9C8B3C3B9353FB4'
>         User-Name = '
> 
> 
> '
>         Acct-Session-Time = 0
>         Acct-Authentic = RADIUS
>         Acct-Delay-Time = 0
>         Acct-Multi-Session-Id = '57FBF6CF0000013C222013200038833F'
>         Proxy-State = 0x3136
>         Proxy-State = 0x3837
>         Timestamp = 1476130511
> 
> > > As you can see Username string is written wrong and when file is
processed from detail job to load record on database I have two
different problem:
> 
> > > case 1) accounting is written correctly but Username is not resolve
and an empty string is sent. I resolve temporary this with a fake
string to identify this problem.
> 
> > > case 2) currently I see that thread for parse detail file and call
database is blocked. I see just record before this error packet
"Donestamp" field and then nothing.
> 
> > Is already open this issue or is already resolve with a fresh version
?
> 
> > > I'm not sure that this is a false issue. I see that from RFC 2865
permit all UTF-8 chars so it seems a valid scenario this where I
receive CRCR chars on User-Name field.
> 
> Thanks in advance.
> Geaaru
> 
>