Yes, thanks a lot - this config is working as expected.
On 27.11.2012, at 9.37, Nikita Koshikov wrote:
>>> Here is the problem:
>>> I have few:
>>> passdb {
>>> #1
>>> }
>>> passdb {
>>> #2
>>> }
>>> And relative userdb sections. If user not found in 1) section it
>> fallbacks
>>> to next one - it's expected and right, IMHO. But when the user exists in
On Tue, Nov 27, 2012 at 3:04 AM, Timo Sirainen wrote:
> On 23.11.2012, at 9.46, Nikita Koshikov wrote:
>
> > Hello list,
> >
> > Here is the problem:
> > I have few:
> > passdb {
> > #1
> > }
> > passdb {
> > #2
> > }
> > And relative userdb sections. If user not found in 1) section it
> fallback
On 23.11.2012, at 9.46, Nikita Koshikov wrote:
> Hello list,
>
> Here is the problem:
> I have few:
> passdb {
> #1
> }
> passdb {
> #2
> }
> And relative userdb sections. If user not found in 1) section it fallbacks
> to next one - it's expected and right, IMHO. But when the user exists in
> bot
On Fri, 23 Nov 2012 12:20:23 +0100
Alessio Cecchi wrote:
> Il 23/11/2012 08:46, Nikita Koshikov ha scritto:
> > Hello list,
> >
> > Here is the problem:
> > I have few:
> > passdb {
> > #1
> > }
> > passdb {
> > #2
> > }
> > And relative userdb sections. If user not found in 1) section it fallback
Il 23/11/2012 08:46, Nikita Koshikov ha scritto:
Hello list,
Here is the problem:
I have few:
passdb {
#1
}
passdb {
#2
}
And relative userdb sections. If user not found in 1) section it fallbacks
to next one - it's expected and right, IMHO. But when the user exists in
both section and password
Hello list,
Here is the problem:
I have few:
passdb {
#1
}
passdb {
#2
}
And relative userdb sections. If user not found in 1) section it fallbacks
to next one - it's expected and right, IMHO. But when the user exists in
both section and password verification fails on 1) database it successfully
a
