Okay this bug has suffered neglect on my part - sorry about that. : ( I've just rebuilt from source with the change applied to the latest 1.4.8 release and I can confirm that this does fix the problem I described and builds successfully. The user's password may risk being exposed in several places, but thats really the nature of these types of URLs and I think that the risk of exposing the password is less important than the inconvenience of an - from the users point of view - unrelated error message about not being able to find a suitable decoder. I suspect that this is a fairly rare requirement anyway, but it works for me at least.
To fix the bug, I have changed the KURL::prettyURL() call to a regular KURL::url() call on line 1201 in the new release. I think that this is more appropriate here regardless of the bug, since prettyURL is for displaying the URL and in most cases any changes would probably make it unusable in practice, anyway. Sorry about dropping the ball on this one. -- Incorrect storage of authenticated stream URLS https://bugs.launchpad.net/bugs/133340 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
