Mon Nov 8 14:12:44 PST 2010
- Previous message: [Slony1-bugs] [Bug 165] Hiding Password in logs
- Next message: [Slony1-bugs] [Bug 165] Hiding Password in logs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=165 Steve Singer <ssinger at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX | Status|RESOLVED |REOPENED --- Comment #5 from Steve Singer <ssinger at ca.afilias.info> 2010-11-08 14:12:44 PST --- The talk of .pgpass SHOULD have been moved from best practices to the "Security Considerations" section but was missed. I will move that. One feature of slony that people might be be taking advantage of is that you can deploy slon to a new machine and and tell it to connect to one node (the local node) from that it will get the paths+credentials for connecting to all the remote nodes. I can see situations where this would be desirable, but I can also see why in other situations .pgpass would be better than storing the passwords in the conninfo in sl_path I think this issue is still worth fixing. The 8.3 incompatibility is more incidental to Jose's patch and it could be reworked. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 165] Hiding Password in logs
- Next message: [Slony1-bugs] [Bug 165] Hiding Password in logs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list