Semantics of !~ operator

[Alan DeKok]

On Apr 28, 2015, at 1:18 PM, Gerald Vogt <vogt at spamcop.net> wrote:
> I thought it has been established it is a bug.

  No.  If, as you claim, it doesn't work, then it's a bug.  The argument here was you haven't shown your claims.

> I have attached the full output of a test run of a eap-peap
> authentication from a new CentOS 7 freeradius-3.0.4-6.el7.x86_64
> installation.
> 
> As you can see outer.request:Called-Station-SSID and
> outer.Called-Station-SSID don't return anything but
> "%{outer.request:Called-Station-SSID}" does.

  Because your tests are wrong.

>  authorize {
> + 	update request {
> + 		Called-Station-SSID := outer.request:Called-Station-SSID

  See "man unlang".  This is documented.

  This configuration is the same as:

	update request {
		Called-Station-SSID := "outer.request:Called-Station-SSID"
	}

  Because you're not doing:

	update request {
		Called-Station-SSID := &outer.request:Called-Station-SSID
	}

  As is documented by "man unlang".

  So all of this back and forth could have been simplified by (a) describing exactly what you're doing, and not "it doesn't get updated", and (b) providing the debug output.

  Alan DeKok.