Your message dated Tue, 08 Jul 2008 02:02:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#476624: fixed in cryptsetup 2:1.0.6-3
has caused the Debian Bug report #476624,
regarding Man page typos in cryptsetup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
476624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476624
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.6-1
Tags: patch
User: [EMAIL PROTECTED]
Usertags: origin-ubuntu ubuntu-patch hardy
Severity: minor
/usr/share/man/man5/crypttab.5.gz:
s/eg./e.g./g
s/ie./i.e.
s/dvd/DVD
s/inidicated/indicated
s/nondefault/non-default
s/mountpoints/mount points
Also the lines in this file are incredibly long, but I guess that's a fault
of the software which generated it, and it's not meant to be edited anyway.
/usr/share/man/man8/cryptsetup.8.gz:
s/Maintainance/Maintenance
s/underlaying/underlying
s/backend/back-end
s/calculcation/calculation
s/evertime/every time/g
s/ist stripped/is stripped
s/Mathematic/Mathematics
s/suddely/suddenly
s/COMPATABILITY/COMPATIBILITY
The wording of this manual page could also need some care and loving but
this is just a quick aspell check.
--
Bruno Barrera Yever
LP ID: www.launchpad.net/~bbyever
1c1
< .TH CRYPTSETUP "8" "March 2005" "cryptsetup 1.0.3" "Maintainance Commands"
---
> .TH CRYPTSETUP "8" "March 2005" "cryptsetup 1.0.3" "Maintenance Commands"
91c91,93
< use file as key material. With LUKS, key material supplied in key files via \-d are always used for existing passphrases. If you want to set a new key via a key file, you have to use a positional arg to \fIluksFormat\fR or \fIluksAddKey\fR. If the key file is "-", stdin will be used.
---
> use file as key material. With LUKS, key material supplied in key files via \-d are always used for existing passphrases. If you want to set a new key via a key file, you have to use a positional arg to \fIluksFormat\fR or \fIluksAddKey\fR.
>
> If the key file is "-", stdin will be used. This is different from how cryptsetup usually reads from stdin. See section \fBNOTES ON PASSWORD PROCESSING\fR for more information.
94c96
< set key size in bits. Has to be a multiple of 8 bits. The key size is limited by the used cipher. See output of /proc/crypto for more information. Can be used for \fIcreate\fR or \fIluksFormat\fR, all other LUKS actions will ignore this flag, as the key-size is specified by the partition header. Default is 128.
---
> set key size in bits. Has to be a multiple of 8 bits. The key size is limited by the used cipher. See output of /proc/crypto for more information. Can be used for \fIcreate\fR or \fIluksFormat\fR, all other LUKS actions will ignore this flag, as the key-size is specified by the partition header. Default is 128 for \fIluksFormat\fR and 256 for \fIcreate\fR.
97c99
< force the size of the underlaying device in sectors.
---
> force the size of the underlying device in sectors.
100c102
< start offset in the backend device.
---
> start offset in the back-end device.
103c105
< how many sectors of the encrypted data to skip at the beginning. This is different from the \-\-offset options with respect to IV calculations. Using \-\-offset will shift the IV calculcation by the same negative amount. Hence, if \-\-offset \fIn\fR, sector \fIn\fR will be the first sector on the mapping with IV \fI0\fR. Using \-\-skip would have resulted in sector \fIn\fR being the first sector also, but with IV \fIn\fR.
---
> how many sectors of the encrypted data to skip at the beginning. This is different from the \-\-offset options with respect to IV calculations. Using \-\-offset will shift the IV calculation by the same negative amount. Hence, if \-\-offset \fIn\fR, sector \fIn\fR will be the first sector on the mapping with IV \fI0\fR. Using \-\-skip would have resulted in sector \fIn\fR being the first sector also, but with IV \fIn\fR.
109c111
< The number of microseconds to spend with PBKDF2 password processing. This options is only relevant to LUKS key setting operations as \fIluksFormat\fR or \fIluksAddKey\fR.
---
> The number of microseconds to spend with PBKDF2 password processing. This option is only relevant to LUKS key setting operations as \fIluksFormat\fR or \fIluksAddKey\fR.
115c117
< The number of seconds to wait before timeout. This option is relevant evertime a password is asked, like \fIcreate\fR, \fIluksOpen\fR, \fIluksFormat\fR or \fIluksAddKey\fR.
---
> The number of seconds to wait before timeout. This option is relevant every time a password is asked, like \fIcreate\fR, \fIluksOpen\fR, \fIluksFormat\fR or \fIluksAddKey\fR. It has no effect if used in conjunction with \-\-key-file.
118c120
< How often the input of the passphrase shall be retried. This option is relevant evertime a password is asked, like \fIcreate\fR, \fIluksOpen\fR, \fIluksFormat\fR or \fIluksAddKey\fR. The default is 3 tries.
---
> How often the input of the passphrase shall be retried. This option is relevant every time a password is asked, like \fIcreate\fR, \fIluksOpen\fR, \fIluksFormat\fR or \fIluksAddKey\fR. The default is 3 tries.
128,129c130,131
< .SH NOTES ON PASSWORD PROCESSING FOR REGULAR MAPPINGS
< \fIFrom a file descriptor or a terminal\fR: Password processing is new-line sensitive, meaning the reading will stop after encountering \\n. It will processed the read material with the default hash or the hash given by \-\-hash. After hashing it will be cropped to the key size given by \-s (default 256 bits).
---
> .SH NOTES ON PASSWORD PROCESSING
> \fIFrom a file descriptor or a terminal\fR: Password processing is new-line sensitive, meaning the reading will stop after encountering \\n. It will processed the read material (without newline) with the default hash or the hash given by \-\-hash. After hashing it will be cropped to the key size given by \-s.
131c133
< \fIFrom stdin\fR: Reading will continue until EOF (so using e.g. /dev/random as stdin will not work). After that the read data will be hashed with the default hash or the hash given by \-\-hash and the result will be cropped to the keysize given by \-s (default 256 bits). If "plain" is used as an argument to the hash option, the input data will not be hashed. Instead it will be zero padded (if shorter than the keysize) or truncated (if longer than the keysize) and used directly as the key. No warning will be given if the amount of data read from stdin is less than the keysize.
---
> \fIFrom stdin\fR: Reading will continue until EOF (so using e.g. /dev/random as stdin will not work), with the trailing newline stripped. After that the read data will be hashed with the default hash or the hash given by \-\-hash and the result will be cropped to the keysize given by \-s. If "plain" is used as an argument to the hash option, the input data will not be hashed. Instead it will be zero padded (if shorter than the keysize) or truncated (if longer than the keysize) and used directly as the key. No warning will be given if the amount of data read from stdin is less than the keysize.
133a136,137
>
> If \-\-key-file=- is used for reading the key from stdin, no trailing newline is stripped from the input. Without that option, cryptsetup strips trailing newlines from stdin input.
135c139
< Password processing is totally different for LUKS. LUKS uses PBKDF2 to protect against dictionary attacks (see RFC 2898).
---
> LUKS uses PBKDF2 to protect against dictionary attacks (see RFC 2898).
146c150
< Mathematic can't be bribed. Make sure you keep your passwords safe. There are a few nice tricks for constructing a fallback, when suddely out of (or after being) blue, your brain refuses to cooperate. These fallbacks are possible with LUKS, as it's only possible with LUKS to have multiple passwords.
---
> Mathematics can't be bribed. Make sure you keep your passwords safe. There are a few nice tricks for constructing a fallback, when suddnely out of (or after being) blue, your brain refuses to cooperate. These fallbacks are possible with LUKS, as it's only possible with LUKS to have multiple passwords.
151,154c155,158
< .SH "COMPATABILITY WITH OLD SUSE TWOFISH PARTITIONS"
< To read images created with SuSE Linux 9.2's loop_fish2 use --cipher
< twofish-cbc-null -s 256 -h sha512, for images created with even
< older SuSE Linux use --cipher twofish-cbc-null -s 192 -h
---
> .SH "COMPATIBILITY WITH OLD SUSE TWOFISH PARTITIONS"
> To read images created with SuSE Linux 9.2's loop_fish2 use \-\-cipher
> twofish-cbc-null \-s 256 \-h sha512, for images created with even
> older SuSE Linux use \-\-cipher twofish-cbc-null \-s 192 \-h
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.0.6-3
We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive:
cryptsetup-udeb_1.0.6-3_amd64.udeb
to pool/main/c/cryptsetup/cryptsetup-udeb_1.0.6-3_amd64.udeb
cryptsetup_1.0.6-3.diff.gz
to pool/main/c/cryptsetup/cryptsetup_1.0.6-3.diff.gz
cryptsetup_1.0.6-3.dsc
to pool/main/c/cryptsetup/cryptsetup_1.0.6-3.dsc
cryptsetup_1.0.6-3_amd64.deb
to pool/main/c/cryptsetup/cryptsetup_1.0.6-3_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Meurer <[EMAIL PROTECTED]> (supplier of updated cryptsetup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Mon, 07 Jul 2008 00:30:07 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb
Architecture: source amd64
Version: 2:1.0.6-3
Distribution: unstable
Urgency: low
Maintainer: Jonas Meurer <[EMAIL PROTECTED]>
Changed-By: Jonas Meurer <[EMAIL PROTECTED]>
Description:
cryptsetup - configures encrypted block devices
cryptsetup-udeb - configures encrypted block devices (udeb)
Closes: 476624 477203 483882 487056 487246 488128 488131
Changes:
cryptsetup (2:1.0.6-3) unstable; urgency=low
.
[ Jonas Meurer ]
* Fix cryptdisks.functions to actually recognize the noauto option. Thanks
to Christian Pernegger <[EMAIL PROTECTED]> (closes: #483882)
* Update patches/02_manpage.patch to fix two more typos, thanks to Bruno
Barrera Yever <[EMAIL PROTECTED]> (closes: #476624) and to remove a
duplicate sentence.
* Rephrase "Enter password for $crypttarget" to "Enter password to unlock
the disk $cryptsource ($crypttarget)" in initramfs/cryptroot.script.
* Bump Standards-Version to 3.8.0:
- Add a README.source which references /usr/share/doc/quilt/README.source.
- Add support for debian build option parallel=n to debian/rules.
* Add a udev rules file to ignore temporary-cryptsetup-* devices, as
suggested in bug #467200. Thanks to Sam Morris <[EMAIL PROTECTED]>.
* Transform debian/copyright into machine-readable code as proposed in
http://wiki.debian.org/Proposals/CopyrightFormat. Update and add several
copyright notices.
* Change reference to docbook xml v4.2 driver file from an online version
to a local one in the manpage files, as the build process should not
depend on internet access. Add docbook-xml to build-depends. Thanks to
Lucas Nussbaum <[EMAIL PROTECTED]>. (closes: #487056)
.
[ David Härdeman ]
* Hopefully fix askpass to properly handle console and usplash input
(closes: #477203)
* Clarify crypttab manpage (closes: #487246)
* Make regex work if keyfile has extended attributes,
https://launchpad.net/bugs/231339 (closes: #488131)
* Support comments in options part of crypttab (closes: #488128)
Checksums-Sha1:
188e589284e6e2732b4b2cf625ab5a1bd27ca35c 1445 cryptsetup_1.0.6-3.dsc
ffc83fa04eb62dd966024525889769050060959d 57647 cryptsetup_1.0.6-3.diff.gz
547bd3e7aec4fa1ba5b765b9a770e39a5d6a68a2 309830 cryptsetup_1.0.6-3_amd64.deb
1afd97b429773cd809c3d603a84a9bbcab584b43 248080
cryptsetup-udeb_1.0.6-3_amd64.udeb
Checksums-Sha256:
6db57c2016dbdb6b4da41b248d8e7bd16dfb963716989b89d6ac32d4e50914f0 1445
cryptsetup_1.0.6-3.dsc
fe66fd2922b51edf6860cdb623a1997706e0454fa0d8c7fa28eb4945fb1ef38e 57647
cryptsetup_1.0.6-3.diff.gz
d3b48375ae837afc62a4cbc5633fcea2e8de9e085504714867db636884858a26 309830
cryptsetup_1.0.6-3_amd64.deb
c2b12fde0e0f1f4233b76f010602854721ed4248c09db288a48479dd08185864 248080
cryptsetup-udeb_1.0.6-3_amd64.udeb
Files:
8d6f94a09766273ee7257cbce8b47f07 1445 admin optional cryptsetup_1.0.6-3.dsc
ca15fedbd73b4180de071e536f87b435 57647 admin optional
cryptsetup_1.0.6-3.diff.gz
4572af0c78b62b2ca1884cd4f606451f 309830 admin optional
cryptsetup_1.0.6-3_amd64.deb
e371dd29ad1ad1aba603d40673255eeb 248080 debian-installer optional
cryptsetup-udeb_1.0.6-3_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkhxSYQACgkQd6lUs+JfIQLKMQCdEjTwBJJGlOmrdLUfUhC/v/Qa
wikAniZXUSF6duZh+P2DUmdCY0K26LNC
=ofaw
-----END PGP SIGNATURE-----
--- End Message ---
