radsecproxy

radsecproxy@lists.nordu.net

72 discussions

F-Ticks VISINST default
by Zenon Mousmoulas 28 Jun '16

28 Jun '16

Hi, I noticed this in fticks.c, line 109: if (options->fticks_reporting == RSP_FTICKS_REPORTING_FULL) { if (client->conf->fticks_visinst != NULL ) { snprintf((char *) visinst, sizeof(visinst), "VISINST=%s#", client->conf->fticks_visinst); } else { snprintf((char *) visinst, sizeof(visinst), "VISINST=%s#", client->conf->name); } } If a client has no fticksVISINST set, this means radsecproxy will log the client name instead. However that may not be a valid operator-name (1<domain>) and it probably won't convey anything meaningful: if you don't set fticksVISINST you probably expect requests from different operators to be proxied through that client. If the Operator-Name attribute value won't be used in the absence of fticksVISINST, then I guess it would be better to have an empty VISINST (not sure if that would be valid). However it is not even possible to force an empty value through configuration, as the tokenizer in getconfigline() reports that "fticksVISINST needs a non-empty value". Any ideas? Please advise. Thanks, Zenon Mousmoulas

2 2

Testing redirect to new list
by Linus Nordberg 19 May '16

19 May '16

Hi, This is a test message for verifying the redirect from radsecproxy(a)uninett.no to radsecproxy(a)lists.nordu.net.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

radsecproxy