similar to: dovecot sha512-crypt database storage

Displaying 20 results from an estimated 2000 matches similar to: "dovecot sha512-crypt database storage"

2018 Mar 10
0
dovecot sha512-crypt database storage
Hi, Thanks. That query doesn't return any parse errors but it does say that it can't save the password. Any ideas? Thanks. Dave. On 3/10/18, David Mehler <dave.mehler at gmail.com> wrote: > Hello, > > Thanks. Trying that query adapted to my database table and getting an > error can not save password, any ideas? > > When you made your initial database tables how
2018 Jun 25
2
doveadm: problem listing shared mailboxes using a wildcard
* Thore B?decker <me at foxxx0.de>: > You might need to quote that last argument, otherwise it can get > interpreted by the shell as globbing, which obviously is not what you > want. > > I've been using wildcard arguments enclosed within '' and "" for > various doveadm commands without issues so far. Right. I had thought so too (and forgot to mention
2018 Mar 11
2
dovecot sha512-crypt database storage
On 2018-03-10 (16:48 MST), David Mehler <dave.mehler at gmail.com> wrote: > > Thanks. That query doesn't return any parse errors but it does say > that it can't save the password. Are you referencing the right table in your database? -- It is the business of the future to be dangerous.
2018 Mar 11
1
dovecot sha512-crypt database storage
On Mar 11, 2018, at 10:19, David Mehler <dave.mehler at gmail.com> wrote: > Other suggestions welcome. Does the account you are using have access to write the new passwords?> Doe s the command work from the command line or phpmyadmin? -- My main job is trying to come up with new and innovative and effective ways to reject even more mail. I'm up to about 97% now.
2018 Jun 25
3
doveadm: problem listing shared mailboxes using a wildcard
I'm setting up a dovecot server with private and shared namespaces. My test setup has these mailboxes: # /bin/doveadm mailbox list -u fdl01 at spike.test INBOX/sub01 shared shared/sammel01 at spike.test shared/sammel02 at spike.test INBOX In order to do some post-login scripting foo I'd like to get a list of shared mailboxes the user is currently subscribed to. The doveadm-mailbox man
2013 Dec 25
1
SHA512-CRYPT scheme fails password verification
Hello, If I try to use the crypt schemes provided by libc. I fail as follows: jnikula at jlaptop:~/$ doveadm pw -s SHA512-CRYPT -p 123456 {SHA512-CRYPT}$6$to2umWLDtqvzS8SV$ZGpBeGNKuUN/2HKG6I2BEAt.Gzrz/y.SZDkos2GT2ik8obnp3XCFWfVsKVriJa6jjHULmLIqCSSyaF5YrTH7u. jnikula at jlaptop:~/$ doveadm pw -t
2014 Aug 12
3
doveadm pw with SHA512-CRYPT won't roundtrip
Hi, Not sure if this is a PBKAC or not:- root at ds3:/usr/share/postfixadmin# doveadm pw -s SHA512-CRYPT -p password {SHA512-CRYPT}$6$aUgGXP0UshkMj7hY$9JV4yMRsjIe/98CzmglYrMjf.9NJ.FXzxcLE9B0v3doCRUWo2wRncc6hg6VCs0DCUHQbeC/bRDZdGCge/nB/h/ root at ds3:/usr/share/postfixadmin# doveadm pw -t
2014 Dec 05
3
MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
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) should be safer although it is using PLAIN auth mechanism. Of course I would always use STARTTLS and
2015 May 01
1
Fatal: Unknown scheme: SHA512-CRYPT. On a Mac-mini
Running postfix+dovecot+mysql on a mac-mini, and trying to solve this puzzle. Is this a Mac issue?, a MySQL issue? or something I haven't configured in? You can see from the output of the samples shows in the first case, that SHA512-CRYPT seems to be Unknown. The code I used is from a Linux based tutorial on setting up Postfix+Dovecot+MySQL on a site. Everything is generally going ok, apart
2014 Dec 06
3
MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
On 12/06/2014 02:35 AM, Nick Edwards wrote: > 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
2015 Jun 04
2
Testing SHA512-CRYPT password hashes with doveadm pw -t fails
Hi, I use Debian jessie with Dovecot 2.2.13-11. While writing a script for Horde to change the passwords in my passwd file I noticed doveadm pw -t fails for SHA512-CRYPT: # doveadm pw -s SHA1 -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= # doveadm pw -t {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= (verified) # doveadm pw -s SHA512-CRYPT -p test
2018 Mar 11
0
dovecot sha512-crypt database storage
Hello, Yes I am referencing my virtual users table. Other suggestions welcome. Thanks. Dave. On 3/11/18, @lbutlr <kremels at kreme.com> wrote: > On 2018-03-10 (16:48 MST), David Mehler <dave.mehler at gmail.com> wrote: >> >> Thanks. That query doesn't return any parse errors but it does say >> that it can't save the password. > > Are you
2017 Apr 29
2
most secure password scheme
Hello, I have a few questions on password schemes. Is SHA512 the most secure? Is there a difference between SHA512 and SHA512-CRYPT? What about SSHA512 and SSH512-CRYPT? Is there a problem with this sql statement: UPDATE virtual_users SET password=CONCAT(?{SHA256-CRYPT}?, ENCRYPT (?Password Goes Here?, CONCAT(?$5$?, SUBSTRING(SHA(RAND()), -16)))) WHERE user=?user at example.com?; I'm
2014 Dec 06
1
MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
Am 6. Dezember 2014 13:10:58 MEZ, schrieb Reindl Harald <h.reindl at thelounge.net>: > >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)
2017 Apr 30
2
most secure password scheme
Hello, Thanks for the explanation. So should I go with SSHA512 or SHA512-CRYPT? From your explanation i'm interpreting to mean that SHA512-CRYPT also salts. This is for storing in a mysql database. Also, what should the password field length and type be set for? Currently it's varchar(128) Thanks. Dave. On 4/29/17, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On April
2019 Feb 12
6
Using SHA256/512 for SQL based password
I have trying to find how to set the dovecot-sql.conf for using SHA256/512.? I am going to start clean with the stronger format, not migrate from the old MD5.? It seems all I need is: driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=$Postfix_Database_Password default_pass_scheme = SHAxxx-CRYPT # following should all be on one line. password_query =
2018 Oct 20
2
Bug: 'noreplicate' database extra field ingnored
The 'noreplicate' user database field described in the wiki appears to make no difference as to whether an account gets replicated or not. My sql user query returns a 'noreplicate' field and I can confirm that this is getting set using 'doveadm user', however when I add a new account with noreplicate=true it gets replicated regardless. User query: user_query = SELECT
2012 Oct 19
4
still having difficulties with per-user quotas
Hello, I am trying to get per-user quotas working. My thanks to all who have helped so far. To recap I am running Dovecot 2.1 and Mysql where I've got my virtual users. All virtual users are under the system user vmail with a UID and GID of 5000. Looking over the wiki docs I've added a quota table and got the dict service working, I am not having problems with permissions or the login
2014 Dec 06
0
MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
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)
2014 Dec 06
0
MD5-CRYPT/CRAM-MD5 vs SHA512-CRYPT/PLAIN
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