popa3d-users - Re: [PATCH] RFC2449 "CAPA" support

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Fri, 26 Aug 2005 17:47:35 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: [PATCH] RFC2449 "CAPA" support

On Thu, Aug 25, 2005 at 06:40:06PM -0700, N.Cat wrote:
> Since some clients want capabilities to be described (e.g. KMail complains 
> that it can't determine UIDL support),

I was unaware that such clients existed.  Although adding CAPA support
to popa3d has been on TODO for years, I was not planning on doing that
until popa3d would have to say anything beyond RFC 1939's definitions. (*)

> I implemented the "CAPA" command as per RFC 2449.
> The capabilities set also includes "pass" (it's identical to NGPopper's).

RFC 2449 doesn't define a capability named PASS.  Unless there's a
client which depends on it, I would rather not declare it.

(*) Well, frankly, I was about to add CAPA support into popa3d in 1999,
but then put it on the back burner.  There are also some problems with
RFC 2449 (especially with PIPELINING) that noone has bothered to comment
on (let alone fix them in a subsequent revision of the RFC):

	http://www.imc.org/ietf-pop3ext/mail-archive/msg00083.html

Thanks,

-- 
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments

Was I helpful?  Please give your feedback here: http://rate.affero.net/solar