Bug 90749

Summary:	self-cert.sh creates key in the wrong directory for jabberd 2.0
Product:	Gentoo Linux	Reporter:	Daniel Guido <dguido>
Component:	New packages	Assignee:	Wolfram Schlich (RETIRED) <wschlich>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Daniel Guido 2005-04-28 11:30:24 UTC

It appears that in the new, masked jabberd 2.0 builds the config directory has changed from /etc/jabber/ to /etc/jabberd/ .  The self-cert.sh script that is included with jabberd 2.0 still creates a self-signed certificate in the old config directory.

Reproducible: Always
Steps to Reproduce:
1. emerge '>=jabberd-2' (or something like that)
2. /etc/jabberd/self-cert.sh
3. cert created in /etc/jabber/gentoo.pem



Expected Results:  
self-cert.sh should have created gentoo.pem in /etc/jabberd/gentoo.pem

Comment 1 Daniel Guido 2005-04-28 11:42:22 UTC

The jabber docs also say the file should be

chown root:jabber /etc/jabberd/gentoo.pem    
chmod 640 /etc/jabberd/gentoo.pem

self-cert.sh doesn't do this

http://jabberd.jabberstudio.org/2/docs/app_sslkey.html

Comment 2 Wolfram Schlich (RETIRED) gentoo-dev

2005-04-28 12:59:49 UTC

Taking care... also updating jabberd to 2.0.8 (2.0s8). Stay tuned.

Comment 3 Wolfram Schlich (RETIRED) gentoo-dev

2005-04-28 14:29:30 UTC

Added self-cert.jabberd-2.sh and fixed jabberd-2.0.8.ebuild.