similar to: CRAM-MD5 HMAC-MD5 password algorithm for PHP

Hi, I'm just in the middle of setting up dovecot to serve IMAPS -- Actually I've finished apart from one thing: CRAM-MD5 passwords. I'm using SQL as a backend for the password storage, and I don't want to store the passwords in plaintext. I've also configured dovecot to be rather restrictive when it comes to authentication methods (only CRAM-MD5 is allowed). To generate the

Hello, I want to use PostgreSQL to store my Dovecot users. I setup a very basic configuration, following word for word this page http://wiki.dovecot.org/DovecotPostgresql and it works ... almost. In fact, it works if I use PLAIN password scheme in my database. However, I would like to store them encrypted. But, if I replace the password field for my user with {HMAC-MD5}-... (the password

Hi List, My FC2 Wine installation crashes (without any message displayed) on every application which shows the std. file selection dialog (eg File - Open) as soon as I change the directory in the dialog or click "OK" or "Cancel". This even happens with the stock "notepad" that comes with Wine. "Winefile" however can browse the file systems correctly,

$ dovecotpw -p testpass {HMAC-MD5}fe8522268d91e485ccac8f36800e4fa6b10363e2a371cfa61731109b450906cd I wonder if the prefix 'HMAC-MD5' is the correct notation here. According to RFC2104 an HMAC is calculated as follows: H(K XOR opad, H(K XOR ipad, text)) where H is the cryptographic hash function (MD5 in this case). Therefore the result has to be a 128 bit string, which is obviously not

Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves. Am 15.02.2019 um 11:35 schrieb Hajo Locke via dovecot: > Hello, > > Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot: >> El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: >>> Hello, >>> >>> Am 11.02.2019 um 09:12 schrieb Hajo

Hello, Am 21.02.2019 um 10:51 schrieb Aki Tuomi via dovecot: > On 21.2.2019 10.53, Hajo Locke via dovecot wrote: >> Hello, >> >> Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot: >>>> On 18 February 2019 09:28 Hajo Locke via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> >>>> >>>> Hello, >>>>

El 21/02/2019 a las 10:51, Aki Tuomi via dovecot escribi?: > On 21.2.2019 10.53, Hajo Locke via dovecot wrote: >> Hello, >> >> Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot: >>>> On 18 February 2019 09:28 Hajo Locke via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> >>>> >>>> Hello, >>>> ?

/etc/dovecot.conf: auth default { mechanisms=plain login cram-md5 passdb { #.............. Windows Live Mail: CRAM-MD5 authentication failed. This could be due to a lack of memory on your system. Your IMAP command could not be sent to the server, due to non-network errors. This could, for example, indicate a lack of memory on your system. Configuration: Account: Sheltoncomputers

Thanks, Hajo This mostly works, but we can?t seem to send an arbitrary mailbox name with UserDB, we have to initialize it in the config: "namespace/inbox/mailbox=Junk namespace/inbox/mailbox/Junk/name"="Spam" seems to initialize the folder somehow so that the subsequent "namespace/inbox/mailbox/Junk/auto"="subscribe" and

After upgrading my dovecot installation about a month ago, I have started seeing "Requested CRAM-MD5 scheme, but we have only MD5-CRYPT" message from dovecot in my logs. Any help in finding and correcting the cause will be greatly appreciated. --Richard

Hi all, Got a question on configuring dovecot, I'm still new at this so I might be doing this all wrong. I want dovecot to authenticate the mail client using CRAM-MD5 so I've setup the config in dovecot.conf: auth default { mechanisms = cram-md5 passdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf args = /etc/dovecot/dovecot-sql.conf

We have a plethora of accounts for which we would like to enable CRAM-MD5 but their passwords are stored as MD5 hashes. Is there anything we can do? Can we take a linux MD5 hashed password (e.g. $1$fac330ee$wd6Tll...) and convert it to dovecot's CRAM-MD5 format (e.g. {CRAM-MD5}b3f297...)? Thanks!

On 12/5/14, ML mail <mlnospam at yahoo.com> wrote: > Hello, > > I am wondering which variant is more secure for user authentication and > password scheme. Basically I am looking at both variants: > > 1) MD5-CRYPT password scheme storage with CRAM-MD5 auth mechanism > 2) SHA512-CRYPT password scheme storage with PLAIN auth mechanism > > In my opinion the option 2)

Am 06.12.2014 um 06:56 schrieb Jan Wide?: > If you add disable_plaintext_auth=yes ssl=required settings, then > dovecot will drop authentication without STARTTLS. But damage will be > done, client will send unencrypted (or in this scenario MD5 or SHA512 > hash) login/password no, damage will *not* be done STARTTLS happens in context of connect and *log before* any authentication is

El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: > Hello, > > Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot: >> Hello, >> Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: >>> Hello List, >>> >>> i have a problem with index-files which is separated in 2 >>> subproblems. May be these problems are connected.

On Mon, 16 Jan 2017 09:07:35 -0800 (PST) rawi via samba <samba at lists.samba.org> wrote: > Samba - General mailing list wrote > >> [2017/01/11 16:42:34.522067, 1] > >> ../source3/librpc/crypto/gse.c:496(gse_get_server_auth_token) > >> gss_accept_sec_context failed with [ Miscellaneous failure (see > >> text): Failed to find cifs/hg004.humgen.0zone

Hello, Am 16.01.2017 um 18:07 schrieb rawi via samba: > I discovered, that the generated smb.conf was not enough for an AD-DC. > > Despite having: > > server role = active directory domain controller > > ... the default settings for: > > domain logons = no (?) > domain master = auto (aka equally NO) > local master = yes > > (not specifically mentioned

On 16/12/2019 20:22, Jonathon Reinhart via samba wrote: > Hello everyone, > > I have a FreeNAS server (9.10 running samba 4.3.11-GIT-UNKNOWN) that's recently > started emitting this error: > If you are running Samba 4.3.11 then you should be aware that it is EOL and bug 12262 was fixed in 4.4, so I would suggest you upgrade to a supported Samba version. You will probably find

On 18/12/2019 14:34, Jonathon Reinhart wrote: > On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > Problem is, and as I said, Samba? 4.3.x is EOL as far as Samba is > concerned and if you have found a bug in it, it is very, very > unlikely > to get fixed, unless it is

Hello, Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot: > El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: >> Hello, >> >> Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot: >>> Hello, >>> Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: >>>> Hello List, >>>> >>>> i have a problem