From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: smtpmail and ~/.authinfo
Date: Tue, 27 Sep 2011 08:55:45 -0400 [thread overview]
Message-ID: <jwvipoe5f1a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1R8Vsh-0007P6-0Q@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 27 Sep 2011 07:31:23 -0400")
Here's my take on it:
.authinfo contains various things and is used in different ways, and
there isn't a single answer that covers all cases:
- each kind of field (hostname, username, password) may require
a different encoding/decoding.
- when reading a password from the file, it should be read using
raw-text (i.e. as a "unibyte string").
In other words, the password should not be decoded into chars but left
as a sequence of bytes that will be sent as-is to whoever needs it.
- when a password is typed by the user it'll be a sequence of chars, so
we'll have to convert it into a sequence of bytes. The best coding
system to use for that purpose is probably going to be
locale-coding-system. That sequence of bytes is then send to whoever
needs it and saved as-is (using raw-text) into the .authinfo file.
- i.e. authinfo should be read as a unibyte file.
- i.e. when reading other fields than passwords, we'll have to
explicitly decode them using the coding system we want to use for
those fields.
- similarly, we'll have to encode those other fields manually when
writing them into .authinfo.
Of course, another option is to just read&write authinfo without
thinking about it, so Emacs will usually pick locale-coding-system for
it and it'll work just fine in 99.9% of the cases.
Stefan
next prev parent reply other threads:[~2011-09-27 12:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 10:26 smtpmail and ~/.authinfo Eli Zaretskii
2011-08-21 4:39 ` Lars Magne Ingebrigtsen
2011-08-21 6:12 ` Eli Zaretskii
2011-08-21 19:25 ` Lars Magne Ingebrigtsen
2011-08-21 19:59 ` Eli Zaretskii
2011-08-21 20:17 ` Lars Magne Ingebrigtsen
2011-08-22 5:35 ` Eli Zaretskii
2011-09-10 19:01 ` Lars Magne Ingebrigtsen
2011-09-25 12:33 ` Ted Zlatanov
2011-09-25 12:48 ` Eli Zaretskii
2011-09-25 13:21 ` Ted Zlatanov
2011-09-25 17:08 ` Eli Zaretskii
2011-09-26 14:41 ` Ted Zlatanov
2011-09-26 16:18 ` Eli Zaretskii
2011-09-26 16:53 ` Ted Zlatanov
2011-09-26 17:15 ` Eli Zaretskii
2011-09-26 17:23 ` Eli Zaretskii
2011-09-26 17:31 ` Ted Zlatanov
2011-09-26 17:00 ` Stefan Monnier
2011-09-26 17:28 ` Ted Zlatanov
2011-09-26 21:27 ` Stefan Monnier
2011-09-26 18:04 ` Lars Magne Ingebrigtsen
2011-09-26 19:22 ` Ted Zlatanov
2011-09-26 19:30 ` Lars Magne Ingebrigtsen
2011-09-26 19:48 ` Ted Zlatanov
2011-09-26 21:31 ` Stefan Monnier
2011-09-26 21:43 ` Lars Magne Ingebrigtsen
2011-09-26 21:54 ` Ted Zlatanov
2011-09-27 4:07 ` Stephen J. Turnbull
2011-09-27 6:11 ` Lars Magne Ingebrigtsen
2011-09-27 10:29 ` Ted Zlatanov
2011-09-27 12:33 ` Stephen J. Turnbull
2011-09-27 20:15 ` Ted Zlatanov
2011-09-28 1:41 ` Stephen J. Turnbull
2011-09-28 8:38 ` Eli Zaretskii
2011-09-26 21:55 ` Ted Zlatanov
2011-09-27 2:57 ` Eli Zaretskii
2011-09-27 10:38 ` Ted Zlatanov
2011-09-27 11:31 ` Eli Zaretskii
2011-09-27 12:55 ` Stefan Monnier [this message]
2011-09-27 14:02 ` Jason Rumney
2011-09-26 19:34 ` Eli Zaretskii
2011-09-26 19:40 ` Ted Zlatanov
2011-09-27 2:51 ` Eli Zaretskii
2011-09-27 13:54 ` Jason Rumney
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=jwvipoe5f1a.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.