On Monday 03 July 2006 12:38, Ingo Claro wrote:
> select(1, [0], NULL, NULL, {1177, 147000}) = 1 (in [0], left {1172,
> 868000}) read(0, "starttls\r\n", 1024) = 10
> brk(0) = 0x8407000
> brk(0x8428000) = 0x8428000
> open("control/clientca.pem", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> open("/dev/urandom", O_RDONLY) = 3
> read(3, "\3364\355\233p\277\303\240\320\350|\24H\254[\0%k\22\251"...,
> 32) = 32
> open("control/servercert.pem", O_RDONLY) = 4> looking it crashes while reading servercert.pem, so here it goes too. > The strange thing, as I mentioned earlier, is that with vpopmail without > mysql it works fine. strange. I would say try doing a 'make clean' on your qmail source directory, recompiling and reinstalling with new binaries and give that a try. If that doesn't work... I don't know :( > lrwxrwxrwx 1 root root 33 Jun 28 03:38 clientcert.pem -> > /var/qmail/control/servercert.pem > -rw-r----- 1 vpopmail qmail 1937 Jun 28 03:38 servercert.pem > -----BEGIN RSA PRIVATE KEY----- eek! don't ever post this publicly! You should go right now and generate a new keypair and destroy this one. Otherwise people may be able to use this to forge communications from your company. Private keys are exactly what they sound: private. The public key is fine to distribute publicly, use in marketing material, print 1 million copies of it and post them throughout moscow, whatever.. but the private key *must* remain private. On a lighter note, providing it did help with one thing.. the private key is not encrypted, so it's not bombing out while trying to find a passphrase ;) -Jeremy -- Jeremy Kitchen ++ [EMAIL PROTECTED] http://www.pirate-party.us/ -- defend your rights
pgpmwo2kA9wCb.pgp
Description: PGP signature
