'--auth-user-pass FILE' and '--auth-nocache' problem
|Reported by:||ye_olde_iron||Owned by:|
|Severity:||Not set (if unsure, select this one)||Keywords:||auth-user-pass auth-nocache|
If you specify that username/password information should be read from a file ('--auth-user-pass FILE'), but that this information should NOT be cached ('--auth-nocache') then initially all works well, with the username and password being read from the file. However, when the renegotiation timeout occurs on the client ('--reneg-sec nnn'), an attempt is made to read the username and password FROM STDIN instead of from the specified file!
[The log gives the error "ERROR: could not read Auth username from stdin"]
If you have specified that the information should be read from a file, then the nocache should cause the information to be re-read from the file, not stdin.
(In this case I wish the file to contain a password that changes over time, so I do not want it to be cached).
The same problem may to have been reported under "Ticket #60 : --auth-user-pass <file> does not work after TLS soft reset disconnect", but '--auth-nocache' is not mentioned.
Change History (7)
comment:3 Changed 14 months ago by dazo
- Component changed from Generic / unclassified to Configuration
- Keywords stdin removed
- Priority changed from major to minor