Ubuntu
haveged package

haveged in a container can't output anything to stdout/stderr

Bug #1894905 reported by Dan Streetman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
haveged (Ubuntu)
Fix Released
Medium
Dan Streetman
Xenial
New
Low
Unassigned
Bionic
New
Low
Unassigned
Focal
New
Low
Unassigned
Groovy
Fix Released
Medium
Dan Streetman

Bug Description

[impact]

haveged is unable to output anything at all to stdout or stderr due to its apparmor profile

[test case]

in a container, run haveged with any parameters, e.g.:

$ haveged -h
$

[regression potential]

any regression would likely involve haveged being unable to output to stdout/stderr, or incorrectly losing or gaining apparmor permissions

[scope]

this is needed for all releases

See original description
Dan Streetman (ddstreet)
description: updated
Changed in haveged (Ubuntu Groovy):
assignee: nobody → Dan Streetman (ddstreet)
Changed in haveged (Ubuntu Focal):
assignee: nobody → Dan Streetman (ddstreet)
Changed in haveged (Ubuntu Bionic):
assignee: nobody → Dan Streetman (ddstreet)
Changed in haveged (Ubuntu Xenial):
assignee: nobody → Dan Streetman (ddstreet)
Changed in haveged (Ubuntu Groovy):
importance: Undecided → Medium
Changed in haveged (Ubuntu Focal):
importance: Undecided → Medium
Changed in haveged (Ubuntu Xenial):
importance: Undecided → Medium
status: New → In Progress
Changed in haveged (Ubuntu Bionic):
status: New → In Progress
importance: Undecided → Medium
Changed in haveged (Ubuntu Focal):
status: New → In Progress
Changed in haveged (Ubuntu Groovy):
status: New → In Progress
description: updated
Revision history for this message
Dan Streetman (ddstreet) wrote :

not sure if this matters enough to bother sru'ing...haveged is rarely run directly, especially inside a container

summary: - haveged can't output anything to stdout/stderr
+ haveged in a container can't output anything to stdout/stderr
description: updated
description: updated
Changed in haveged (Ubuntu Focal):
status: In Progress → New
Changed in haveged (Ubuntu Bionic):
status: In Progress → New
Changed in haveged (Ubuntu Xenial):
status: In Progress → New
Changed in haveged (Ubuntu Focal):
assignee: Dan Streetman (ddstreet) → nobody
Changed in haveged (Ubuntu Bionic):
assignee: Dan Streetman (ddstreet) → nobody
Changed in haveged (Ubuntu Xenial):
assignee: Dan Streetman (ddstreet) → nobody
importance: Medium → Low
Changed in haveged (Ubuntu Focal):
importance: Medium → Low
Changed in haveged (Ubuntu Bionic):
importance: Medium → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package haveged - 1.9.8-4ubuntu3

---------------
haveged (1.9.8-4ubuntu3) groovy; urgency=medium

  * d/p/lp1894865-Fixed-https-github.com-jirka-h-haveged-issues-29.patch:
    - Fix segfault when using --Foreground param (LP: #1894809)
  * d/p/lp1894877-don-t-fail-completely-if-we-can-t-set-write-wakeup-w.patch:
    - Don't fail if -w is used in a container (LP: #1894877)
  * d/haveged.default:
    - remove -w param by default
  * d/apparmor-profile:
    - allow haveged to actually output to stdout/stderr (LP: #1894905)
    - allow haveged to bind to unix sockets
  * d/haveged.service:
    - add ConditionVirtualization=!container
  * d/t/control, d/t/dieharder, d/t/run-tests, d/t/check-service:
    - restore dieharder test, but with limited tests
    - verify haveged service is active
    - fix run-tests to check installed haveged
    - skip dieharder tests on s390x, where dieharder is broken

 -- Dan Streetman <email address hidden> Fri, 11 Sep 2020 13:40:44 -0400

Changed in haveged (Ubuntu Groovy):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.