Bug 475616 - [openSUSE:Tools:Devel/obs-signd] obssignd init script does not work during boot
Summary: [openSUSE:Tools:Devel/obs-signd] obssignd init script does not work during boot
Status: CONFIRMED
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other openSUSE 11.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 13:07 UTC by Dominique Leuenberger
Modified: 2010-01-20 10:46 UTC (History)
2 users (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Leuenberger 2009-02-13 13:07:24 UTC 
the rcobssignd init script has a little flaw if used in an automatic manner.

signd starts with a not yet initialized HOME var (empty) and all gpg child processes can't find the keypairs for the user.

If you login as root and rcobssignd start, then everything works and the ENVVAR HOME is set to /root (obvious).

A 'simple' fix is to add
export HOME=/root
to /etc/init.d/obssignd
Comment 1 Dominique Leuenberger 2009-02-13 13:09:03 UTC 
forgot to mention: at the moment I have:

dominique@messiah:/etc/init.d> rpm -q obs-signd
obs-signd-1.6.0.6258S-1.1

from openSUSE:Tools:Devel
Comment 2 Carsten Hoeger 2009-02-17 08:53:46 UTC 
I have the same problem on SLE10.

rpm -q obs-signd
obs-signd-1.5.rc1.5898-1.1
Comment 3 Thomas Schmidt 2010-01-19 18:54:36 UTC 
Adrian, shall we include this for 1.7?
Comment 4 Adrian Schröter 2010-01-20 10:46:23 UTC 
actually we should not re-use the root users keyring at all IMHO.

Need to check that, but yes, we should solve this for 1.7.