From: Jean Louis <bugs@gnu.support>
To: Robert <rchar@protonmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: sql and auth-source
Date: Fri, 27 Nov 2020 10:10:35 +0300 [thread overview]
Message-ID: <X8Cma/x6KWErTixW@protected.rcdrun.com> (raw)
In-Reply-To: <xSYeibwpEkzAcYo24zzCntGjkfxCqWq3JDEKzIlsRQhNXMzmYUGtNTCpO5wblnSR2-FLsv0mFjfou3Ua48iyXIAC3wlKtzVrG9CE2_VHuOU=@protonmail.com>
* Robert <rchar@protonmail.com> [2020-11-27 09:52]:
> The ideal solution will include:
> - no passwords in init.el
I do keep passwords in init.el as it is personal file.
I do not keep passwords in init.el on remote servers. Then I would
prefer entering them. If it is multi user server then what if
administrator or some other user with access rights or backdoor is
listening on tty to read what I am typing?
Change permissions:
-rw------- 1 50K Nov 25 22:04 init.el
Use better umask limits and also change permission on /home/user
directory to be user readable only if user is "protected" then
/home/protected would be:
drwx------ 244 92K Nov 27 09:22 protected
Database password is not the only thing that is private, there are
other more important or more private things in the user's directory.
Unless init.el is not published for demonstrations it can be used to
store passwords.
> - I connect to the database using sql-connect or sql-postgres
> - (usually PostgreSQL) when connecting, I choose an alias to the
> - database
> - I am only asked to enter a password in order to decrypt the
> - authinfo wallet file
Interesting, as I may use those methods for program I am developing
when it comes to be used by public.
For Unix domain sockets I use trust method in pg_hba.conf
# "local" is for Unix domain socket connections only
local all all trust
For remote databases SSL security with usernames and passwords is
necessary.
prev parent reply other threads:[~2020-11-27 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 12:46 sql and auth-source Robert via Users list for the GNU Emacs text editor
2020-11-26 19:49 ` Filipp Gunbin
2020-11-27 1:58 ` Jean Louis
2020-11-27 6:52 ` Robert
2020-11-27 7:10 ` Jean Louis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X8Cma/x6KWErTixW@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=rchar@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).