- dovecot - dovecot.org

[Dovecot] lstats on all files in Maildir when opening an e-mail.
by Tan Shao Yi 27 Feb '07

27 Feb '07

Hi, I'm running RC19 on a Solaris 10 SPARC box. It seems that whenever I open an e-mail in any folder via IMAP, dovecot appears to scan every other folder in the Maildir. A truss reveals that it is lstat-ing every e-mail in every directory. I'm sorry I am sending only a fragment of the truss, it's really too long... but is this behaviour expected? Cheers, Tan Shao Yi lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170337156.M209211P18431V025055F0I0000DAF0_0.recess1,S=2596", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170337594.M159985P18549V025055F0I0001891B_0.recess1,S=4111", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170338379.M564254P18933V025055F0I000196A3_0.recess1,S=3630", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170344035.M859029P24106V025055F0I000198E4_0.recess1,S=4254", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170344816.M69242P24829V025055F0I000199CB_0.recess1,S=3810", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170347789.M408186P27905V025055F0I00019A8F_0.recess1,S=3922", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170378895.M589722P25748V025055F0I00019279_0.recess1,S=2782", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170380726.M524353P29456V025055F0I0001AEE1_0.recess1,S=3619", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/new/1170381420.M702545P517V025055F0I0001B208_0.recess1,S=3028", 0xFFBFF040) = 0 getdents64(8, 0xFEE72000, 8192) = 0 close(8) = 0 lstat64("/var/qmail/maildirs/AA/AA/test(a)pacific.net.sg/Maildir/.qmail/maildirfolder", 0xFFBFF148) = 0 lstat64("/var/qmail/maildirs/AA/AA/test(a)pacific.net.sg/Maildir/.qmail/cur", 0xFFBFF148) = 0 openat(-3041965, "/var/qmail/maildirs/AA/AA/test(a)pacific.net.sg/Maildir/.qmail/cur", O_RDONLY|O_NDELAY|O_LARGEFILE) = 8 fcntl(8, F_SETFD, 0x00000001) = 0 fstat64(8, 0xFFBFEEE8) = 0 getdents64(8, 0xFEE72000, 8192) = 1088 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/cur/1169092926.M656431P6118V04010002I000023E9_0.recess1,S=4701:2,S", 0xFFBFF040) = 0 lstat64("/var/qmail/maildirs/AA/AA/test@pacific.net.sg/Maildir/.qmail/cur/1168983168.M76366P8906V04010002I000027AB_0.recess1,S=2345:2,S", 0xFFBFF040) = 0

3 6

Re: [Dovecot] pid stamp on log entries?
by Bill Boebel 27 Feb '07

27 Feb '07

On Mon, February 26, 2007 2:40 pm, bhayden(a)umn.edu said: > Hi folks. Is there a way to modify the log stamp to include pid as well as > time? Take a look at http://wiki.dovecot.org/Variables %p = pid I use: mail_log_prefix = "%Us(%u)(%p): " Syslog adds the timestamp though. Bill

1 0

[Dovecot] pid stamp on log entries?
by bhayden＠umn.edu 26 Feb '07

26 Feb '07

Hi folks. Is there a way to modify the log stamp to include pid as well as time? Preferably for all logging, but at least for imap and pop. I took a look at the mail-login plugin, but that seems to associate operations with uid, still no pid. Am I missing something? Thanks for any info, -Brian U of Minnesota Internet Services

1 0

[Dovecot] dovecot and ldap
by Antonis Faragitakis 26 Feb '07

26 Feb '07

hi im trying to install dovecot and use ldap as the backend and i get the following error srv:/root# telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS AUTH=PLAIN] Dovecot ready. 1 login b.tapratzis passwordhere 1 NO Authentication failed. tail -f /var/log/dovecot.info dovecot: Feb 26 18:14:21 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGIudGFwcmF0emlzADM2Yi50YXByIw== dovecot: Feb 26 18:14:21 Info: auth(default): ldap(b.tapratzisb.tapratzis,127.0.0.1): bind search: base=ou=Company,ou=Ath,dc=company,dc=gr filter=(&(objectClass=posixAccount)(uid=b.tapratzisb.tapratzis)) dovecot: Feb 26 18:14:21 Info: auth(default): ldap(b.tapratzisb.tapratzis,127.0.0.1): unknown user dovecot: Feb 26 18:14:21 Info: auth(default): client out: FAIL 1 user=b.tapratzisb.tapratzis i cant understand why is place 2 times the username in the uid= for search. my dovecot.conf: passdb ldap { args = /etc/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot-ldap.conf } my dovecot-ldap.conf: base = ou=Company,ou=Ath,dc=company,dc=gr deref = never scope = subtree user_attrs = uid,homeDirectory,,uid,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid where it my be the fault? Thanks Atn

1 0

[Dovecot] Quota stored in LDAP
by Venilton Junior 26 Feb '07

26 Feb '07

Hie folks, Does anyone have any experiences using dovecot + per user quota + ldap? I've configured my settings as this example: # quotaStorage must be in the format mentioned above # For example: dirsize:storage=10240 user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota But, Dovecot isn't creating maildirsize file. Any guesses? PS: I've already instaled 1.0rc24 Venilton C. Junior HPS Sercompe Computadores Ltda. Office: +55 47 3431-9700 Fax: +55 47 3431-9747 Mobile: +55 47 9653-5872 www.sercompe.com.br <http://www.sercompe.com.br/>

2 1

[Dovecot] Bigcrypt password patch
by Philipp Kolmann 26 Feb '07

26 Feb '07

Hi, we are currently in the progress of switching an HPUX mailserver to linux and dovecot. The only issue so far is, that HPUX has bigcrypt for passwords > 8 chars. Bigcrypt uses standard libc crypt for every block of 8 chars. The linux pam modules have a bigcrypt.c file which can be used for dovecot as well to authenticate crypt and bigcrypt passwords. I have used the pam bigcrypt.c code to patch the mycrypt.c dovecot file. Maybe you could add this path (against branch_1_0 cvs). thanks Philipp Kolmann -- If you have problems in Windows: REBOOT If you have problems in Linux: BE ROOT

2 1

[Dovecot] problem with NFS from Microsoft Windows Services for Unix
by Arnaud Grandville 26 Feb '07

26 Feb '07

Hi all, I'm using dovecot 1.0 RC24 compiled form source on a OpenBSD 4.0, I use IMAP service with maildir storage and my mail client is Outlook 2003. If the root of the user maildir stay on the BSD filesystem everything is right. If the root of the maildir is mount on an NFS drive on Microsoft Windows 2003 server, I always have the same error when I try to move mail (under Outlook) form my Pop3 account to my Imap account : dovecot: Feb 24 21:41:13 Error: IMAP(arno): rename(/var/mail/arno/Maildir/tmp/1172353272.P7684Q1.mail.domaine.fr, /var/mail/arno/Maildir/cur/1172353272.P7684Q1.mail.domaine.fr:2,S) failed: Input/output error As you see, the name of the file gets an extra string ":2,S" and that's why the new filename can't be created. what's wrong? thanks --- dovecot.conf ------------------ base_dir: /var/run/dovecot/ log_path: /dev/stderr protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_gid: 0 mail_location: maildir:~/Maildir mmap_disable: yes lock_method: dotlock auth default: passdb: driver: passwd-file args: /etc/master.passwd userdb: driver: passwd

4 5

[Dovecot] Updated SHA256 patch
by Jasper Slits 25 Feb '07

25 Feb '07

Hi, This is the updated version of the SHA256 password hashing patch I submitted earlier to this list. I changed it, based on the suggestions by Andrey Panin (AP). Also some other parts have been changed, summary as follows: [sha2.h] - typedef of context dropped for consistency (AP) - removed ifndef SHA2_TYPES part (AP) - removed sha256() prototype [sha2.c] - added lib.h and safe_memset.h includes - added static const to sha256_h0[8] and sha256_k[64] (AP) - replaced memset with safe_memset - used standard types from stdint.h: (AP) - uint32 -> uint32_t - uint8 -> uint8_t - removed strings.h include - removed PACK64 and UNPACK64 (defined but not used) The updated patch 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 --exclude=CVS dv_bas/src/auth/password-scheme.c src/auth/password-scheme.c --- dv_bas/src/auth/password-scheme.c 2007-02-25 02:13:29.697424750 +0100 +++ src/auth/password-scheme.c 2007-02-23 14:34:23.940550315 +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 --exclude=CVS dv_bas/src/lib/sha2.c src/lib/sha2.c --- dv_bas/src/lib/sha2.c 1970-01-01 01:00:00.000000000 +0100 +++ src/lib/sha2.c 2007-02-25 01:53:03.876815750 +0100 @@ -0,0 +1,226 @@ +/* + * 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 "lib.h" + +#include "sha2.h" +#include "safe-memset.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_t) ((x) ); \ + *((str) + 2) = (uint8_t) ((x) >> 8); \ + *((str) + 1) = (uint8_t) ((x) >> 16); \ + *((str) + 0) = (uint8_t) ((x) >> 24); \ +} + +#define PACK32(str, x) \ +{ \ + *(x) = ((uint32_t) *((str) + 3) ) \ + | ((uint32_t) *((str) + 2) << 8) \ + | ((uint32_t) *((str) + 1) << 16) \ + | ((uint32_t) *((str) + 0) << 24); \ +} + + + +#define SHA256_SCR(i) \ +{ \ + w[i] = SHA256_F4(w[i - 2]) + w[i - 7] \ + + SHA256_F3(w[i - 15]) + w[i - 16]; \ +} + + + +static const uint32_t sha256_h0[8] = + {0x6a09e667, 0xbb67ae85, 0x3c6ef372, 0xa54ff53a, + 0x510e527f, 0x9b05688c, 0x1f83d9ab, 0x5be0cd19}; + + +static const uint32_t 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(struct sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb) +{ + uint32_t w[64]; + uint32_t wv[8]; + uint32_t 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_init(struct 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(struct 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(struct 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; + + safe_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]) +{ + struct 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 --exclude=CVS dv_bas/src/lib/sha2.h src/lib/sha2.h --- dv_bas/src/lib/sha2.h 1970-01-01 01:00:00.000000000 +0100 +++ src/lib/sha2.h 2007-02-24 19:45:48.447687500 +0100 @@ -0,0 +1,71 @@ +/* + * 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 +*/ + +struct sha256_ctx { + unsigned int tot_len; + unsigned int len; + unsigned char block[2 * SHA256_BLOCK_SIZE]; + uint32_t h[8]; +}; + +void sha256_transf(struct sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb); + + +void sha256_init(struct sha256_ctx * ctx); +void sha256_loop(struct sha256_ctx *ctx, const unsigned char *message, + unsigned int len); +void sha256_result(struct sha256_ctx *ctx, unsigned char *digest); +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]); + + + +#endif /* !SHA2_H */ +

1 0

[Dovecot] openssl mkcert problem
by Zbigniew Szalbot 24 Feb '07

24 Feb '07

Hello, Can someone point me to what I should do to install the missing files? I am trying to generate self-signed certificates using mkcert.sh but I get the following error: $ /usr/local/share/dovecot/mkcert.sh error on line -1 of ./dovecot-openssl.cnf} 6213:error:02001002:system library:fopen:No such file or directory:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bio/bss_file.c:104:fopen('./dovecot-openssl.cnf}','rb') 6213:error:2006D080:BIO routines:BIO_new_file:no such file:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bio/bss_file.c:107: 6213:error:0E064072:configuration file routines:CONF_load:no such file:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/conf/conf_def.c:197: I am using OpenSSL 0.9.7e-p1 25 Oct 2004. Many thanks for your help in advance! -- Zbigniew Szalbot

2 1

[Dovecot] Dovecot on Solaris x86?
by Tim Skirvin 24 Feb '07

24 Feb '07

I'm trying to get dovecot working on Solaris x86. I've got it working just fine on RH Desktop 4; and while I have a built, limping version on solx86, it's not actually usable except from other solx86 systems. Basic details: Version 1.0rc23 OS Solaris x86 (64 bit) CPU Opteron Filesystem NFS (but it's not getting that far) The general problem is apparently SSL-related. I can connect properly from another Solaris x86 machine, using either mutt or straight openssl; but when I try mutt from a Solaris or Linux machine, I get the error "SSL failed: I/O error" and it fails, and when I use openssl from a Linux machine, I get something like this: victor ~> stelnet xxxxxxxx.ks.uiuc.edu 993 + openssl s_client -connect xxxxxxxx.ks.uiuc.edu:993 -verify -debug verify depth is 0 CONNECTED(00000003) depth=0 /C=US/ST=Illinois/L=Urbana/O=UIUC/OU=[...] verify error:num=18:self signed certificate verify return:1 depth=0 /C=US/ST=Illinois/L=Urbana/O=UIUC/OU=[...] verify return:1 24748:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:226: Annoyingly, the same command run from a Solaris machine connects, even though mutt doesn't. (I'm using 'mutt -f imaps://xxxx/', which I know works elsewhere; and the Linux mutt is the system default one, so I don't suspect that it is the source of the problem.) The logs have been remarkably un-useful: dovecot: Feb 21 09:41:21 Info: imap-login: Disconnected: rip=[...], lip=[...] TLS handshake The software was built in all cases with: ./configure --prefix=/usr/local/encap/dovecot-1.0rc23.1 I've tried with both Sun's native cc and gcc compilers. I have also tried building on SPARC Solaris with the native cc compiler, to the same (negative) effect. (I used to have v0.99.14 running just fine on this SPARC machine, so this worries me... but I only checked it just now as an after-thought.) Any suggestions? - Tim Skirvin (tskirvin(a)ks.uiuc.edu) -- Theoretical and Computational http://www.ks.uiuc.edu/~tskirvin/ Biophysics, Beckman Institute, UIUC Senior Systems Administrator

4 9