[MIR] ipmitool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ipmitool (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
An MIR was originally attempted a few years ago (see LP: #1576812) but was denied as the package was not yet in a good enough state. In that time ipmitool has become a more reasonable candidate for main inclusion.
ipmitool is used often by MAAS and has shown up in component mismatches for a few years. It is also used often for high availability systems.
[Availability]
The package ipmitool is already in Ubuntu universe.
The package ipmitool builds for the architectures it is designed to work on.
It currently builds and works for architectures: any
Link to package https:/
[Rationale]
- The package ipmitool will generally be useful for a large part of our
user base since it is widely used in systems management and in various
HA components. It is also suggested by tools such as cluster-glue which
is in main
[Security]
- Based on CVE trackers ipmitool had 2 relevant security issues
- CVE-2020-5208 (https:/
1.8.19 upstream and in a set of 6 patches in 1.8.18-10.1 Debian/Ubuntu
- CVE-2011-4339 (https:/
in 1.8.11-5
- The binary ipmievd is installed to /usr/sbin. It has a fairly limited
scope with limited exposure, acting as a daemon for sending IPMI events
to syslog. ipmievd requires super user priveleges to access syslog.
- The package installs a service corresponding to ipmievd located at:
/etc/
- The package does not open privileged ports (ports < 1024), but defaults to
using port 514 in certain situations.
- The package does not contain extensions to security-sensitive software
[Quality assurance - function/usage]
- The package works well right after install. Site-specific options for
accessing a BMC may be necessary, but are documented in the man page.
[Quality assurance - maintenance]
- Ubuntu https:/
- Debian https:/
- The package is maintained well in Debian/Ubuntu and does not have too
many bugs with nothing long term and critical open
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- The package does not run a test at build time because it has no test
suite. If it had tests they would likely have strict hardware
dependencies.
- The package does not have any autopkgtests
[Quality assurance - packaging]
- debian/watch is present and works
- This package does not yield massive lintian Warnings, Errors
Lintain results:
W: ipmitool-dbgsym: elf-error In program headers: Unable to find program interpreter name [usr/lib/
W: ipmitool-dbgsym: elf-error In program headers: Unable to find program interpreter name [usr/lib/
- Lintian overrides are no longer present in the package
- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies
- The package will not be installed by default
- Packaging and build is easy
[UI standards]
- Outside of the comand-line tool, the application is not end-user facing.
It has no translations present though.
- ipmitool has no desktop file, and is primarily used via the
command-line on servers
[Dependencies]
- No further depends or recommends dependencies that are not yet in main
[Standards compliance]
- This package correctly follows FHS and Debian Policy
[Maintenance/Owner]
- Owning Team will be Ubuntu Server
- Team is already subscribed to the package
- This does not use static builds
- This does not use vendored code
[Background information]
The Package description explains the package well
Upstream Name is ipmitool
Link to upstream project https:/
Related branches
- Adam Collard (community): Needs Information
-
Diff: 32 lines (+2/-3)2 files modifiedcommunity-maas (+2/-1)
supported-maas (+0/-2)
CVE References
description: | updated |
description: | updated |
Changed in ipmitool (Ubuntu): | |
milestone: | none → ubuntu-22.08 |
Changed in ipmitool (Ubuntu): | |
assignee: | nobody → Ioanna Alifieraki (joalif) |
Changed in ipmitool (Ubuntu): | |
assignee: | Ioanna Alifieraki (joalif) → Ubuntu Security Team (ubuntu-security) |
tags: | added: sec-1107 |
Changed in ipmitool (Ubuntu): | |
status: | Incomplete → New |
Changed in ipmitool (Ubuntu): | |
status: | New → Won't Fix |
Review for Package: ipmitool
[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does need a security review.
List of specific binary packages to be promoted to main: ipmitool_ 1.8.18- 11ubuntu2
Notes:
- Team is already subscribed
Required TODOs: /wiki.ubuntu. com/MainInclusi onProcess# Main_Inclusion_ requirements,
1. Package lacks tests. The lack of tests is understandable due to the nature of the
tool (requires hardware). In this case the subscribed team should provide a test plan.
Copy from https:/
section [Quality assurance - testing] :
the subscribed team must provide a written test plan in a comment to the MIR bug, and
commit to running that test either at each upload of the package or at least once each
release cycle. In the comment to the MIR bug, please link to the codebase of these tests
(scripts or doc of manual steps) and attach a full log of these test runs. This is meant to
assess their validity (e.g. not just superficial)"
Recommended TODOs:
2. Both upstream and Ubuntu builds have many warnings (mostly type related).
It would be nice, if possible, to address some of those.
[Duplication]
There is no other package in main providing the same functionality.
[Dependencies]
OK:
- no other Dependencies to MIR due to this
- ipmitool checked with `check-mir`
- all dependencies can be found in `seeded-in-ubuntu` (already in main)
- none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
more tests now.
Problems: None
[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main
Problems: None
[Security]
OK:
- history of CVEs does not look concerning
- does not use webkit1,2
- does not use lib*v8 directly
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
Problems:
- does open a port/socket
- does deal with cryptography (en-/decryption, certificates, signing, ...)
- does not parse data formats (files [images, video, audio,
xml, json, asn.1], network packets, structures, ...) from
an untrusted source.
- does run a daemon as root
[Common blockers]
OK:
- does not FTBFS currently
- no new python2 dependency
Problems:
- does not have a test suite that runs at build time
- does not have a non-trivial test suite that runs as autopkgtest
[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
control
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update his...