Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: smtpmail authentication again
Date: Tue, 10 Jan 2012 17:26:21 +0100	[thread overview]
Message-ID: <xm8vlfcymq.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87wr8zei8c.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Tue, 10 Jan 2012 03:34:43 +0100 Richard Riley <rileyrg@gmail.com> wrote: 
>
> RR> Thanks ted. I'll try to use this then to store my erc credentials in gpg
> RR> file. Strikes me as the srt of thing that would greatly benefit from
> RR> little wrappers for the commone usage as simple as
>
> RR> getUserForHost("host");
> RR> getPassForHost("host");
>
> (CamelCase?  Horror!)
>
> That would hide the search API, especially that you can get multiple
> answers and connection parameters for a query.  End users are not

It doesnt hide anything. The serch "api" is still there. Personally I
wouldnt have a snowballs chance in hell of understanding the elisp you
posted above ;)

> supposed to use auth-source directly, and packages will almost always
> want the complex search.

I think thats a bit of a jump. I'm asking as I have a lot of passwords
for various things in a hidden, chmod'ed plain text file. And Im certain
many others do too. In a gpg file they are safe. If I lose my netbook...

>
> Also getPass or whatever it's called will expose the password, whereas
> now it's wrapped in a lexical-let so you can't see it easily until
> you're ready to use it.

If one uses the function one takes the chance. I suspect the great
majority of us dont worryy too mcuh about certain passwords for things
not overly critical being in the memory of our local machines at
home. And anyways, it depends on how we code the the stuff that uses
this getPass/getUser wrapper : lexical hiding can be applied there too.

>
> I understand the benefit of simplicity, though.  Hmmm.  Besides ERC,
> where would you use the simpler functions?

Absolutely everywhere I needed to access a uid & password that I dont want
stored in plain text : "machine" here doubles for "account". Off the top
of my head:

erc, twitter, mysql, mpd server, bitlbee, identica.

Im sure there are plenty more.





      parent reply	other threads:[~2012-01-10 16:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 16:06 Richard Riley
2012-01-03 22:25 ` Lars Magne Ingebrigtsen
2012-01-05  8:03   ` Kostas Zorbadelos
2012-01-05 19:00     ` Richard Riley
2012-01-05  9:29   ` Leo
2012-01-05 19:02     ` Richard Riley
2012-01-07  2:07   ` Ted Zlatanov
2012-01-07  2:16     ` Ted Zlatanov
2012-01-07  2:28       ` Lars Magne Ingebrigtsen
2012-01-07  2:43         ` Ted Zlatanov
2012-01-26 18:58           ` Lars Ingebrigtsen
2012-01-26 22:44             ` Ted Zlatanov
2012-01-27 17:59               ` Lars Ingebrigtsen
2012-01-27 19:17                 ` Ted Zlatanov
2012-01-27 18:25                   ` Lars Ingebrigtsen
2012-01-28 11:30                     ` Steinar Bang
2012-02-01 18:48                     ` Ted Zlatanov
2012-02-01 18:53                       ` Johann 'Myrkraverk' Oskarsson
2012-02-01 19:02                         ` Ted Zlatanov
2012-02-02  7:44                           ` Richard Riley
2012-01-07  5:33         ` Richard Riley
2012-01-07 13:10           ` Ted Zlatanov
2012-01-07 14:45             ` Richard Riley
2012-01-08 19:36               ` Ted Zlatanov
2012-01-10  2:34                 ` Richard Riley
2012-01-10 14:37                   ` Ted Zlatanov
2012-01-10 14:47                     ` Ted Zlatanov
2012-01-11  5:45                       ` Richard Riley
2012-01-11 13:39                         ` Ted Zlatanov
2012-01-12 23:47                           ` Richard Riley
2012-01-11 22:59                       ` Eric S Fraga
2012-01-10 16:26                     ` Richard Riley [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

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

  git send-email \
    --in-reply-to=xm8vlfcymq.fsf@news.eternal-september.org \
    --to=rileyrg@gmail.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).