Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.
Date: Sun, 19 Sep 2010 21:30:01 -0500	[thread overview]
Message-ID: <87fwx56tau.fsf@lifelogs.com> (raw)
In-Reply-To: <m3y6azi884.fsf@quimbies.gnus.org>

On Sat, 18 Sep 2010 13:47:39 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I was trying to discourage people from putting their password in an
>> unencrypted file.  So I'm sort of OK with making the unencrypted file
>> the second choice, but I'd like to at least warn the user.  WDYT?

LMI> If it could be done unobtrusively...  I don't really like software that
LMI> tells me that what I'm doing is stupid, even though it's right.  :-)

An unobtrusive warning?  That's pretty useless, better not to bother the
user.

On Sat, 18 Sep 2010 14:50:38 +0200 Sebastian Krause <sebastian@realpath.org> wrote: 

SK> Personally, I don't like to enter my long GnuPG password every time
SK> I start up Gnus.

It's entered once per Emacs session.  If that's too much use the Secrets
API (KWallet or Gnome Seahorse).

SK> It's safe enough anyway because I use full disk encryption with
SK> LUKS.

That's a completely different type of security, though it's useful too.
Your passwords are in the clear to anything running in your environment,
right?

SK> Or maybe those passwords are not too important because they're only
SK> for a simple Usenet server. So, warning users shouldn't be too noisy
SK> because there might be good reasons of using the unencrypted file.

It's a balancing act (and a familiar problem since I've been a sysadmin
for a long time).  I'll just be quiet about this as long as it's the
second default choice.

On Sat, 18 Sep 2010 17:40:23 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> And if there was a nice, painless road towards storing the passwords in
LMI> ~/.authinfo.gpg, that would be nice.  That is, if the user is queried
LMI> for user name/password, then auth-source.el should store it encrypted,
LMI> and not in the plain ~/.authinfo file.

auth-source.el has nothing to do with it.  All the work is done by
EPA/EPG and I'm intentionally keeping auth-source.el agnostic of
encryption issues beyond mentioning the .gpg extension.

On Sat, 18 Sep 2010 23:29:01 +0200 Sebastian Krause <sebastian@realpath.org> wrote: 

SK> However, I just saw that even in case of an encrypted
SK> ~/.authinfo.gpg it's pretty easy to find out my IMAP password if
SK> Gnus is still running: It's simply shown in the *imap log*
SK> buffer. It's probably because imap.gmail.com uses cleartext login
SK> through SSL. Is there any way to not print out the password, but
SK> some kind of placeholder instead?

If the attacker has any access to Emacs, he can sniff the encryption
passphrase from the auth-source.el cache.  Sorry but ELisp (in Emacs or
XEmacs) is just not a secure environment; auth-source.el tries to at
least make it less necessary to store your passwords in an unencrypted
location.  Its main purpose is to provide a single place for all ELisp
code to get authentication tokens.

Ted




  reply	other threads:[~2010-09-20  2:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OwjUu-0007Om-00@quimby.gnus.org>
2010-09-18  6:19 ` Ted Zlatanov
2010-09-18 11:47   ` Lars Magne Ingebrigtsen
2010-09-20  2:30     ` Ted Zlatanov [this message]
2010-09-20  8:14       ` Lars Magne Ingebrigtsen
2010-09-20 15:03         ` Ted Zlatanov
2010-09-25 12:47           ` Gijs Hillenius
2010-09-25 13:56             ` Lars Magne Ingebrigtsen
2010-09-25 15:12             ` Ted Zlatanov
     [not found]               ` <87mxr46gv9.fsf@hillenius.net>
2010-09-26 12:27                 ` Ted Zlatanov
2010-09-26 12:38                   ` tls.el I added '--insecure' (Was :Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.) Gijs Hillenius
2010-09-26 20:53                     ` tls.el I added '--insecure' Ted Zlatanov
2010-09-20 10:47       ` [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users Sebastian Krause
2010-09-20 14:59         ` Ted Zlatanov
2010-09-20 18:40           ` Michael Albinus
2010-09-20 14:27       ` Richard Riley
2010-09-20 15:01         ` Ted Zlatanov
2010-09-20 15:29           ` Richard Riley
2010-09-18 12:50   ` Sebastian Krause
2010-09-18 15:40     ` Lars Magne Ingebrigtsen
2010-09-18 21:29       ` Sebastian Krause
2010-09-18 21:31         ` Lars Magne Ingebrigtsen
2010-09-20 11:03   ` Robert Pluim
2010-09-20 14:10     ` Richard Riley
2010-09-20 14:59       ` Robert Pluim
2010-09-20 15:26     ` Ted Zlatanov
2010-09-20 15:43       ` Tibor Simko
2010-09-20 15:53       ` Robert Pluim
2010-09-21 16:19       ` Lars Magne Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fwx56tau.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).