From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: smtpmail authentication again
Date: Fri, 13 Jan 2012 00:47:38 +0100 [thread overview]
Message-ID: <qkvcogjxet.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87ty429x4u.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Wed, 11 Jan 2012 06:45:23 +0100 Richard Riley <rileyrg@gmail.com> wrote:
>
> RR> I pulled nognus from git but this function is not there. there is
> RR> an -or-password funtion
>
> RR> (auth-source-user-or-password MODE HOST PORT &optional USERNAME
> RR> CREATE-MISSING)
>
> RR> but that takes different args. Can you confirm
> RR> which repo this new function is in and sorry if Im wasting your time.
>
> It's in the Gnut Git repo. You did something wrong. Here's the
> function, anyhow:
>
>
>
> #+begin_src lisp
> (defun auth-source-user-and-password (host &optional user)
> (let* ((auth-info (car
> (if user
> (auth-source-search
> :host host
> :user "yourusername"
> :max 1
> :require '(:user :secret)
> :create nil)
> (auth-source-search
> :host host
> :max 1
> :require '(:user :secret)
> :create nil))))
> (user (plist-get auth-info :user))
> (password (plist-get auth-info :secret)))
> (when (functionp password)
> (setq password (funcall password)))
> (list user password auth-info)))
>
> #+end_src
>
>
>
> The old `auth-source-user-or-password' is obsolete. I named this one
> slightly differently to liven things up a bit (think "who's on first?"
> "user-or-password?" "no, user-AND-password" "AND is on second?" etc. :)
>
> Ted
>
>
>
>
Problem isolated but not properly fixed : have some sort of nasty race
issue/ side affect from loading nognus using el-get. Not relying on
el-get to set the path and manually setting the path to my nognus
installation BEFORE allowing el-get to do its stuff solved the
issue. Cheers for the function, I think you see the value or use more
clearly now - certainly my hidden password files are now a thing of the
path and everything is in the authinfo gpg file.
next prev parent reply other threads:[~2012-01-12 23:47 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 [this message]
2012-01-11 22:59 ` Eric S Fraga
2012-01-10 16:26 ` Richard Riley
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=qkvcogjxet.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).