Magnus Hagander wrote: > Well, the question is not about sensitive information, is it? It's about > password disclosure due to spoofing. Which would affect *all* services > that accept passwords over any kind of local connections - both unix > sockets and TCP localhost. > > I'm just saying that pretty much everybody has to be affected by this. > And you can't claim it's very common to use SSL to secure localhost > connections. Maybe it should be, but I hardly ever see it...
Yep. I think the big issue is most people think unix domain sockets and localhost are secure, but they are not if the server is down, unless SSL is used or the socket file is in a privileged directory. > The best way to avoid it is of course not to give untrusted users access > to launch arbitrary processes on your server. Something about that > should perhaps be added to that new docs section? Yep, doing that now. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
