So yeah, um, this is not okay. It is not discoverable and could easily leak sensitive information. Auth credentials even, seriously? Also Chrome does this too. And it is preserved across `mv` to another filesystem.https://twitter.com/gynvael/status/1077671412847046657 …
Credentials in a URI is one (perhaps the only?) standard way for supplying the contents of that header field that is cross-application.
-
-
Microsoft disabled it in IE for security reasons, so it wasn’t all that cross-application. A standard rule of web development is never to put anything confidential in the URL because URLs leak all over the place. Browser history, for example.
-
The *point* of putting confidential information in the URL is to make it portable. So you can paste the URL into another app and it'll work. Yes, it's a tradeoff. But I don't expect the browser to deliberately leak them as non-discoverable xattrs on files.
- Show replies
New conversation -
-
-
Actually, working with basic auth recently I found that most browsers have already dropped support for URL creds. Too easy to exploit. Wget needs to fix, but one possible fix is dropping URL creds entirely.
-
Chrome and Firefox support it, >77% market share right there. Who are these "most browsers"?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
$ getfattr -d -m - test
user.xdg.origin.url="https://user:passwd@gynvael.coldwind.pl/"