Displaying 20 results from an estimated 1140 matches for "crams".
Did you mean:
cram
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
When I used backup copy of the dovecot.conf file I have this same error. So
I think that maybe something was written to database? I really would point
out that I only added
passdb {
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
}
and comment out from above block default lines
#args = /etc/dovecot/dovecot-sql.conf
#driver = sql
And in auth_mechanisms add line
2017 Jan 31
3
Dovecot auth-worker error after cram-md5 auth
I set up cram-md5 using this tutorial
https://wiki2.dovecot.org/HowTo/CRAM-MD5 in /etc/dovecot/dovecot.conf in
passdb code block:
listen = *,[::]
protocols = imap pop3
#auth_mechanisms = plain login cram-md5
auth_mechanisms = cram-md5 plain login
#dodana nizej linia
ssl = required
disable_plaintext_auth = yes
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_privileged_group = vmail
2019 Jun 18
4
Help on CRAM-MD5
Howdy,
I'm using dovecot and mysql users, and i'm creating the password with:
ENCRYPT('some-passwd',CONCAT('$6$', SUBSTRING(SHA(RAND()), -16)))
So far so good, everything's fine.
Today saw that i didn't enabled CRAM-MD5, but if I do, and the (at least)
IMAP client (roundcube/thunderbird/etc) issues CRAM-MD5 it doesn't
authenticate.
What am i doing wrong, or
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
It still use:
passdb {
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
}
When I delete above and delete "cram-md5" in auth_mechanisms it still not
working.
2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> You are probably wanting to do
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
2015 Mar 18
2
Support for multiple passwords?
Am 2015-03-18 20:46, schrieb Reindl Harald:
> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki:
>> Hi!
>> Currently, the passwords are stored in plaintext for my dovecot, as I
>> am
>> still using cram-md5 AND digest-md5.
>> I have still to offer that, as I have some deprecated clients,
>> therefore, I am unable to hash at least those passwords for that
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
I can check each logs, I have root privileges.
2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> Can you check your logs?
>
> Aki
>
>
> On 01.02.2017 10:02, Poliman - Serwis wrote:
> > When I used backup copy of the dovecot.conf file I have this same error.
> So
> > I think that maybe something was written to database? I really would
>
2019 Jun 19
2
Help on CRAM-MD5
On 19.6.2019 7.48, Alexander Dalloz via dovecot wrote:
> Am 19.06.2019 um 00:04 schrieb Jorge Bastos via dovecot:
>> Howdy,
>>
>> I'm using dovecot and mysql users, and i'm creating the password with:
>>
>> ENCRYPT('some-passwd',CONCAT('$6$', SUBSTRING(SHA(RAND()), -16)))
>>
>> So far so good, everything's fine.
>>
2006 Jul 24
3
Problem with CRAM and flac-1.1.2
A user of CRAM (http://swami.sourceforge.net/cram.php) sent in a bug
report related to decoding of CRAM files. This issue occurs with
flac-1.1.2 but not previous versions (such as flac-1.1.1). Note that
the same file is used for this test (hopefully ruling out any issue with
the encoder).
Details of the issue:
When calling FLAC__stream_decoder_process_single() the error callback is
triggered
2004 Jul 22
3
CRAM-MD5
Hi,
after getting dovecot working with PostgreSQL and plaintext passwords
I tried to use md5 encrypted passwords with mozilla.
www.roughtrade.net/dovecot says that Mozilla only supports CRAM-MD5
and that CRAM-MD5 is included in HEAD.
Now I have two questions:
1) Is the md5 hash stored in passdb with cram-md5 the same as in
digest-md5?
2) Is a new dovecot stable build planned within the next two
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
Default it was: "auth_mechanisms = plain login" and I added cram-md5.
After restart all work perfectly. But after I added:
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
I can't set default lines because I got error. Please tell me which lines
should be changed to resolve this issue. Should I remove "login" from
auth_mechanism
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
Can you check your logs?
Aki
On 01.02.2017 10:02, Poliman - Serwis wrote:
> When I used backup copy of the dovecot.conf file I have this same error. So
> I think that maybe something was written to database? I really would point
> out that I only added
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
> }
>
> and comment out from
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
doveadm log errors can be helpful too
On 01.02.2017 10:25, Poliman - Serwis wrote:
> I can check each logs, I have root privileges.
>
> 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
>
>> Can you check your logs?
>>
>> Aki
>>
>>
>> On 01.02.2017 10:02, Poliman - Serwis wrote:
>>> When I used backup copy of the
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
Is there any strange thing in these config lines?
2017-02-01 9:40 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> doveadm log errors can be helpful too
>
>
> On 01.02.2017 10:25, Poliman - Serwis wrote:
> > I can check each logs, I have root privileges.
> >
> > 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> >
> >> Can
2015 Mar 18
2
Support for multiple passwords?
Quoting Reindl Harald <h.reindl at thelounge.net>:
> Am 18.03.2015 um 20:56 schrieb Conrad Kostecki:
>> Am 2015-03-18 20:46, schrieb Reindl Harald:
>>> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki:
>>>> Hi!
>>>> Currently, the passwords are stored in plaintext for my dovecot, as I
>>>> am
>>>> still using cram-md5 AND
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
Are you still trying to authenticate using cram-md5?
Aki
On 01.02.2017 09:51, Poliman - Serwis wrote:
> It still use:
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
> }
>
> When I delete above and delete "cram-md5" in auth_mechanisms it still not
> working.
>
> 2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
I haven't doveadm logs in /var/log/. Are they default in another place or
maybe should I turn on something?
My config (default passdb block and auth_mechanisms, nothing more changed):
root at vps342401:/etc/dovecot# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
listen = *,[::]
log_timestamp =
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
This is debug log files in syslog:
Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out:
CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4=
Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT<hidden>
Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069): Debug: sql(
do_not_reply at example.com,12.173.211.32): query: SELECT email as user,
2008 Jul 08
2
Dovecot CRAM-MD5 & DIGEST-MD5
Hello all.
Im try to make a SMTP Auth using Docecot SASL.
Im use swaks for tests.
Im store users in LDAP.
As im understand for CRAM & DIGEST MD5 we need to store pass in a clear
text?... Ok.
mail: admin3 at domain.off
userPassword: 123 <- Clear text
What im do
%swaks -a CRAM-MD5 -au admin3 at domain.off -ap 123
To: admin3 at domain.off
=== Trying mx.domain.off:25...
=== Connected to
2019 Jun 20
2
Help on CRAM-MD5
I don't desagree with your vision, but if the use of CRAM-XXXX has to use
plaint text password's on the server there's a dark side, or there's a
CRAM-XXX that can use encrypted on server side? There's always the thing
that can clients don't support it.
I think i'm not wrong with what i said,
On 20 Jun 2019, at 02:53, FUSTE Emmanuel via dovecot <dovecot at
2017 Feb 02
0
Dovecot auth-worker error after cram-md5 auth
I haven't doveadm logs in /var/log/. Are they default in another place or
maybe should I turn on something?
My config (default passdb block and auth_mechanisms, nothing more changed):
root at vps342401:/etc/dovecot# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
listen = *,[::]
log_timestamp = "%Y-%m-%d