Add entry on encrypted kernel crash dumps from def
This commit is contained in:
parent
45bc8e3808
commit
39ca45527b
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48000
1 changed files with 41 additions and 0 deletions
|
@ -1980,4 +1980,45 @@
|
|||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
<project cat='proj'>
|
||||
<title>Encrypted Kernel Crash Dumps</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>Konrad</given>
|
||||
<common>Witaszczyk</common>
|
||||
</name>
|
||||
<email>def@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://lists.FreeBSD.org/pipermail/freebsd-security/2015-December/008780.html">Technical Details</url>
|
||||
<url href="https://reviews.FreeBSD.org/D4712">Patch Review</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>Kernel crash dumps contain information about currently
|
||||
running processes. This can include sensitive data, for example
|
||||
passwords kept in memory by a browser when a kernel panic
|
||||
occurred. An entity that can read data from a dump device or a
|
||||
crash directory can also extract this information from a core
|
||||
dump. In order to prevent this situation, the core dump should be
|
||||
encrypted before it is stored on the dump device.</p>
|
||||
|
||||
<p>This project allows a kernel to encrypt a core dump during
|
||||
a panic. A user can configure the kernel for encrypted dumps and
|
||||
save the core dump after reboot using the existing tools,
|
||||
<tt>dumpon(8)</tt> and <tt>savecore(8)</tt>. A new tool
|
||||
<tt>decryptcore(8)</tt> was added to decrypt the core files.</p>
|
||||
|
||||
<p>A patch has been uploaded to Phabricator for review. The
|
||||
project is currently being updated to address the review comments,
|
||||
and should be committed as soon as it is accepted. For more
|
||||
technical details, please visit the FreeBSD-security mailing list
|
||||
archive or see the Phabricator review.</p>
|
||||
</body>
|
||||
</project>
|
||||
</report>
|
||||
|
|
Loading…
Reference in a new issue