This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug. This will ensure that all associated bugs get updated
when new packages are pushed to stable.
# bugfix, security, enhancement, newpackage (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for CVE-2016-4484
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
This is NOT bug in cryptsetup package.
The mentioned scripts are not part of the cryptsetup package, neither in fedora, nor upstream.
People who need to secure their system have to:
- add a BIOS password
- add a grub password
- add "rd.shell=0" to the kernel cmdline
Anaconda does add "rd.shell=0" to the kernel cmdline, if you setup the
bootloader with a password. To setup a bootloader with a password, kickstart must be used. In other words, the default installation is not safe from physical access at the bootloader level without additional steps listed above.
So this is not a bug, although the documentation could be more verbose certainly.