Re: [PATCH] Enable passwords to be functions in erc-services

[Ted Zlatanov <tzz@lifelogs.com>]

On Thu, 09 Apr 2020 00:21:50 -0400 Amin Bandali <bandali@gnu.org> wrote: 

AB> +1.  Rudolf, what do you think about sending a new version with examples
AB> using the auth-source library, and maybe even the newer auth-source-pass
AB> as well?

erc.el uses auth-source.el so I agree this makes sense to add to
erc-services.el. Compared to Rudolf's proposed patch, I think this will
have the advantage of less code and easier integration for the user.

Maybe something like this (in the authinfo+.json format) would work for
the users?

machine MyService login myuser password mysecret
machine freenode login user1 password secret1
machine freenode login user2 password secret2

[
 { "machine": "MyService", "login": "myuser", "password": "mysecret" },
 { "machine": "freenode", "login": "user1", "password": "secret1" },
 { "machine": "freenode", "login": "user2", "password": "secret2" }
]

so then you'd just call:

(auth-source-search :host "MyService" :user "myuser")

auth-source-pass.el provides a backend for auth-source.el, so it will be
usable like all the other storage backends (.gpg files, plain files,
JSON files, Secrets API, etc). I don't think any extra work will be
required on the ERC side or the user side.

Ted