From: Simon Josefsson <jas@extundo.com>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: pop3.el broken
Date: Sat, 16 Mar 2002 10:59:20 +0100 [thread overview]
Message-ID: <iluit7wesuf.fsf@extundo.com> (raw)
In-Reply-To: <m3bsdpxipk.fsf@peorth.gweep.net> (Stainless Steel Rat's message of "15 Mar 2002 23:03:19 -0500")
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Simon Josefsson <jas@extundo.com> on Fri, 15 Mar 2002
> | The problem really is that POP3/APOP does not define in what encoding the
> | password should be encoded into before inputting it to the hash function.
> | It is left as a customization things, which means that only ASCII will
> | interoperate unless you configure your client to what the server uses.
>
> Actually, er... as I recall, POP3 passwords are not 8-bit clean (they are
> also Unix passwords). Simple ASCII is all that is allowed.
Then passing 'ascii as the CODING-SYSTEM for `md5' seem like the right
thing. If we want to extend the spec a little with the most likely
politically correct coding system this week, we could change it into
'utf-8 (if the Emacs supports CODING-SYSTEM and the utf-8 coding
system), which is compatible with ascii for ASCII-only characters, so
it shouldn't break correct usage. The coding system to use should be
customizable, of course.
> Same goes for APOP and I think KPOP as well. You are doing
> something very, very wrong if you try to use 8-bit characters in
> passwords like that.
APOP/KPOP doesn't transfer the password, so perhaps this area is
underspecified. KPOP uses Kerberos, which "supports" non-ASCII
characters, but only if the client and server uses the same charsets.
AFAICR, they are moving towards UTF-8.
next prev parent reply other threads:[~2002-03-16 9:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:58 Pavel Janík
2002-03-13 15:50 ` Stainless Steel Rat
2002-03-13 16:20 ` Bill White
2002-03-13 16:31 ` Bill White
2002-03-13 17:46 ` Bill White
2002-03-13 17:53 ` Paul Jarc
2002-03-13 20:21 ` Karl Kleinpaste
2002-03-13 19:58 ` Simon Josefsson
2002-03-13 22:39 ` Katsumi Yamaoka
2002-03-14 4:52 ` Stainless Steel Rat
2002-03-14 7:01 ` Katsumi Yamaoka
2002-03-14 9:35 ` Simon Josefsson
2002-03-14 22:11 ` Stainless Steel Rat
2002-03-15 13:18 ` Katsumi Yamaoka
2002-03-15 18:03 ` Simon Josefsson
2002-03-16 4:03 ` Stainless Steel Rat
2002-03-16 9:59 ` Simon Josefsson [this message]
2002-03-16 10:24 ` Simon Josefsson
2002-03-16 15:19 ` Stainless Steel Rat
2002-03-18 13:03 ` Katsumi Yamaoka
2002-03-18 15:53 ` Stainless Steel Rat
2002-03-18 17:12 ` Simon Josefsson
2002-03-18 18:04 ` Stainless Steel Rat
2002-03-18 17:30 ` Simon Josefsson
2002-03-18 23:43 ` Katsumi Yamaoka
2002-03-19 1:13 ` Stainless Steel Rat
2002-03-19 9:54 ` Simon Josefsson
2002-03-16 3:57 ` Stainless Steel Rat
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=iluit7wesuf.fsf@extundo.com \
--to=jas@extundo.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).