Timo Sirainen wrote:
> On Jun 16, 2009, at 4:01 AM, Tom Sommer wrote:
>
> # TTL for negative hits (user not found). 0 disables caching them
> completely.
> #auth_cache_negative_ttl = 3600
>
> I suppose there could be a new setting to use auth cache only for
> successful look
On Jun 16, 2009, at 4:01 AM, Tom Sommer wrote:
# TTL for negative hits (user not found). 0 disables caching them
completely.
#auth_cache_negative_ttl = 3600
I suppose there could be a new setting to use auth cache only for
successful lookups..
I don't understand why it would cache negative
Timo Sirainen wrote:
> On Sun, 2009-05-17 at 21:09 +0200, Tom Sommer wrote:
>
>> Timo Sirainen wrote:
>>
The cache seems to be faulty somehow, I wish there was a way to dump the
contents of the cache to debug this, because somehow I cannot forcefully
reproduce it.
>
On Sun, 2009-05-17 at 21:09 +0200, Tom Sommer wrote:
> Timo Sirainen wrote:
> >> The cache seems to be faulty somehow, I wish there was a way to dump the
> >> contents of the cache to debug this, because somehow I cannot forcefully
> >> reproduce it.
> >>
> >
> > Here's a way:
> >
> > 1. Try t
Timo Sirainen wrote:
The cache seems to be faulty somehow, I wish there was a way to dump the
contents of the cache to debug this, because somehow I cannot forcefully
reproduce it.
Here's a way:
1. Try to log in unsuccessfully.
2. Change the password.
3. Try to log in with the changed pas
On Fri, 2009-05-15 at 09:29 +0200, Tom Sommer wrote:
> I'm sorry, but I still have problems with this. I got cache_size 1024,
> cache_ttl 3600, cache_negative_ttl 0, but if a user changes password in
> my SQL, sometimes it requires a restart of dovecot for him to be able to
> log in.
You can alwa
Tom Sommer wrote:
> Timo Sirainen wrote:
>> On Tue, 2009-01-20 at 09:53 +0100, Tom Sommer wrote:
>>
>>> sql(u...@example.com,127.0.0.1): query: SELECT username as user,
>>> plainpassword as password, nopassword FROM cyrususers WHERE username
>>> = 'u...@example.com' AND password = PASSWORD('SECRE
Timo Sirainen wrote:
On Tue, 2009-01-20 at 09:53 +0100, Tom Sommer wrote:
sql(u...@example.com,127.0.0.1): query: SELECT username as user,
plainpassword as password, nopassword FROM cyrususers WHERE username =
'u...@example.com' AND password = PASSWORD('SECRET') AND active = 1
dovecot: Jan 2
On Tue, 2009-01-20 at 09:53 +0100, Tom Sommer wrote:
> sql(u...@example.com,127.0.0.1): query: SELECT username as user,
> plainpassword as password, nopassword FROM cyrususers WHERE username =
> 'u...@example.com' AND password = PASSWORD('SECRET') AND active = 1
> dovecot: Jan 20 09:01:18 Info: a
Timo Sirainen wrote:
On Mon, 2009-01-05 at 14:33 +0100, Tom Sommer wrote:
Sorry to bump this, but I can still reproduce it - I have enabled
auth_debug now to attempt to provide some more details.
Actually enable auth_debug_passwords=yes. It then also logs what's seen
in the cache entri
On Mon, 2009-01-05 at 14:33 +0100, Tom Sommer wrote:
> Sorry to bump this, but I can still reproduce it - I have enabled
> auth_debug now to attempt to provide some more details.
Actually enable auth_debug_passwords=yes. It then also logs what's seen
in the cache entries.
signature.asc
Descript
Timo Sirainen wrote:
On Thu, 2008-08-21 at 09:11 +0200, Tom Sommer wrote:
Timo Sirainen wrote:
On Tue, 2008-08-19 at 15:49 +0200, Tom Sommer wrote:
On Tue, August 19, 2008 15:44, Tom Sommer wrote:
Using version 1.1.1, MySQL userdb, with "nopassword=Y".
Maybe it's due
On Thu, 2008-08-21 at 09:11 +0200, Tom Sommer wrote:
> Timo Sirainen wrote:
> > On Tue, 2008-08-19 at 15:49 +0200, Tom Sommer wrote:
> >> On Tue, August 19, 2008 15:44, Tom Sommer wrote:
> >>
> >>> Using version 1.1.1, MySQL userdb, with "nopassword=Y".
> >>>
> >>> Maybe it's due to nopassword?
> >
Timo Sirainen wrote:
On Tue, 2008-08-19 at 15:49 +0200, Tom Sommer wrote:
On Tue, August 19, 2008 15:44, Tom Sommer wrote:
Using version 1.1.1, MySQL userdb, with "nopassword=Y".
Maybe it's due to nopassword?
Should add, this is my password_query:
password_query = SELECT username as user, N
On Tue, 2008-08-19 at 15:49 +0200, Tom Sommer wrote:
> On Tue, August 19, 2008 15:44, Tom Sommer wrote:
>
> > Using version 1.1.1, MySQL userdb, with "nopassword=Y".
> >
> > Maybe it's due to nopassword?
>
> Should add, this is my password_query:
>
> password_query = SELECT username as user, NUL
On Tue, August 19, 2008 15:44, Tom Sommer wrote:
> Using version 1.1.1, MySQL userdb, with "nopassword=Y".
>
> Maybe it's due to nopassword?
Should add, this is my password_query:
password_query = SELECT username as user, NULL as password, "Y" as
nopassword FROM users WHERE ...
Does the auth ca
Hi,
I have an issue with the authentication cache.
When a user changes his password, the cache doesn't seem to get flushed.
Meaning the user is unable to log in to his IMAP account after changing
his password.
Flow:
- Log into IMAP account using pass1
- Approved
- Stored in auth cache
- Ch
17 matches
Mail list logo
