1995-05-12 19:10:09 +00:00
|
|
|
.\" Copyright (c) 1980, 1991, 1993
|
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
|
.\"
|
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
|
.\" are met:
|
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
|
.\"
|
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
|
.\"
|
|
|
|
|
.\" From: @(#)swapon.8 8.1 (Berkeley) 6/5/93
|
1999-08-28 00:22:10 +00:00
|
|
|
.\" $FreeBSD$
|
1995-05-12 19:10:09 +00:00
|
|
|
.\"
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Dd December 10, 2016
|
1995-05-12 19:10:09 +00:00
|
|
|
.Dt DUMPON 8
|
2001-07-10 11:04:34 +00:00
|
|
|
.Os
|
1995-05-12 19:10:09 +00:00
|
|
|
.Sh NAME
|
|
|
|
|
.Nm dumpon
|
|
|
|
|
.Nd "specify a device for crash dumps"
|
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1995-05-12 19:10:09 +00:00
|
|
|
.Op Fl v
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Op Fl k Ar public_key_file
|
1998-05-27 11:05:59 +00:00
|
|
|
.Ar special_file
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1998-05-27 11:05:59 +00:00
|
|
|
.Op Fl v
|
2004-07-18 09:57:47 +00:00
|
|
|
.Cm off
|
2012-11-01 18:59:19 +00:00
|
|
|
.Nm
|
2012-11-02 17:30:08 +00:00
|
|
|
.Op Fl v
|
2012-11-01 18:59:19 +00:00
|
|
|
.Fl l
|
1995-05-12 19:10:09 +00:00
|
|
|
.Sh DESCRIPTION
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
|
.Nm
|
2004-10-03 23:35:34 +00:00
|
|
|
utility is used to specify a device where the kernel can save a crash
|
|
|
|
|
dump in the case of a panic.
|
1998-05-25 08:54:40 +00:00
|
|
|
.Pp
|
2001-07-15 07:53:42 +00:00
|
|
|
Calls to
|
1998-05-27 11:05:59 +00:00
|
|
|
.Nm
|
|
|
|
|
normally occur from the system multi-user initialization file
|
1995-05-12 19:10:09 +00:00
|
|
|
.Pa /etc/rc ,
|
1998-05-27 11:05:59 +00:00
|
|
|
controlled by the
|
|
|
|
|
.Dq dumpdev
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
and
|
|
|
|
|
.Dq dumppubkey
|
|
|
|
|
variables in the boot time configuration file
|
1998-05-27 11:05:59 +00:00
|
|
|
.Pa /etc/rc.conf .
|
|
|
|
|
.Pp
|
2013-04-30 07:22:03 +00:00
|
|
|
The default type of kernel crash dump is the mini crash dump.
|
|
|
|
|
Mini crash dumps hold only memory pages in use by the kernel.
|
|
|
|
|
Alternatively, full memory dumps can be enabled by setting the
|
|
|
|
|
.Va debug.minidump
|
|
|
|
|
.Xr sysctl 8
|
|
|
|
|
variable to 0.
|
|
|
|
|
.Pp
|
|
|
|
|
For systems using full memory dumps, the size of the specified dump
|
|
|
|
|
device must be at
|
2004-10-03 23:35:34 +00:00
|
|
|
least the size of physical memory.
|
2006-01-07 19:17:13 +00:00
|
|
|
Even though an additional 64 kB header is added to the dump, the BIOS for a
|
2004-10-03 23:35:34 +00:00
|
|
|
platform typically holds back some memory, so it is not usually
|
2002-08-13 11:39:38 +00:00
|
|
|
necessary to size the dump device larger than the actual amount of RAM
|
|
|
|
|
available in the machine.
|
2013-04-30 07:22:03 +00:00
|
|
|
Also, when using full memory dumps, the
|
2004-10-03 23:38:49 +00:00
|
|
|
.Nm
|
|
|
|
|
utility will refuse to enable a dump device which is smaller than the
|
|
|
|
|
total amount of physical memory as reported by the
|
|
|
|
|
.Va hw.physmem
|
|
|
|
|
.Xr sysctl 8
|
|
|
|
|
variable.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Op Fl k Ar public_key_file
|
|
|
|
|
flag causes
|
|
|
|
|
.Nm
|
|
|
|
|
to generate a one-time key for kernel crash dump encryption.
|
|
|
|
|
The key will be replaced by a new one when the
|
|
|
|
|
.Nm
|
|
|
|
|
utility is run again.
|
|
|
|
|
The key is encrypted using
|
|
|
|
|
.Ar public_key_file .
|
|
|
|
|
This process is sandboxed using
|
|
|
|
|
.Xr capsicum 4 .
|
|
|
|
|
Both plain and encrypted keys are sent to the kernel using
|
|
|
|
|
.Dv DIOCSKERNELDUMP
|
|
|
|
|
.Xr ioctl 2 .
|
|
|
|
|
A user can specify the
|
|
|
|
|
.Ar public_key_file
|
|
|
|
|
in the
|
|
|
|
|
.Dq dumppubkey
|
|
|
|
|
variable defined in
|
|
|
|
|
.Pa /etc/rc.conf
|
|
|
|
|
for use with the
|
|
|
|
|
.Pa /etc/rc.d/dumpon
|
|
|
|
|
.Xr rc 8
|
|
|
|
|
script.
|
|
|
|
|
This flag requires a kernel compiled with the
|
|
|
|
|
.Dv EKCD
|
|
|
|
|
kernel option.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
2012-11-01 18:59:19 +00:00
|
|
|
.Fl l
|
|
|
|
|
flag causes
|
|
|
|
|
.Nm
|
|
|
|
|
to print the current dump device or _PATH_DEVNULL ("/dev/null") if no device is
|
|
|
|
|
configured.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
1995-05-12 19:10:09 +00:00
|
|
|
.Fl v
|
2001-07-15 07:53:42 +00:00
|
|
|
flag causes
|
1995-05-12 19:10:09 +00:00
|
|
|
.Nm
|
1998-05-27 11:05:59 +00:00
|
|
|
to be verbose about its activity.
|
2003-05-07 19:37:51 +00:00
|
|
|
.Sh IMPLEMENTATION NOTES
|
2000-07-14 18:04:39 +00:00
|
|
|
Since a
|
|
|
|
|
.Xr panic 9
|
|
|
|
|
condition may occur in a situation
|
|
|
|
|
where the kernel cannot trust its internal representation
|
2002-08-21 18:11:48 +00:00
|
|
|
of the state of any given file system,
|
2000-07-14 18:04:39 +00:00
|
|
|
one of the system swap devices,
|
|
|
|
|
and
|
|
|
|
|
.Em not
|
2002-08-21 18:11:48 +00:00
|
|
|
a device containing a file system,
|
2000-07-14 18:04:39 +00:00
|
|
|
should be used as the dump device.
|
1998-05-25 08:54:40 +00:00
|
|
|
.Pp
|
2001-07-15 07:53:42 +00:00
|
|
|
The
|
1995-05-12 19:10:09 +00:00
|
|
|
.Nm
|
2003-05-07 19:37:51 +00:00
|
|
|
utility operates by opening
|
1995-05-12 19:10:09 +00:00
|
|
|
.Ar special_file
|
2003-05-07 19:37:51 +00:00
|
|
|
and making a
|
|
|
|
|
.Dv DIOCSKERNELDUMP
|
|
|
|
|
.Xr ioctl 2
|
|
|
|
|
request on it to save kernel crash dumps.
|
|
|
|
|
If
|
1995-05-12 19:10:09 +00:00
|
|
|
.Ar special_file
|
1998-05-27 11:05:59 +00:00
|
|
|
is the text string:
|
2003-05-07 19:37:51 +00:00
|
|
|
.Dq Li off ,
|
|
|
|
|
.Nm
|
|
|
|
|
performs a
|
|
|
|
|
.Dv DIOCSKERNELDUMP
|
|
|
|
|
.Xr ioctl 2
|
|
|
|
|
on
|
|
|
|
|
.Pa /dev/null
|
|
|
|
|
and thus instructs the kernel not to save crash dumps.
|
2014-10-08 12:19:48 +00:00
|
|
|
.Pp
|
|
|
|
|
Since
|
|
|
|
|
.Nm
|
|
|
|
|
cannot be used during kernel initialization, the
|
|
|
|
|
.Va dumpdev
|
|
|
|
|
variable of
|
|
|
|
|
.Xr loader 8
|
|
|
|
|
must be used to enable dumps for system panics which occur
|
|
|
|
|
during kernel initialization.
|
2005-01-18 10:09:38 +00:00
|
|
|
.Sh FILES
|
2014-10-08 12:19:48 +00:00
|
|
|
.Bl -tag -width "/dev/{ada,da}?s?b" -compact
|
|
|
|
|
.It Pa /dev/{ada,da}?s?b
|
2005-01-18 10:09:38 +00:00
|
|
|
standard swap areas
|
|
|
|
|
.It Pa /etc/rc.conf
|
|
|
|
|
boot-time system configuration
|
|
|
|
|
.El
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Sh EXAMPLES
|
|
|
|
|
In order to generate an RSA private key a user can use the
|
|
|
|
|
.Xr genrsa 1
|
|
|
|
|
tool:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # openssl genrsa -out private.pem 4096
|
|
|
|
|
.Pp
|
|
|
|
|
A public key can be extracted from the private key using the
|
|
|
|
|
.Xr rsa 1
|
|
|
|
|
tool:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # openssl rsa -in private.pem -out public.pem -pubout
|
|
|
|
|
.Pp
|
|
|
|
|
Once the RSA keys are created the private key should be moved to a safe place.
|
|
|
|
|
Now
|
|
|
|
|
.Pa public.pem
|
|
|
|
|
can be used by
|
|
|
|
|
.Nm
|
|
|
|
|
to configure encrypted kernel crash dumps:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # dumpon -k public.pem /dev/ada0s1b
|
|
|
|
|
.Pp
|
|
|
|
|
It is recommended to test if the kernel saves encrypted crash dumps using the
|
|
|
|
|
current configuration.
|
|
|
|
|
The easiest way to do that is to cause a kernel panic using the
|
|
|
|
|
.Xr ddb 4
|
|
|
|
|
debugger:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # sysctl debug.kdb.panic=1
|
|
|
|
|
.Pp
|
|
|
|
|
In the debugger the following commands should be typed to write a core dump and
|
|
|
|
|
reboot:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl db> call doadump(0)
|
|
|
|
|
.Dl db> reset
|
|
|
|
|
.Pp
|
|
|
|
|
After reboot
|
|
|
|
|
.Xr savecore 8
|
|
|
|
|
should be able to save the core dump in the core directory which is
|
|
|
|
|
.Pa /var/crash
|
|
|
|
|
by default:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # savecore /var/crash /dev/ada0s1b
|
|
|
|
|
.Pp
|
|
|
|
|
Three files should be created in the core directory:
|
|
|
|
|
.Pa info.# ,
|
|
|
|
|
.Pa key.#
|
|
|
|
|
and
|
|
|
|
|
.Pa vmcore_encrypted.#
|
|
|
|
|
where
|
|
|
|
|
.Dq #
|
|
|
|
|
is the number of the last core dump saved by
|
|
|
|
|
.Xr savecore 8 .
|
|
|
|
|
The
|
|
|
|
|
.Pa vmcore_encrypted.#
|
|
|
|
|
can be decrypted using the
|
|
|
|
|
.Xr decryptcore 8
|
|
|
|
|
utility:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # decryptcore -p private.pem -k key.# -e vmcore_encrypted.# -c vmcore.#
|
|
|
|
|
.Pp
|
|
|
|
|
or shorter:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # decryptcore -p private.pem -n #
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Pa vmcore.#
|
|
|
|
|
can be now examined using
|
|
|
|
|
.Xr kgdb 1 :
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # kgdb /usr/obj/sys/GENERIC/kernel.debug vmcore.#
|
|
|
|
|
.Pp
|
|
|
|
|
or shorter:
|
|
|
|
|
.Pp
|
|
|
|
|
.Dl # kgdb -n # /usr/obj/sys/GENERIC/kernel.debug
|
|
|
|
|
.Pp
|
|
|
|
|
The core was decrypted properly if
|
|
|
|
|
.Xr kgdb 1
|
|
|
|
|
does not print any errors.
|
1995-05-12 19:10:09 +00:00
|
|
|
.Sh SEE ALSO
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Xr kgdb 1 ,
|
|
|
|
|
.Xr ddb 4 ,
|
1998-05-25 08:54:40 +00:00
|
|
|
.Xr fstab 5 ,
|
|
|
|
|
.Xr rc.conf 5 ,
|
|
|
|
|
.Xr config 8 ,
|
1998-08-31 16:41:09 +00:00
|
|
|
.Xr init 8 ,
|
2014-10-08 12:19:48 +00:00
|
|
|
.Xr loader 8 ,
|
1995-05-12 19:10:09 +00:00
|
|
|
.Xr rc 8 ,
|
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and
savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump
configuration in the diocskerneldump_arg structure to the kernel.
The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for
backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using
an RSA public key in capability mode. Currently only AES-256-CBC is supported
but EKCD was designed to implement support for other algorithms in the future.
The public key is chosen using the -k flag. The dumpon rc(8) script can do this
automatically during startup using the dumppubkey rc.conf(5) variable. Once the
keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O
control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random
IV and sets up the key schedule for the specified algorithm. Each time the
kernel tries to write a crash dump to the dump device, the IV is replaced by
a SHA-256 hash of the previous value. This is intended to make a possible
differential cryptanalysis harder since it is possible to write multiple crash
dumps without reboot by repeating the following commands:
# sysctl debug.kdb.enter=1
db> call doadump(0)
db> continue
# savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted
symmetric key. The kernel dump key size is included in a kernel dump header.
The size is an unsigned 32-bit integer and it is aligned to a block size.
The header structure has 512 bytes to match the block size so it was required to
make a panic string 4 bytes shorter to add a new field to the header structure.
If the kernel dump key size in the header is nonzero it is assumed that the
kernel dump key is placed after the first header on the dump device and the core
dump is encrypted.
Separate functions were implemented to write the kernel dump header and the
kernel dump key as they need to be unencrypted. The dump_write function encrypts
data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps
are not supported due to the way they are constructed which makes it impossible
to use the CBC mode for encryption. It should be also noted that textdumps don't
contain sensitive data by design as a user decides what information should be
dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header
is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel
dump key. This is performed by a child process in capability mode.
If the decryption was not successful the parent process removes a partially
decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8),
dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.
The feature still has to be tested on arm and arm64 as it wasn't possible to run
FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd
Reviewed by: cem, oshogbo, pjd
Partial review: delphij, emaste, jhb, kib
Approved by: pjd (mentor)
Differential Revision: https://reviews.freebsd.org/D4712
2016-12-10 16:20:39 +00:00
|
|
|
.Xr decryptcore 8 ,
|
1998-05-25 08:54:40 +00:00
|
|
|
.Xr savecore 8 ,
|
|
|
|
|
.Xr swapon 8 ,
|
|
|
|
|
.Xr panic 9
|
1995-05-12 19:10:09 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
|
The
|
|
|
|
|
.Nm
|
2002-07-06 19:34:18 +00:00
|
|
|
utility appeared in
|
2016-10-02 23:35:45 +00:00
|
|
|
.Fx 2.0.5 .
|
2005-01-18 10:09:38 +00:00
|
|
|
.Sh BUGS
|
|
|
|
|
Because the file system layer is already dead by the time a crash dump
|
|
|
|
|
is taken, it is not possible to send crash dumps directly to a file.
|
