[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 9717ba9: Specify precedence in .authinfo files
From: |
Lars Ingebrigtsen |
Subject: |
master 9717ba9: Specify precedence in .authinfo files |
Date: |
Sun, 10 Jan 2021 09:33:49 -0500 (EST) |
branch: master
commit 9717ba930975d772412c65b0e2dbb9258cf502bd
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
Specify precedence in .authinfo files
* doc/misc/auth.texi (Help for users): Mention placing more
specific entries first (bug#45711).
---
doc/misc/auth.texi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/misc/auth.texi b/doc/misc/auth.texi
index d810f15..034004d 100644
--- a/doc/misc/auth.texi
+++ b/doc/misc/auth.texi
@@ -107,6 +107,18 @@ The @code{user} is the user name. It's known as
@var{:user} in
@code{auth-source-search} queries. You can also use @code{login} and
@code{account}.
+Matching entries are usually used in the order they appear, so placing
+the most specific entries first in the file is a good idea. For
+instance:
+
+@example
+machine example.com login foobar password geheimnis port smtp
+machine example.com login foobar password hemmelig
+@end example
+
+Here we're using one password for the @code{smtp} service, and a
+different one for all the other services.
+
You can also use this file to specify client certificates to use when
setting up TLS connections. The format is:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 9717ba9: Specify precedence in .authinfo files,
Lars Ingebrigtsen <=