- dovecot - dovecot.org

Re: [Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 17 Jun '07

17 Jun '07

Tere. > %c expands to "secured" or empty. So you could use eg. > passdb pam { > args = %s%c > } > > and create imap, imapsecured, pop3, pop3secured > > More better, so for example user1 can access only imaps, using Yous suggestion, I have to list all users, except user1 in imap, pop3, pop3secured. But it should works also in other way, that by default all users are allowed to use all protocols and then I exclude user1 from imap, pop3, pop3secured. So I tried: passdb pam { args = %s%c } /etc/pam.d/ includes imap, imapsecured, pop3, pop3secured files which includes: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth and only imapsecured has this line: auth required pam_listfile.so item=user sense=deny file=/etc/imapsusers onerr=succeed and /etc/imapsusers includes user1 But now even pop user can't login:(. -- Mart

2 1

[Dovecot] using 'socat' to relay Dovecot SASL's auth socket over TCP?
by snowcrash 17 Jun '07

17 Jun '07

hi, i've been running Exim & Dovecot together on the same box. Exim's been sharing Dovecot/SASL auth info over a local unix socket. works great. i'm now splitting Exim & Dovecot onto two different boxes. iiuc, Dovecot ONLY provides a UNIX (local) socket; *not* a TCP socket for over-the-network access. SUre, I could mount the Dovecot socket's volume over NFS ... but just don't want to go there. i've just discovered, socat - Multipurpose relay http://www.dest-unreach.org/socat/ "Socat is a command line based utility that establishes two bidirectional byte streams and transfers data between them. Because the streams can be constructed from a large set of different types of data sinks and sources (see address types), and because lots of address options may be applied to the streams, socat can be used for many different purposes. It might be one of the tools that one `has already needed'." which, iiuc (?), can bidirectionally bridge the Dovecot unix-socket to a TCP socket that Exim can talk/listen to. reading further, "address types" (http://www.dest-unreach.org/socat/doc/socat.html#ADDRESS_TYPES) seem to include BOTH unix & tcp sockets ... can anyone here comment further on this? known to work? possible? no way? etc etc thanks!

2 1

[Dovecot] index
by Lucas -LandM- 17 Jun '07

17 Jun '07

Hi, First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things? Thank you in advance, Lucas

4 7

Re: [Dovecot] dovecot under attack
by Dani 16 Jun '07

16 Jun '07

A Dissabte 16 Juny 2007 16:10, Jon Slater va escriure: > Hi, > > I’ve posted this before but no one was able to help. I can’t figure > out what they are trying to do, and if I should be concerned. > I am running dovecot version 0.99.14 on Fedora Core 4. It appears > that my dovecot server is under attack. This morning in my system > e-mail I saw this: Hi Jon, just my 5 cents, eventually you can figure out if they are trying to login directly to you imap/pop3 ports or maybe through a webmail? In every case why don't you give a try to a fail2ban program to block automatically login failures through iptables and of course upgrade your dovecot's installation? http://drees76.blogspot.com/2006/08/fail2ban-dovecot-and-brute-force.html greetings, dani

1 0

[Dovecot] 1st DOVECOT installation automatically quitting on login
by Benton Haynes 16 Jun '07

16 Jun '07

Hi there. I have just installed DOVECOT 1.0.1 for the first time. After launching it, I can verify that ps -ax | grep -i dovecot 1052 ?? Ss 0:00.03 /usr/local/dovecot/sbin/dovecot -c /etc/dovecot/dovecot.conf 1053 ?? S 0:00.06 dovecot-auth 1058 p2 R+ 0:00.01 grep -i dovecot ps -ax | grep -i imap 1054 ?? S 0:00.08 imap-login 1055 ?? S 0:00.08 imap-login 1056 ?? S 0:00.08 imap-login 1060 p2 R+ 0:00.01 grep -i imap Then, if I telnet to DOVECOT/IMAP & login telnet 192.168.1.30 143 Trying 192.168.1.30... Connected to 192.168.1.30. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS QUOTA STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] haynes.name IMAP4 server ready x login ben(a)haynes.name benpass x OK Logged in. Connection closed by foreign host. ^^^^^^^^^^^^^^^^^^^ It disconnects automatically. In my dovecot.conf, I currently have defined verbose_ssl = no auth_verbose = no auth_debug = yes mail_debug = no And, in dovecot.log, I get only, dovecot: Jun 15 18:51:10 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.1.30 rip=192.168.1.3resp=<hidden> dovecot: Jun 15 18:51:10 Info: auth(default): passwd-file(user= ben(a)haynes.name,192.168.1.3) lookup: user=ben(a)haynes.namefile=/etc/dovecot/user.file dovecot: Jun 15 18:51:10 Info: auth(default): client out: OK 1 user=ben(a)haynes.name dovecot: Jun 15 18:51:10 Info: auth(default): master in: REQUEST 11054 1 dovecot: Jun 15 18:51:10 Info: auth(default): master out: USER 1 ben(a)haynes.name static uid=500 gid=500 home=/var/mail/imap/haynes.name/accounts/ben nice=10 dovecot: Jun 15 18:51:10 Info: imap-login: Login: user=<user=ben(a)haynes.name>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.30 dovecot: Jun 15 18:51:14 Error: child 1064 (imap) killed with signal 4 Ihaven't been able to figure out why this is happening. Is there some more detailed debugging I should turn on? Any ideas why this is going on? -- Ben

2 4

Re: [Dovecot] dovecot under attack
by Mart Pirita 16 Jun '07

16 Jun '07

Tere. > > > Does anyone know what this is? Or someone I could ask? > > Normal dictionary attack? -- Mart

1 0

Re: [Dovecot] dovecot under attack
by Charles Marcus 16 Jun '07

16 Jun '07

Hi Jon, I cannot help with the specific question, but in my opinion, your first and primary goal should be to get that server updated to 1.0.1 asap... 0.99.x is no longer supported - and *very* dated... Jon Slater wrote: > Hi, > > > > I’ve posted this before but no one was able to help. I can’t figure out > what they are trying to do, and if I should be concerned. > > > > I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my > dovecot server is under attack. This morning in my system e-mail I saw > this: > > > > dovecot: > > Authentication Failures: > > rhost= : 23431 Time(s) > > adm: 33 Time(s) > > bin: 33 Time(s) > > mail: 33 Time(s) > > mysql: 21 Time(s) > > nobody: 15 Time(s) > > news: 14 Time(s) > > operator: 8 Time(s) > > sshd: 2 Time(s) > > Unknown Entries: > > check pass; user unknown: 23431 Time(s) > > > > But, when I check my log files I can’t find an IP address for the attacker. > So, for example, if I search my logs for “operator” I see: > > ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user > pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user > pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user > pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user > pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user > pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user > pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user > pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user > pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > > > I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 > (for IMAP), but I don’t see anything unusual. I also systematically > filtered out everything I knew was okay (ssh, and httpd) . > > > > Does anyone know what this is? Or someone I could ask? > > > > Thanks!!!!!!!!!!!!!!!!!!!! > > > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 > 11:31 AM > >

1 0

[Dovecot] dovecot under attack
by Jon Slater 16 Jun '07

16 Jun '07

Hi, I’ve posted this before but no one was able to help. I can’t figure out what they are trying to do, and if I should be concerned. I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my dovecot server is under attack. This morning in my system e-mail I saw this: dovecot: Authentication Failures: rhost= : 23431 Time(s) adm: 33 Time(s) bin: 33 Time(s) mail: 33 Time(s) mysql: 21 Time(s) nobody: 15 Time(s) news: 14 Time(s) operator: 8 Time(s) sshd: 2 Time(s) Unknown Entries: check pass; user unknown: 23431 Time(s) But, when I check my log files I can’t find an IP address for the attacker. So, for example, if I search my logs for “operator” I see: ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 (for IMAP), but I don’t see anything unusual. I also systematically filtered out everything I knew was okay (ssh, and httpd) . Does anyone know what this is? Or someone I could ask? Thanks!!!!!!!!!!!!!!!!!!!! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 11:31 AM

1 0

[Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 16 Jun '07

16 Jun '07

Hello. Tried search, no luck, sorry, if this is already answered, but I'm still looking a solution using pam_auth how to define in dovecot which user can access which protocol, for example, default is: protocols = pop3 pop3s imap imaps I'd like to use something like this: exclude_using_pop = user1, user2, @group exclude_using_pops = user1, user2, @group exclude_using_imap = user1, user2, @group exclude_using_imaps = user1, user2, @group The idea is security and also preventing imap user by accident logging in using pop3 and downloading (clearing inbox for imap) all inbox. And also some throttling, for example the adjustable time to pause access after failed login etc would be great. -- Mart

2 2

[Dovecot] SHA256 password patch
by Jasper Slits 16 Jun '07

16 Jun '07

Hi, I made a patch against branch-1.0 for SHA256 password hashing support for Dovecot. Courier Authlib supports this hashing scheme and in order to migrate from Courier to Dovecot, I've added SHA256 support to Dovecot. The attached patch is based on BSD licensed code from Olivier Gay (http://www.ouah.org/ogay/sha2/) Changes made by me in Olivier's sha2{.h,.c} code: - Prototype for sha256_transf is added to sha2.h - sha256_get_digest() is added to sha2{.h,.c} - Code for UNROLL_LOOPS is removed - Support for SHA224,SHA384,SHA512 was removed - Functions are renamed to match those in sha1{.h,.c} - SHA256_DIGEST_SIZE is renamed to SHA256_RESULTLEN I can add safe_memset calls if requested. Patch is attached and can also be found at http://www.malochia.nl/dovecot/sha256.patch Kind regards, Jasper diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/auth/password-scheme.c auth/password-scheme.c --- src/auth/password-scheme.c 2007-02-21 13:30:38.756711250 +0100 +++ auth/password-scheme.c 2007-02-21 14:18:49.645380500 +0100 @@ -10,6 +10,7 @@ #include "mycrypt.h" #include "randgen.h" #include "sha1.h" +#include "sha2.h" #include "str.h" #include "password-scheme.h" @@ -153,6 +154,17 @@ return str_c(str); } +static const char *sha256_generate(const char *plaintext, + const char *user __attr_unused__) +{ + unsigned char digest[SHA256_RESULTLEN]; + string_t *str; + sha256_get_digest(plaintext, strlen(plaintext), digest); + str = t_str_new(MAX_BASE64_ENCODED_SIZE(sizeof(digest)+1)); + base64_encode(digest, sizeof(digest), str); + return str_c(str); +} + static const void * password_decode(const char *password, unsigned int result_len) { @@ -196,6 +208,23 @@ return memcmp(sha1_digest, data, SHA1_RESULTLEN) == 0; } +static bool sha256_verify(const char *plaintext, const char *password, + const char *user) +{ + unsigned char sha256_digest[SHA256_RESULTLEN]; + const char *data; + + sha256_get_digest(plaintext, strlen(plaintext), sha256_digest); + + data = password_decode(password, SHA256_RESULTLEN); + if (data == NULL) { + i_error("sha256_verify(%s): Invalid password encoding", user); + return 0; + } + + return memcmp(sha256_digest, data, SHA256_RESULTLEN) == 0; +} + static const char *ssha_generate(const char *plaintext, const char *user __attr_unused__) { @@ -466,6 +495,7 @@ { "MD5-CRYPT", md5_crypt_verify, md5_crypt_generate }, { "SHA", sha1_verify, sha1_generate }, { "SHA1", sha1_verify, sha1_generate }, + { "SHA256", sha256_verify, sha256_generate }, { "SMD5", smd5_verify, smd5_generate }, { "SSHA", ssha_verify, ssha_generate }, { "PLAIN", plain_verify, plain_generate }, diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/Makefile.am lib/Makefile.am --- src/lib/Makefile.am 2007-02-21 13:30:38.792713500 +0100 +++ lib/Makefile.am 2007-02-21 14:21:59.437241750 +0100 @@ -73,6 +73,7 @@ sendfile-util.c \ seq-range-array.c \ sha1.c \ + sha2.c \ str.c \ str-sanitize.c \ strescape.c \ @@ -146,6 +147,7 @@ sendfile-util.h \ seq-range-array.h \ sha1.h \ + sha2.h \ str.h \ str-sanitize.h \ strescape.h \ diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.c lib/sha2.c --- src/lib/sha2.c 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.c 2007-02-23 14:03:46.857739818 +0100 @@ -0,0 +1,257 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#include <string.h> + +#include "sha2.h" + +#define SHFR(x, n) (x >> n) +#define ROTR(x, n) ((x >> n) | (x << ((sizeof(x) << 3) - n))) +#define ROTL(x, n) ((x << n) | (x >> ((sizeof(x) << 3) - n))) +#define CH(x, y, z) ((x & y) ^ (~x & z)) +#define MAJ(x, y, z) ((x & y) ^ (x & z) ^ (y & z)) + +#define SHA256_F1(x) (ROTR(x, 2) ^ ROTR(x, 13) ^ ROTR(x, 22)) +#define SHA256_F2(x) (ROTR(x, 6) ^ ROTR(x, 11) ^ ROTR(x, 25)) +#define SHA256_F3(x) (ROTR(x, 7) ^ ROTR(x, 18) ^ SHFR(x, 3)) +#define SHA256_F4(x) (ROTR(x, 17) ^ ROTR(x, 19) ^ SHFR(x, 10)) + +#define UNPACK32(x, str) \ +{ \ + *((str) + 3) = (uint8) ((x) ); \ + *((str) + 2) = (uint8) ((x) >> 8); \ + *((str) + 1) = (uint8) ((x) >> 16); \ + *((str) + 0) = (uint8) ((x) >> 24); \ +} + +#define PACK32(str, x) \ +{ \ + *(x) = ((uint32) *((str) + 3) ) \ + | ((uint32) *((str) + 2) << 8) \ + | ((uint32) *((str) + 1) << 16) \ + | ((uint32) *((str) + 0) << 24); \ +} + +#define UNPACK64(x, str) \ +{ \ + *((str) + 7) = (uint8) ((x) ); \ + *((str) + 6) = (uint8) ((x) >> 8); \ + *((str) + 5) = (uint8) ((x) >> 16); \ + *((str) + 4) = (uint8) ((x) >> 24); \ + *((str) + 3) = (uint8) ((x) >> 32); \ + *((str) + 2) = (uint8) ((x) >> 40); \ + *((str) + 1) = (uint8) ((x) >> 48); \ + *((str) + 0) = (uint8) ((x) >> 56); \ +} + +#define PACK64(str, x) \ +{ \ + *(x) = ((uint64) *((str) + 7) ) \ + | ((uint64) *((str) + 6) << 8) \ + | ((uint64) *((str) + 5) << 16) \ + | ((uint64) *((str) + 4) << 24) \ + | ((uint64) *((str) + 3) << 32) \ + | ((uint64) *((str) + 2) << 40) \ + | ((uint64) *((str) + 1) << 48) \ + | ((uint64) *((str) + 0) << 56); \ +} + +/* Macros used for loops unrolling */ + +#define SHA256_SCR(i) \ +{ \ + w[i] = SHA256_F4(w[i - 2]) + w[i - 7] \ + + SHA256_F3(w[i - 15]) + w[i - 16]; \ +} + + + +uint32 sha256_h0[8] = + {0x6a09e667, 0xbb67ae85, 0x3c6ef372, 0xa54ff53a, + 0x510e527f, 0x9b05688c, 0x1f83d9ab, 0x5be0cd19}; + + +uint32 sha256_k[64] = + {0x428a2f98, 0x71374491, 0xb5c0fbcf, 0xe9b5dba5, + 0x3956c25b, 0x59f111f1, 0x923f82a4, 0xab1c5ed5, + 0xd807aa98, 0x12835b01, 0x243185be, 0x550c7dc3, + 0x72be5d74, 0x80deb1fe, 0x9bdc06a7, 0xc19bf174, + 0xe49b69c1, 0xefbe4786, 0x0fc19dc6, 0x240ca1cc, + 0x2de92c6f, 0x4a7484aa, 0x5cb0a9dc, 0x76f988da, + 0x983e5152, 0xa831c66d, 0xb00327c8, 0xbf597fc7, + 0xc6e00bf3, 0xd5a79147, 0x06ca6351, 0x14292967, + 0x27b70a85, 0x2e1b2138, 0x4d2c6dfc, 0x53380d13, + 0x650a7354, 0x766a0abb, 0x81c2c92e, 0x92722c85, + 0xa2bfe8a1, 0xa81a664b, 0xc24b8b70, 0xc76c51a3, + 0xd192e819, 0xd6990624, 0xf40e3585, 0x106aa070, + 0x19a4c116, 0x1e376c08, 0x2748774c, 0x34b0bcb5, + 0x391c0cb3, 0x4ed8aa4a, 0x5b9cca4f, 0x682e6ff3, + 0x748f82ee, 0x78a5636f, 0x84c87814, 0x8cc70208, + 0x90befffa, 0xa4506ceb, 0xbef9a3f7, 0xc67178f2}; + + +/* SHA-256 functions */ + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb) +{ + uint32 w[64]; + uint32 wv[8]; + uint32 t1, t2; + const unsigned char *sub_block; + int i,j; + + + for (i = 0; i < (int) block_nb; i++) { + sub_block = message + (i << 6); + + for (j = 0; j < 16; j++) { + PACK32(&sub_block[j << 2], &w[j]); + } + + for (j = 16; j < 64; j++) { + SHA256_SCR(j); + } + + for (j = 0; j < 8; j++) { + wv[j] = ctx->h[j]; + } + + for (j = 0; j < 64; j++) { + t1 = wv[7] + SHA256_F2(wv[4]) + CH(wv[4], wv[5], wv[6]) + + sha256_k[j] + w[j]; + t2 = SHA256_F1(wv[0]) + MAJ(wv[0], wv[1], wv[2]); + wv[7] = wv[6]; + wv[6] = wv[5]; + wv[5] = wv[4]; + wv[4] = wv[3] + t1; + wv[3] = wv[2]; + wv[2] = wv[1]; + wv[1] = wv[0]; + wv[0] = t1 + t2; + } + + for (j = 0; j < 8; j++) { + ctx->h[j] += wv[j]; + } + } +} + +void sha256(const unsigned char *message, unsigned int len, unsigned char *digest) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, message, len); + sha256_result(&ctx, digest); +} + +void sha256_init(sha256_ctx *ctx) +{ + int i; + for (i = 0; i < 8; i++) { + ctx->h[i] = sha256_h0[i]; + } + + ctx->len = 0; + ctx->tot_len = 0; +} + +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len) +{ + unsigned int block_nb; + unsigned int new_len, rem_len, tmp_len; + const unsigned char *shifted_message; + + tmp_len = SHA256_BLOCK_SIZE - ctx->len; + rem_len = len < tmp_len ? len : tmp_len; + + memcpy(&ctx->block[ctx->len], message, rem_len); + + if (ctx->len + len < SHA256_BLOCK_SIZE) { + ctx->len += len; + return; + } + + new_len = len - rem_len; + block_nb = new_len / SHA256_BLOCK_SIZE; + + shifted_message = message + rem_len; + + sha256_transf(ctx, ctx->block, 1); + sha256_transf(ctx, shifted_message, block_nb); + + rem_len = new_len % SHA256_BLOCK_SIZE; + + memcpy(ctx->block, &shifted_message[block_nb << 6], + rem_len); + + ctx->len = rem_len; + ctx->tot_len += (block_nb + 1) << 6; +} + +void sha256_result(sha256_ctx *ctx, unsigned char *digest) +{ + unsigned int block_nb; + unsigned int pm_len; + unsigned int len_b; + int i; + + block_nb = (1 + ((SHA256_BLOCK_SIZE - 9) + < (ctx->len % SHA256_BLOCK_SIZE))); + + len_b = (ctx->tot_len + ctx->len) << 3; + pm_len = block_nb << 6; + + memset(ctx->block + ctx->len, 0, pm_len - ctx->len); + ctx->block[ctx->len] = 0x80; + UNPACK32(len_b, ctx->block + pm_len - 4); + + sha256_transf(ctx, ctx->block, block_nb); + + for (i = 0 ; i < 8; i++) { + UNPACK32(ctx->h[i], &digest[i << 2]); + } +} + +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, data, size); + sha256_result(&ctx, result); +} + diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.h lib/sha2.h --- src/lib/sha2.h 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.h 2007-02-23 14:22:32.952116316 +0100 @@ -0,0 +1,72 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#ifndef SHA2_H +#define SHA2_H + +#define SHA256_RESULTLEN ( 256 / 8) + +#define SHA256_BLOCK_SIZE ( 512 / 8) + +#ifndef SHA2_TYPES +#define SHA2_TYPES +typedef unsigned char uint8; +typedef unsigned int uint32; +typedef unsigned long long uint64; +#endif + + +typedef struct { + unsigned int tot_len; + unsigned int len; + unsigned char block[2 * SHA256_BLOCK_SIZE]; + uint32 h[8]; +} sha256_ctx; + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb); + + +void sha256_init(sha256_ctx * ctx); +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len); +void sha256_result(sha256_ctx *ctx, unsigned char *digest); +void sha256(const unsigned char *message, unsigned int len, + unsigned char *digest); +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]); + + + +#endif /* !SHA2_H */ +

3 2