From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: pop3.el broken
Date: 18 Mar 2002 13:04:24 -0500 [thread overview]
Message-ID: <02Mar18.130027est.119225@gateway.intersystems.com> (raw)
In-Reply-To: <iluit7tkdg5.fsf@extundo.com>
* Simon Josefsson <jas@extundo.com> on Mon, 18 Mar 2002
| Huh? A password is a text string, entered on the keyboard. As such, it
| must be encoded in some character set in order to be input to a hash
| function.
No, it isn't. A pass phrase could be an 8-bit string, not necessarilly
humanly readable text, and not necessarilly entered on a keyboard. That is
an extreme situation, but if 8-bit pass phrases are to be accepted then
this extreme must be taken into consideration. Such a string must never be
encoded as anything. Or, to MULEtilate it, the coding system is binary
since no-conversion doesn't mean no-conversion some of the time.
| pop3 has implicitely encoded it as ASCII traditionally, assuming that
| (md5 "foobar") encodes the characters "foobar" as ASCII characters before
| applying md5 on it.
pop3.el has never made any such assumption. MULE may make it seem to
appear that it does, but I have long maintained that MULE is broken in this
regard. Emacs Lisp should work identically in any Emacs without having to
work around the environment's brain-damaged assumptions.
[...]
| If you send a patch to the Emacs maintainers that modifies it to what
| you want [as long as it works] I would hope that they will unfork it.
I did, and the FSF did not.
By the way, you cannot use the FSF's version with a VAX/VMS POP server. I
fixed that bug in 1998, but the FSF has ignored the fix after repeated
submissions.
I gave up in disgust.
[...]
| Right, I wish that XEmacs pop3.el could be reverted to your version
| (and that you would handle the bug reports ;)), and that people
| wanting enhanced behaviour could use epop3 or another package
| containing the current XEmacs pop3.el. It is confusing to fork code
| and not change the name.
Too little, too late. I asked them repeatedly to change the name. They
refused, or simply ignored the request.
I gave up in disgust.
[...]
| Defadvice isn't a good long term solution.
Yes, well, given that the real problem, MULE, will never be fixed, advice
is the only solution that has a reasonable chance of working everywhere.
There are three hopelessly forked versions of pop3.el out there. Creating
a fourth is not going to help.
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball contains a liquid core,
Minion of Nathan - Nathan says Hi! \ which, if exposed due to rupture, should
PGP Key: at a key server near you! \ not be touched, inhaled, or looked at.
That and five bucks will get you a small coffee at Starbucks.
next prev parent reply other threads:[~2002-03-18 18:04 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
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 [this message]
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=02Mar18.130027est.119225@gateway.intersystems.com \
--to=ratinox@peorth.gweep.net \
/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).