Timo Sirainen wrote:
> Couldn't you change the client to use AUTHENTICATE PLAIN command instead?
> The buffer wouldn't be a problem then..
Sorry for the delay, I missed the reply.
That is not an option, as the client is not SASL capable.
--- src/lib-master/master-auth.h.orig
+++ src/lib-ma
On 16.8.2012, at 4.07, Emmanuel Dreyfus wrote:
> 38 month ago, I submitted a patch to increase
> AUTH_WORKER_MAX_LINE_LENGTH to use exotic authentication scheme (see
> message below). The patch was accepted, but now I upgrade to dovecot
> 2.1.7, I face the same problem with MASTER_AUTH_MAX_DATA_S
Hi
38 month ago, I submitted a patch to increase
AUTH_WORKER_MAX_LINE_LENGTH to use exotic authentication scheme (see
message below). The patch was accepted, but now I upgrade to dovecot
2.1.7, I face the same problem with MASTER_AUTH_MAX_DATA_SIZE. I had to
increase it from 1024 to 4096.
Is it
On Wed, Jun 24, 2009 at 02:21:50PM -0400, Timo Sirainen wrote:
> There's no real reason to keep it at 1 kB. I probably didn't even think
> about it much when I added it. I increased it to 8192 now.
Thanks a lot!
--
Emmanuel Dreyfus
m...@netbsd.org
On Wed, 2009-06-24 at 14:45 +, Emmanuel Dreyfus wrote:
> I have been playing with some exotic authentication scheme with Dovecot
> and PAM. That involves sending really large base64 encoded data as
> the IMAP password, and I have hit a line limit in Dovecot, with
> AUTH_WORKER_MAX_LINE_LENGTH
Hello
I have been playing with some exotic authentication scheme with Dovecot
and PAM. That involves sending really large base64 encoded data as
the IMAP password, and I have hit a line limit in Dovecot, with
AUTH_WORKER_MAX_LINE_LENGTH set to 1024.
This limit is especially frustrating since oth
