cryptsetup(8) man page confused about signals

Bug #1905065 reported by Brian Foster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
New
Undecided
Unassigned

Bug Description

The cryptsetup(8) manual page says (spurious lines omitted):

   reencrypt <device> or --active-name <name> [<new_name>]

      Run resilient reencryption (LUKS2 device only).
    [...]
      Reencryption process may be safely interrupted by a user via SIGTERM
      signal (ctrl+c).

No: Control-C generates SIGINT.
System shutdown generates SIGTERM.

Nothing is said about the other two very similar signals:

   SIGHUP Generated by logout (historically, by modem hanging up).
   SIGQUIT Generated by control-\ (control-backslash).

I do not know if cryptsetup worries about those two signals or not.
Either way, the manual page should say something — in addition to
un-confusing SIGTERM and control-C (SIGINT); see signal(7).

N.b. To be pedantic, the keys which generate SIGINT and SIGQUIT
      can be configured (see, e.g., stty(1)), however, ^C and ^\
      are the most common (and default, I think).

Also, the package is technically "cryptsetup-bin" not "cryptsetup",
but Launchpad claims "'cryptsetup-bin' does not exist in Ubuntu."

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cryptsetup-bin 2:2.2.2-3ubuntu2.3
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Nov 20 18:15:03 2020
InstallationDate: Installed on 2020-10-19 (32 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian Foster (blfoster) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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