<!--
    SPDX-FileCopyrightText: 2000-2003 Shie Erlich <erlich@users.sourceforge.net>
    SPDX-FileCopyrightText: 2000-2003 Rafi Yanai <yanai@users.sourceforge.net>
    SPDX-FileCopyrightText: 2004-2010 Frank Schoolmeesters <codeknight@users.sourceforge.net>
    SPDX-FileCopyrightText: 2000-2022 Krusader Krew <https://krusader.org>
-->
<sect1 id="checksum">
  <title>Checksum Creation and Verification</title>
  <indexterm>
    <primary>Checksum</primary>
  </indexterm>
  <para>
    <menuchoice>
      <guimenu>File</guimenu>
      <guimenuitem>Create Checksum...</guimenuitem>
    </menuchoice>:
  &krusader; checks which tools you have
  and if those tools allow recursive operation (in case you
  selected folders), you can generate a checksum by choosing a
  checksum type from the list (<guilabel>md5</guilabel>,
  <guilabel>sha</guilabel>, &etc;). You can then save the
  checksum to a file, usually called <filename>checksum.md5</filename>
  or <filename>checksum.sha1</filename>.</para>
  <para>
    <menuchoice>
      <guimenu>File</guimenu>
      <guimenuitem>Verify Checksum...</guimenuitem>
    </menuchoice>:
  &krusader; checks if you have a tool that
  supports the type of checksum you need (from your specified
  checksum file) and displays the files that failed the checksum
  (if any).</para>
  <para>The system abstracts over different checksum mechanisms and
  Checksum Utilities. At the moment, the following checksums are
  supported: md5, sha1, sha256, sha224, sha256, sha384, sha512,
  tiger, whirlpool, cfv and crc. Please check your 
  <link linkend="konfig-dependencies">Checksum Utilities
  settings</link> before using this function.</para>
</sect1>
