I've just installed dovecot on my FC5 box. I tweaked the dovecot-openssl.cnf and attempted to recreate the cert but get the errors below. I see older postings about this problem on FC2. help?
- e
./mkcert.sh
/etc/ssl/certs directory doesn't exist /etc/ssl/private directory doesn't exist error on line -1 of dovecot-openssl.cnf 2810:error:02001002:system library:fopen:No such file or directory:bss_file.c:122:fopen('dovecot-openssl.cnf','rb') 2810:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:125: 2810:error:0E078072:configuration file routines:DEF_LOAD:no such file:conf_def.c:197:
Erick Calder napisał(a):
I've just installed dovecot on my FC5 box. I tweaked the dovecot-openssl.cnf and attempted to recreate the cert but get the errors below. I see older postings about this problem on FC2. help?
- e
./mkcert.sh
/etc/ssl/certs directory doesn't exist /etc/ssl/private directory doesn't exist error on line -1 of dovecot-openssl.cnf 2810:error:02001002:system library:fopen:No such file or directory:bss_file.c:122:fopen('dovecot-openssl.cnf','rb') 2810:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:125: 2810:error:0E078072:configuration file routines:DEF_LOAD:no such file:conf_def.c:197:
make directory
/etc/ssl/certs and /etc/ssl/certs
PJ
INTERIA.PL dla kobiet... >>> http://link.interia.pl/f193b
Erick Calder wrote:
I've just installed dovecot on my FC5 box. I tweaked the dovecot-openssl.cnf and attempted to recreate the cert but get the errors below. I see older postings about this problem on FC2. help?
- e
./mkcert.sh
/etc/ssl/certs directory doesn't exist /etc/ssl/private directory doesn't exist error on line -1 of dovecot-openssl.cnf 2810:error:02001002:system library:fopen:No such file or directory:bss_file.c:122:fopen('dovecot-openssl.cnf','rb') 2810:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:125: 2810:error:0E078072:configuration file routines:DEF_LOAD:no such file:conf_def.c:197:
I updated the wiki with info regarding this. See http://wiki.dovecot.org/QuestionsAndAnswers#head-acc50b0e2161f91f2ed164df243...
The parts in parenthesis are what I did for Fedora Core 5. Mark Nienberg
From: Mark Nienberg gmane@tippingmar.com Erick Calder wrote:
I've just installed dovecot on my FC5 box. I tweaked the dovecot-openssl.cnf and attempted to recreate the cert but get the errors below. I see older postings about this problem on FC2. help?
I updated the wiki with info regarding this. See http://wiki.dovecot.org/QuestionsAndAnswers#head-acc50b0e2161f91f2ed164df243... 8e056040603
The parts in parenthesis are what I did for Fedora Core 5.
thanks much. that worked. I wanted to suggest that a better patch for that script might be one that picks up the path for $OPENSSLCONFIG from the RPM. it could be done sort of like this:
OPENSSL=${OPENSSL-openssl}
# test for presence of RPM rpm --help > /dev/null 2>&1 [[ $? = 0 ]] && { OPENSSLCONFIG=$(rpm -ql dovecot |grep cnf) SSLDIR=${OPENSSLCONFIG%/*} }
On 2006-06-07 22:50:55 -0700, Erick Calder wrote:
OPENSSL=${OPENSSL-openssl}
# test for presence of RPM rpm --help > /dev/null 2>&1 [[ $? = 0 ]] && { OPENSSLCONFIG=$(rpm -ql dovecot |grep cnf) SSLDIR=${OPENSSLCONFIG%/*} }
that would badly fail on all other systems, which are supported by dovecot but that dont ship with rpm.
if some of your parse dont match the assumptions you can easily overwrite them with
SSLDIR=/usr/share/ssl/etc ./mkcert.sh
you could file a bug report at redhat to fix the defaults inside the script. so they match the distro a bit better
darix
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
From: Marcus Rueckert rueckert@informatik.uni-rostock.de that would badly fail on all other systems, which are supported by dovecot but that dont ship with rpm.
my code was incomplete. the failures would be silent and enough to determine whether we can fetch the directory from rpm (if it exists) and "else" part would contain the original code
if some of your parse dont match the assumptions you can easily overwrite them with
SSLDIR=/usr/share/ssl/etc ./mkcert.sh
true, but why should I have to know that?
you could file a bug report at redhat to fix the defaults inside the script. so they match the distro a bit better
quite. that is what I need to do. thx!
On 2006-06-09 21:16:56 -0700, Erick Calder wrote:
if some of your parse dont match the assumptions you can easily overwrite them with
SSLDIR=/usr/share/ssl/etc ./mkcert.sh
true, but why should I have to know that?
reading the shell script :) and it is a common behavior to pass temporary environment variables to programs that way.
you could file a bug report at redhat to fix the defaults inside the script. so they match the distro a bit better
quite. that is what I need to do. thx!
welcome
darix
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
participants (4)
-
Erick Calder
-
Marcus Rueckert
-
Mark Nienberg
-
pitun