diff options
Diffstat (limited to 'security/nss/doc/rst/legacy/tools/nss_tools_dbck-tasks/index.rst')
| -rw-r--r-- | security/nss/doc/rst/legacy/tools/nss_tools_dbck-tasks/index.rst | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/security/nss/doc/rst/legacy/tools/nss_tools_dbck-tasks/index.rst b/security/nss/doc/rst/legacy/tools/nss_tools_dbck-tasks/index.rst new file mode 100644 index 0000000000..a9e8af546a --- /dev/null +++ b/security/nss/doc/rst/legacy/tools/nss_tools_dbck-tasks/index.rst @@ -0,0 +1,28 @@ +.. _mozilla_projects_nss_tools_nss_tools_dbck-tasks: + +NSS Tools dbck-tasks +==================== + +.. _nss_security_tools_dbck_tasks: + +`NSS Security Tools: dbck Tasks <#nss_security_tools_dbck_tasks>`__ +------------------------------------------------------------------- + +.. container:: + + Newsgroup: `mozilla.dev.tech.crypto <news://news.mozilla.org/mozilla.dev.tech.crypto>`__ + +.. _task_list: + +`Task List <#task_list>`__ +~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. container:: + + #. In analyze mode, there should be an option to create a file containing a graph of the + certificate database without any information about the user's certificates (no common names, + email addresses, etc.). This file could be mailed to a mail alias to assist in finding the + source of database corruption. + #. The dbck tool should be able to repair a currupted database. There should be command-line + options and, perhaps, an interactive mode to allow determine which certificates to keep. + #. The dbck tool should be able to update a databa
\ No newline at end of file |