| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fix by Adam Osuchowski.
|
|
|
|
| |
Closes RADSECPROXY-40.
|
|
|
|
|
|
|
|
|
|
|
| |
code.
clientwr() should treat the dynamic lookup as a failure and will not
be any happier to know that the exact error was that it didn't resolv.
The script can do whatever logging is wanted.
That said, this commit also makes the scripts exit with 10 in order to
signal failure.
|
|
|
|
| |
`-e' to /bin/echo isn't portable. The BSD's lacks it for instance.
|
|
|
|
| |
Spotted by Paul Dekkers. Closes RADSECPROXY-39.
|
|
|
|
| |
This triggers a bug in radsecproxy. Don't use it for now.
|
|
|
|
|
|
|
|
|
| |
This way a script can signal "not found".
The naptr-eduroam.sh and radsec-dynsrv.sh scripts are changed to
behave like this.
Closes RADSECPROXY-22.
|
|
|
|
| |
Also, change `test' to '['.
|
|
|
|
|
|
|
|
|
|
| |
Not all systems have bash (esp. not in /bin) and some people argue
that /bin/sh should be less unsafe due to less code, lower complexity
and being around for longer time.
Fixes:
- /bin/sh builtin echo doesn't have `-e' -- use /bin/echo
- /bin/sh builtin test ([) doesn't understand `==' -- use `='
|
| |
|
|
|