PR/58212: Malte Dehling: Add zfs verification method

cgdconfig(8): Handle -P/-S for shared keys with -G too.

This way you can convert an existing parameters file to one that is
derived from a shared key, and derive other subkeys for other disks
from the same shared key.

cgdconfig -G -S -o /etc/cgd/wd0.shared /etc/cgd/wd0
cgdconfig -G -S -o /etc/cgd/wd1.shared \
-P /etc/cgd/wd0.shared /etc/cgd/wd1

This way, if you enter the same new password both times, wd0.shared
and wd1.shared generate the same keys as wd0 and wd1, but only need
one password entry with `cgdconfig -C'.

cgdconfig(8): Add support for generating shared-key parameters files.

Usage model:

- Generate a parameters file that supports sharing its main key:

cgdconfig -g -S -o /etc/cgd/wd0e -V gpt adiantum

- Make another parameters file that uses the same shared main key but
derives an independent subkey from it:

cgdconfig -g -S -P /etc/cgd/wd0e -o /etc/cgd/ld1e \
-V disklabel aes-cbc 256

cgdconfig(8): Add support for shared keys.

New clause `shared <id> algorithm <alg> subkey <info>' in a keygen
block enables `cgdconfig -C' to reuse a key between different params
files, so you can, e.g., use a single password for multiple disks.
This is better than simply caching the password itself because:

- Hashing the password is expensive, so it should only be done once.

Suppose your budget is time t before you get bored, and you
calibrate password hash parameters to unlock n disks before you get
bored waiting for `cgdconfig -C'.

. With n password hashings the adversary's cost goes up only by a
factor of t/n.
. With one password hashing and n subkeys the adversary's cost goes
up by a factor of n.

And if you ever add a disk, rehashing it will make `cgdconfig -C'
go over budget, whereas another subkey adds negligible cost to you.

- Subkeys work for other types of keygen blocks, like shell_cmd,
which could be used to get a key from a hardware token that needs a
button press.

The <info> parameter must be different for each params file;
everything else in the keygen block must be the same. With this
clause, the keygen block determines a shared key used only to derive
keys; the actual key used by cgdconfig is derived from the shared key
by the specified algorithm.

The only supported algorithm is hkdf-hmac-sha256, which uses
HKDF-Expand of RFC 5869 instantiated with SHA-256.

Example:

algorithm aes-cbc;
iv-method encblkno1;
keylength 128;
verify_method none;
keygen pkcs5_pbkdf2/sha1 {
iterations 39361;
salt AAAAgMoHiYonye6KogdYJAobCHE=;
shared "pw" algorithm hkdf-hmac-sha256
subkey AAAAgFlw0BMQ5gY+haYkZ6JC+yY=;
};

The key used for this disk will be derived by

HKDF-HMAC-SHA256_k(WXDQExDmBj6FpiRnokL7Jg==),

where k is the outcome of PBKDF2-SHA1 with the given parameters.

Note that <info> encodes a four-byte prefix giving the big-endian
length in bits of the info argument to HKDF, just like all other bit
strings in cgdconfig parameters files.

If you have multiple disks configured using the same keygen block
except for the info parameter, `cgdconfig -C' will only prompt once
for your passphrase, generate a shared key k with PBKDF2 as usual,
and then reuse it for each of the disks.

cgdconfig(8): New -T operation prints all generated keys in cgd.conf.

For testing purposes.

cgdconfig(8): New -t operation just prints the derived key in base64.

For testing purposes.

cgdconfig.8: Use argon2id in examples

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for
password-based disk encryption.

Several new keygen parameters are supported:

memory (integer, in kilobytes)
parallelism (integer, usually the number of CPU cores)
version (integer, usually 19...)

We do our best to calibrate these automatically when the paramsfile
is initially generated.

lgtm riastradh@

cgdconfig.8: use gpt in examples, it's more versatile for this use case

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

cgdconfig(8): Handle -P/-S for shared keys with -G too.

This way you can convert an existing parameters file to one that is
derived from a shared key, and derive other subkeys for other disks
from the same shared key.

cgdconfig -G -S -o /etc/cgd/wd0.shared /etc/cgd/wd0
cgdconfig -G -S -o /etc/cgd/wd1.shared \
-P /etc/cgd/wd0.shared /etc/cgd/wd1

This way, if you enter the same new password both times, wd0.shared
and wd1.shared generate the same keys as wd0 and wd1, but only need
one password entry with `cgdconfig -C'.

cgdconfig(8): Add support for generating shared-key parameters files.

Usage model:

- Generate a parameters file that supports sharing its main key:

cgdconfig -g -S -o /etc/cgd/wd0e -V gpt adiantum

- Make another parameters file that uses the same shared main key but
derives an independent subkey from it:

cgdconfig -g -S -P /etc/cgd/wd0e -o /etc/cgd/ld1e \
-V disklabel aes-cbc 256

cgdconfig(8): Add support for shared keys.

New clause `shared <id> algorithm <alg> subkey <info>' in a keygen
block enables `cgdconfig -C' to reuse a key between different params
files, so you can, e.g., use a single password for multiple disks.
This is better than simply caching the password itself because:

- Hashing the password is expensive, so it should only be done once.

Suppose your budget is time t before you get bored, and you
calibrate password hash parameters to unlock n disks before you get
bored waiting for `cgdconfig -C'.

. With n password hashings the adversary's cost goes up only by a
factor of t/n.
. With one password hashing and n subkeys the adversary's cost goes
up by a factor of n.

And if you ever add a disk, rehashing it will make `cgdconfig -C'
go over budget, whereas another subkey adds negligible cost to you.

- Subkeys work for other types of keygen blocks, like shell_cmd,
which could be used to get a key from a hardware token that needs a
button press.

The <info> parameter must be different for each params file;
everything else in the keygen block must be the same. With this
clause, the keygen block determines a shared key used only to derive
keys; the actual key used by cgdconfig is derived from the shared key
by the specified algorithm.

The only supported algorithm is hkdf-hmac-sha256, which uses
HKDF-Expand of RFC 5869 instantiated with SHA-256.

Example:

algorithm aes-cbc;
iv-method encblkno1;
keylength 128;
verify_method none;
keygen pkcs5_pbkdf2/sha1 {
iterations 39361;
salt AAAAgMoHiYonye6KogdYJAobCHE=;
shared "pw" algorithm hkdf-hmac-sha256
subkey AAAAgFlw0BMQ5gY+haYkZ6JC+yY=;
};

The key used for this disk will be derived by

HKDF-HMAC-SHA256_k(WXDQExDmBj6FpiRnokL7Jg==),

where k is the outcome of PBKDF2-SHA1 with the given parameters.

Note that <info> encodes a four-byte prefix giving the big-endian
length in bits of the info argument to HKDF, just like all other bit
strings in cgdconfig parameters files.

If you have multiple disks configured using the same keygen block
except for the info parameter, `cgdconfig -C' will only prompt once
for your passphrase, generate a shared key k with PBKDF2 as usual,
and then reuse it for each of the disks.

cgdconfig(8): New -T operation prints all generated keys in cgd.conf.

For testing purposes.

cgdconfig(8): New -t operation just prints the derived key in base64.

For testing purposes.

cgdconfig.8: Use argon2id in examples

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for
password-based disk encryption.

Several new keygen parameters are supported:

memory (integer, in kilobytes)
parallelism (integer, usually the number of CPU cores)
version (integer, usually 19...)

We do our best to calibrate these automatically when the paramsfile
is initially generated.

lgtm riastradh@

cgdconfig.8: use gpt in examples, it's more versatile for this use case

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

cgdconfig.8: Use argon2id in examples

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for
password-based disk encryption.

Several new keygen parameters are supported:

memory (integer, in kilobytes)
parallelism (integer, usually the number of CPU cores)
version (integer, usually 19...)

We do our best to calibrate these automatically when the paramsfile
is initially generated.

lgtm riastradh@

cgdconfig.8: use gpt in examples, it's more versatile for this use case

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for
password-based disk encryption.

Several new keygen parameters are supported:

memory (integer, in kilobytes)
parallelism (integer, usually the number of CPU cores)
version (integer, usually 19...)

We do our best to calibrate these automatically when the paramsfile
is initially generated.

lgtm riastradh@

cgdconfig.8: use gpt in examples, it's more versatile for this use case

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

cgdconfig.8: use gpt in examples, it's more versatile for this use case

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

The -n flag is useless with -g, don't mention it.

From rudolf in PR misc/36243

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

Touch up cgdconfig(8) man page.

- Suggest adiantum first.
- Remove references to Blowfish.
- Clarify that ivmethod is relevant only for ancient compatibility.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

Use Nm.

cgdconfig.8: remove references to using cgd for swap

this is potentially misleading now that the kernel does swap encryption

cgdconfig.8: Reflect actual behaviour of /dev/(u)random

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

branches: 1.40.2;

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.

branches: 1.24.2;
Convert TNF licenses to new 2 clause variant

branches: 1.23.12; 1.23.14;
Add a DIAGNOSTICS section and explain that the error message "could not
calibrate pkcs5_pbkdf2" could have resulted due to dynamic changes in cpu
clock frequency.

Correct the omission in 're-enter' verification method addition in EXAMPLES.

Bump date for previous, and re-add some flags that were removed in the
previous commit without a mention in the commit message, and which are
still in the usage.

Add "urandomkey" key generation method as described in PR kern/22766;
useful for configuring a throwaway key for cgd-on-swap at boot time.

Add options to SYNOPSIS.

Addresses PR misc/26065.

branches: 1.18.2;
Drop trailing whitespace; new sentence, new line.

Fix a longstanding algorithmic flaw in PKCS#5 key generation.

The existing pkcs5_pbdkf2 keygen method is retained functionally
as-is, for compatibility with existing params files. The corrected
algorithm, which is now the default for new params file generation, is
called pkcs5_pbkdf2/sha1.

NB. The backwards compatibility for the miscreant keygen method will
be removed at the same time as support for the previous parameters
file syntax. Sometime between now and then, users should update their
params files using -G, which will create a new params file including
an xor value so that the resulting generated key is the same; they
should also

Problem discovery and 2-char algorithm fix by Charles Blundell, messy
compat goop by me, long complicated names by Roland Dowdeswell.

Update manpage accordingly and bump date.

Add article.

add a new verification method that prompts for the pkcs#5 pbkdf2
passphrase again and checks the generated key against the original.

Remove superfluous "".

Bump date for last-but-one; remove superfluous .Pp.

Fix typo. params files are not stored in /dev/cgd/

substantial rototill of the code.

o added new features:
o -G: generate a new paramsfile that produces the same
key as the old paramsfile,
o ffs verify_method,
o multiple keygen methods that are xor'ed together
(for n-factor authentication), and
o calibrating the iteration count of PKCS#5 PBKDF2 to
the current machine's speed.
o changed paramsfile format to allow for the new features.
o replaced open-coded parser with yacc grammar.
o lots of supporting changes.
o updated documentation to reflect new features and new
paramsfile format.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

The next release will be 2.0, not 1.7.

At the suggestion of wiz@, we remove the lines that mention that the
lack of the feature added earlier today was a bug.

Add documentation for verification methods. Specify defaults for IV
method, keygen method and verification method.

Begin new sentence in upper case.

cgdconfig first appeared in NetBSD 1.7 (for now).

New sentence, new line. Some mdoc cleanup, other minor nits.

note some other caveats and uses

channelling wiz

Initial checkin of cgdconfig(8), a program to configure a cgd.

Sort SEE ALSO.

s/Dec/December/.

Document that cgd.conf supports NAME=label and ROOT.<suffix> targets.

XXX Default paramsfile for NAME=label is /etc/cgd/dkNN (resolved wedge
partition) and /etc/cgd/ROOT.<suffix> for ROOT.<suffix>. This isn't yet
documented. IMO, it should be the other way around: /etc/cgd/label
for the former and /et/cgd/[root-device] for the latter.

typo

With the change to use getpass_r the 128 byte passphrase limit no
longer applies, so update the BUGS section here to reflect that change.
The limit now is 1023 whichever method is used to fetch the passphrase.

Add '-e' option (echo the passphrase) and wipe the passphrase after use.

XXX Using memset for wiping isn't a good idea because memset is likely
optimised away by gcc. This should be revisited.

Add commas in enumeration.

Fix missing -p in usage message (noted by Christoph Badura, thanks),
and update -l usage as well.

While here fix man page synopses and a few other odds and ends.

branches: 1.36.6; 1.36.12;
Spelling mistake.
Bump date.

Bump date for previous. Fix typo.

Add validation methods "mbr" and "gpt" for disks without a valid disklabel.

Whitespace.
New sentence, new line.

add cgdconfig -l like vnconfig -l

branches: 1.31.2; 1.31.8;
fix typo

\\ -> \e

Document -n, from Jukka Ruohonen in private mail.
Bump date.

PR/39525: Joachim Schueth, Frederik Sausmikat:
cgd inadvertently encrypts blkno eight times to generate IV

Bump date for previous.

Add a new keygen method which will execute an external command and
take its output as the key. I've been meaning to do this for quite
a while...

Add -p flag to retrieve passphrases from stdin. This is mainly aimed
at programatic use where the caller wants to be able to use PKCS#5.

Disable looping on invalid verifications unless both a passphrase method
is in use and the -p flag is not specified.

Update man page to document -p flag.