similar to: doveadm pw with SHA512-CRYPT won't roundtrip

Displaying 20 results from an estimated 90 matches similar to: "doveadm pw with SHA512-CRYPT won't roundtrip"

2012 Jul 28
0
[LLVMdev] Roundtrip clang -> llc -> clang fails
On Fri, Jul 27, 2012 at 3:36 PM, Kai <kai at redstar.de> wrote: > Hi! > > I am not sure if this is a bug or not. > > I have the following non-sense C module exc_alloc.c: > > #include <windows.h> > > void *AllocMem() { > HANDLE heap = GetProcessHeap(); > void *p = HeapAlloc(heap, HEAP_GENERATE_EXCEPTIONS | > HEAP_ZERO_MEMORY,
2012 Jul 27
3
[LLVMdev] Roundtrip clang -> llc -> clang fails
Hi! I am not sure if this is a bug or not. I have the following non-sense C module exc_alloc.c: #include <windows.h> void *AllocMem() { HANDLE heap = GetProcessHeap(); void *p = HeapAlloc(heap, HEAP_GENERATE_EXCEPTIONS | HEAP_ZERO_MEMORY, 16*1024*1014*1024); return p; } If I execute the following commands clang -S -emit-llvm -o exc_alloc.ll exc_alloc.c llc -filetype=asm
2005 Apr 21
2
[Bug 1023] Add support for dhgex-sha512
http://bugzilla.mindrot.org/show_bug.cgi?id=1023 Summary: Add support for dhgex-sha512 Product: Portable OpenSSH Version: -current Platform: All OS/Version: OpenBSD Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: djm at
2011 Feb 01
1
Cannot authenticate with new Red Hat/Fedora SHA512
RHEL6 and Fedora 14 use an improved password algorithm of SHA512 on a brand new install of the OS (:$6$ in shadow file). cat /etc/shadow user1:$6$<salt>$<password>:15006:0:99999:7::: I cannot get dovecot to authenticate. I've search for a way to change the default algorithm in dovecot and found you should use CRYPT but I don't know what to put in the
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 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
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
2015 Jun 04
0
Testing SHA512-CRYPT password hashes with doveadm pw -t fails
doveadm pw -t '{SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811' -p test You have $ in the password, see man-page of shell ... Am 04.06.2015 um 05:29 schrieb Felix Zielcke: > oveadm pw -t {SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811 -p
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 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
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
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.
2024 May 09
1
[Bug 3689] New: Implicit function declarations: SHA256, SHA512 with -DWITH_XMSS
https://bugzilla.mindrot.org/show_bug.cgi?id=3689 Bug ID: 3689 Summary: Implicit function declarations: SHA256, SHA512 with -DWITH_XMSS Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd
2018 Mar 10
3
dovecot sha512-crypt database storage
Hello, I've got dovecot authenticating to a MySQL database. I've got a field varchar(128) called password. Whenever I create a password I use doveadm pw as in: doveadm pw -s sha512-crypt now i'd like to get MySQL to make a dovecot-specific password. My goal is to eventually have roundcube's password plugin working with this MySQL database to change the password. Thanks. Dave.
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)
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
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 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
2018 Feb 07
0
retpoline mitigation and 6.0
On Wed, 2018-02-07 at 10:11 -0800, Guenter Roeck wrote: > On Wed, Feb 07, 2018 at 10:49:25AM +0000, David Woodhouse wrote: > > Hm, please could we also have the %V asm constraint modifier? That > > allows us to emit calls to the thunks from inline asm using the > > register that the compiler chose for us: > > > >  asm volatile ("call