547488 – mail-filter/dkimproxy: Init file for dkimproxy.out requires expose DKIM's private key for nobody

Bug 547488 - mail-filter/dkimproxy: Init file for dkimproxy.out requires expose DKIM's private key for nobody

Summary: mail-filter/dkimproxy: Init file for dkimproxy.out requires expose DKIM's pri...

Status:	UNCONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Jason A. Donenfeld

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-04-23 14:53 UTC by Maxim Britov
Modified:	2020-06-10 15:13 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

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 Maxim Britov 2015-04-23 14:53:24 UTC

dkimproxy.out using for DKIM sign header with private key.

From /etc/dkimproxy_out.conf:
# specify location of the private key
keyfile   /etc/ssl/dkimproxy/private.key

From init.d/dkimproxy.out:
start-stop-daemon --start --exec /usr/bin/dkimproxy.out --pidfile /var/run/dkimproxy.out.pid -- --conf_file /etc/dkimproxy_out.conf --daemonize --group=nobody --user=nobody

With this command dkimproxy.out will run as nobody:nobody and I should expose private key for this user.

Is it right?

In ebuild pre 1.4 user was dkfilter, with 1.4 it changed to nobody.


Reproducible: Always