user & password

tinyproxy server operators may want to not run an "open" proxy for the whole world, but rather limit usage to a smaller goup of users. They then put the line

 BasicAuth username password

into the control file /usr/local/etc/tinyproxy/tinyproxy.conf

While a browser like firefox and the IRC app KDE Konversation can smoothly handle this (fill in the fields at runtime (firefox) or in settings (Konversation), other apps may not be able to handle it. For example, the IRC client Srain won't be able to work (missing settings fields), if in KDE system settings a proxy is defined. KDE system settings for proxy do not have a password field, so any app using it will fail with an Auth error. Unless KDE is ameliorated accordingly, users without a compatible app will be shut out from using a proxy server with the HTTP BasicAuth mechanism. Without password, Srain will work nicely over e.g. the KDE globally defined proxy.

Since the password prompt in firefox sounds rather generic, many users will of course be confused as to which of the thousands of passwords one has to deal with these days is required now - while some password-managers, so-called, even exacerbate the issue further.