From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: eliz@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: smtpmail support of unicode passwords
Date: Mon, 14 Apr 2014 18:55:29 +0200 (CEST) [thread overview]
Message-ID: <20140414.185529.1321864689645246401.hanche@math.ntnu.no> (raw)
In-Reply-To: <838ur7ly88.fsf@gnu.org>
[Eli Zaretskii <eliz@gnu.org> (2014-04-14 15:36:23 UTC)]
> > Date: Mon, 14 Apr 2014 16:57:02 +0200 (CEST)
> > From: Harald Hanche-Olsen <hanche@math.ntnu.no>
> >
> > It is with some trepidation I notice that RFC 4616 does not mention
> > normalization at all. Are "élan" and "élan" the same password or not?
> > Should the latter (NFD) be normalized to the former (NFC) or not? Or
> > the other way around?
>
> If someone can find out what is TRT here, Emacs can normalize if
> needed.
Poking around a little more in RFC4616, I see a reference to SASLprep
(RFC 4013) and StringPrep (RFC 3454). Apparently, the correct
normalization is NFKC; however, that is considered optional, and
reading between the lines a bit, I think this normalization, if done
at allo, is intended to happen in the server – just prior to computing
the hash.
If I have that right, TRT on the client side is to just pass the
string through unchanged. Which is a relief.
Apologies for not doing this small bit of research before raising the
issue.
– Harald
next prev parent reply other threads:[~2014-04-14 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 18:27 smtpmail support of unicode passwords Garreau, Alexandre
2014-04-13 19:11 ` Eli Zaretskii
2014-04-14 1:18 ` Stefan Monnier
2014-04-14 5:50 ` Stephen J. Turnbull
2014-04-14 8:18 ` Eli Zaretskii
2014-04-14 7:44 ` Eli Zaretskii
2014-04-14 12:14 ` Stephen J. Turnbull
2014-04-14 12:27 ` Eli Zaretskii
2014-04-14 12:55 ` Stefan Monnier
2014-04-14 14:57 ` Harald Hanche-Olsen
2014-04-14 15:36 ` Eli Zaretskii
2014-04-14 16:55 ` Harald Hanche-Olsen [this message]
2014-04-14 18:03 ` Stephen J. Turnbull
2014-04-14 21:01 ` Eli Zaretskii
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=20140414.185529.1321864689645246401.hanche@math.ntnu.no \
--to=hanche@math.ntnu.no \
--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.