similar to: Headsup on feature removal

Displaying 20 results from an estimated 8000 matches similar to: "Headsup on feature removal"

2020 Mar 18
2
Headsup on feature removal
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Those plugins can be resurrected with simple `git revert`. </div> <div> <br> </div> <div> Are you planning on open sourcing your client id authetication plugin? </div> <div> <br> </div>
2020 Mar 18
3
Headsup on feature removal
So I am on of the many users with qmail, and using vpopmail auth, I guess chatting with some other guys in the other mailing list we will convert to mysql driver but this is a lot of work for many people. I do understand dropping things out but a valid solutions needs to be proposed. Remo > On Mar 18, 2020, at 06:49, Michael Peddemors <michael at linuxmagic.com> wrote: > >
2020 Mar 17
0
Headsup on feature removal
With these planned changes, you mention they will be removed from 'core', so is the intention to allow more of these legacy plugins to more to their own repo's for those that might still want to use them? Eg, more in the the path of plug-in architecture? Just curious for clarity. Oh, and have to add.. still waiting on the variable capability patch, to allow plugins to modify
2020 Mar 18
0
Headsup on feature removal
Amongst other plug-ins, yes.. On 2020-03-17 10:15 p.m., Aki Tuomi wrote: > Those plugins can be resurrected with simple `git revert`. > > Are you planning on open sourcing your client id authetication plugin? > > Aki >> On 18/03/2020 01:44 Michael Peddemors < michael at linuxmagic.com >> <mailto:michael at linuxmagic.com>> wrote: >> >>
2020 Mar 18
0
Headsup on feature removal
Hi! I understand that it is not trivial to move away from vpopmail and does require changing a working system. But then again, one should be able to configure MySQL passdb/userdb with vpopmail schema. I am not familiar with vpopmail but if someone comes with instructions we can polish them a bit (if necessary) and publish them as howto on doc.dovecot.org. Aki > On 18/03/2020 17:52 Remo
2020 Mar 19
2
[Dovecot-news] Headsup on feature removal
Hi! We appreciate the feedback we have received from everyone, and we have discussed it internally. The features we are removing are deprecated and should not have been used anymore. They all have alternatives that work equally well if not better. For the authentication drivers, you can use passwd, pam and Lua as replacements for most of them. Lua in particular allows good integration with just
2020 Mar 17
3
Headsup on feature removal - password
> Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5 The web is flooded with plain text passwords and hashed passwords harvested from hacked servers. Dovecot stores passwords with the same scheme used for client authentication. Therefore, we use crammd5/hmac-md5. It does not look like much, but is better than plaintext. As md5 is about to go, and I have no intention to
2020 Mar 18
2
[Dovecot-news] Headsup on feature removal
On 19/03/2020 03:56, JAVIER MIGUEL RODRIGUEZ wrote: > I fully agree with this: > >> Please consider holding off on removing features for the next major >> release, 2.4.0 instead. It makes sense to retain, in as much as is >> possible, feature backwards compatibility across a major release. I'm astonished that features are being removed in a dot release as well, no
2018 Dec 06
3
argonid and dovecote
on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play nice with "argonid" encryption. In the "10-auth.conf" file, I tried: auth_mechanisms = plain argon2id Upon restarting dovecot, I received an error message when attempting to actually it: auth: FATAL: Unknown authentication mechanism "ARGON2ID" Output from doveadm pw -l doveadm pw -l SHA1
2020 Mar 18
0
Headsup on feature removal - password
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 18/03/2020 00:06 Rupert Gallagher <ruga@protonmail.com> wrote: </div> <div> <br> </div> <div> <br>
2020 Mar 18
2
Headsup on feature removal - password
Was there any reason for this message to be HTML-only? On Wed, Mar 18, 2020 at 07:13:12AM +0200, Aki Tuomi wrote: > <!doctype html> > <html> > <head> > <meta charset="UTF-8"> > </head> > <body> > <div> > <br> > </div> > <blockquote type="cite"> > <div> >
2018 Dec 03
2
dovecot and argon2 encryption
I am using a FreeBSD 11-2 amd/64 system with dovecot version 2.3.4 installed. I was playing around with different encryption schemes. doveadm pw -l SHA1 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CRYPT CRYPT SSHA MD5-CRYPT SKEY PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 LANMAN SHA512-CRYPT CLEAR CLEARTEXT SSHA256 NTLM MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5
2016 Jun 03
3
Blowfish hashed passwords
(I subscribed to a daily digest for this list and can?t figure out how to reply to a reply.) Anyway, Aki Tuomi replied to my feature request saying: > We support in latest 2.2 release > > MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN > CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 > PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY
2019 Feb 13
3
Using SHA256/512 for SQL based password
On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote: > > > Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz > <rgm at htt-consult.com>: > >> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote: >>> Am 12.02.2019 um 17:05 schrieb Robert Moskowitz via dovecot: >>>> I have trying to find how to set the dovecot-sql.conf for using
2019 Feb 13
1
Using SHA256/512 for SQL based password
On 2/13/19 8:30 AM, Aki Tuomi wrote: > On 13.2.2019 15.18, Robert Moskowitz via dovecot wrote: >> >> On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote: >>> >>> Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz >>> <rgm at htt-consult.com>: >>> >>>> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote:
2019 Feb 13
3
Using SHA256/512 for SQL based password
On 2/13/19 8:30 AM, Aki Tuomi wrote: > On 13.2.2019 15.18, Robert Moskowitz via dovecot wrote: >> >> On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote: >>> >>> Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz >>> <rgm at htt-consult.com>: >>> >>>> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote:
2020 Mar 18
0
[Dovecot-news] Headsup on feature removal
On 17/03/20 7:50 pm, Aki Tuomi wrote: > Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. > > We are starting to gradually remove some of these parts, which are unused, untested or deprecated. > We will provide advance notification before removing anything. > > To start, the following
2019 Feb 14
3
Using SHA256/512 for SQL based password
Jean-Daniel Dupas via dovecot wrote: > > >> Le 13 f?vr. 2019 ? 14:54, Robert Moskowitz via dovecot >> <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> a ?crit : >> >> >> >> On 2/13/19 8:30 AM, Aki Tuomi wrote: >>> On 13.2.2019 15.18, Robert Moskowitz via dovecot wrote: >>>> >>>> On 2/13/19 1:23 AM,
2018 Dec 04
1
dovecot and argon2 encryption
On 12/4/18, 1:14 AM, "dovecot on behalf of Aki Tuomi" <dovecot-bounces at dovecot.org on behalf of aki.tuomi at open-xchange.com> wrote: On 3.12.2018 22.24, Jerry wrote: > I am using a FreeBSD 11-2 amd/64 system with dovecot version 2.3.4 installed. > I was playing around with different encryption schemes. > > doveadm pw -l > SHA1
2019 Feb 20
4
Using SHA256/512 for SQL based password
On 2/19/19 1:50 AM, Aki Tuomi via dovecot wrote: > > > On 17.2.2019 10.46, Aki Tuomi via dovecot wrote: >> >>> On 17 February 2019 at 10:38 Odhiambo Washington via dovecot < >>> dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >>> >>> >>> On Sun, 17 Feb 2019 at 11:34, Marc Weustink via dovecot < >>>