BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Subject: [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- From: kentborg at borg.org (Kent Borg)
- Date: Sat, 31 Jan 2015 13:53:54 -0500
- In-reply-to: <54CCF4A4.6040703@borg.org>
- References: <54CCF4A4.6040703@borg.org>
All I am doing is connecting the server with the client code, on the same machine. I don't care what the password is, only that the two agree, on any given box. How about this: Give every boot, of every box running the code, its own unique password. At every boot, create a new password in a boot script (read a UUID out of /proc/sys/kernel/random/uuid). Give it to Postgres and put it in a config file with reasonable ownership restrictions appropriate to be read by the client code. Seems pretty simple. -kb P.S. Also turn off all but loopback access to the server process.
- Follow-Ups:
- [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- References:
- [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Prev by Date: [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Next by Date: [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Previous by thread: [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Next by thread: [Discuss] Passwords in Source Code?? Or, How to secure interprocess communications?
- Index(es):