TDE personal information management applications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

using-chiasmus.docbook 4.6KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  1. <chapter id="chiasmus">
  2. <chapterinfo>
  3. <authorgroup>
  4. <author>
  5. <firstname>Jan-Oliver</firstname>
  6. <surname>Wagner</surname>
  7. <affiliation><address>
  8. <email>jan@intevation.de</email>
  9. </address></affiliation>
  10. </author>
  11. <author>
  12. <firstname>Till</firstname>
  13. <surname>Adam</surname>
  14. <affiliation><address>
  15. <email>till@kdab.net</email>
  16. </address></affiliation>
  17. </author>
  18. </authorgroup>
  19. <date>2005-06-30</date>
  20. <releaseinfo>1.8</releaseinfo>
  21. </chapterinfo>
  22. <title>Using the Chiasmus encryption tool</title>
  23. <sect1 id="chiasmus-preparations">
  24. <title>Preparations</title>
  25. <para>
  26. To encrypt and decrypt with Chiasmus, you need the BSI's Chiasmus
  27. command line tool for GNU/Linux. It is intended solely for use in
  28. government agencies and availabe from the BSI on request.
  29. </para>
  30. <para>
  31. When executed without parameters, the <command>chiasmus</command>
  32. program should output something like:
  33. </para>
  34. <para>
  35. <screen>
  36. Chiasmus (R) fuer Windows K 1.8.0.0
  37. Bundesamt fuer Sicherheit in der Informationstechnik
  38. Kontakt: Chiasmus@bsi.bund.de
  39. (C) 2001 - 2005
  40. [ ...]
  41. </screen>
  42. </para>
  43. <para>
  44. Version 1.8.0.0 was tested succesfully. Other versions may or may not
  45. work correctly.
  46. </para>
  47. <para>
  48. As a last preparation step a directory which will hold the key files
  49. ending in <filename>.xis</filename> has to be created, if none already exists. Usually
  50. <filename class="directory">~/.chiasmus/</filename> is used.
  51. </para>
  52. </sect1>
  53. <sect1 id="chiasmus-configuration">
  54. <title>Configuration</title>
  55. <para>
  56. Select <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure KMail
  57. </guimenuitem></menuchoice> and choose the <guilabel>Crypto-Backends</guilabel>
  58. tab on the Security page. Select the entry for <guilabel>Chiasmus</guilabel> and click
  59. <guibutton>Configure....</guibutton> to open the configuration dialog
  60. for the Chiasmus backend.
  61. </para>
  62. <para>
  63. Specify the path to the Chiasmus binary and the directory where key files are
  64. to be stored, using the file selection dialogs which open when you click the
  65. folder icons next to the path entries.
  66. </para>
  67. <para>
  68. Close the backend configuration dialog by clicking <guibutton>Ok</guibutton>
  69. and check the <guilabel>Chiasmus Checkbox</guilabel> to activate it. Then also close the main
  70. configuration dialog.
  71. </para>
  72. </sect1>
  73. <sect1 id="chiasmus-encryption">
  74. <title>Encryption</title>
  75. <para>
  76. To encrypt a message with Chiasmus, select <menuchoice><guimenu>
  77. Options</guimenu><guimenuitem>Encrypt message with chiasmus
  78. </guimenuitem></menuchoice>. A dialog comes up in which you can select
  79. the key file to use, as well as additional command line arguments to
  80. be passed to <command>chiasmus</command>.
  81. </para>
  82. <note>
  83. <para>
  84. If you want to use Chiasmus encryption regularly, you should add
  85. an icon for that option to your toolbar, using <menuchoice><guimenu>
  86. Settings</guimenu><guimenuitem>Configure toolbars</guimenuitem>
  87. </menuchoice>. Move the entry for <guilabel>Encrypt with Chiasmus
  88. </guilabel> from the left side of the dialog to the right, using the
  89. buttons between the two panes. You can then quickly enable or disable
  90. Chiasmus encryption using that toolbar button and have a visual
  91. indication of the current state.
  92. </para>
  93. </note>
  94. <note>
  95. <para>
  96. If automatic saving of backup copies of currently edited messages is
  97. enabled, you will be prompted for your Chiasmus password, if Chiamsus
  98. encryption is active.
  99. </para>
  100. </note>
  101. <para>
  102. On message sending, you will be prompted for the password. If the password
  103. is correct, the text of the message and all its attachments will be
  104. encrypted.
  105. </para>
  106. <note>
  107. <para>
  108. The other signing and encryption options are completely independent of
  109. the Chiasmus encryption. You can use those in addition to Chiasmus,
  110. &eg; to sign the message. Additional encryption, on the other hand,
  111. does not make much sense and complicates decryption for the
  112. recipients.
  113. </para>
  114. </note>
  115. </sect1>
  116. <sect1 id="chiasmus-decryption">
  117. <title>Decryption</title>
  118. <para>
  119. &kmail; and &kontact; detect messages that have been encrypted
  120. using Chiasmus and will automatically ask for the key file to use for
  121. decryption, as well as the corresponding password. If the password is correct, the
  122. message will be decrypted and displayed.
  123. </para>
  124. <para>
  125. To decrypt attachments that were encrypted using Chiasmus (&ie; those which have
  126. a file name ending in <filename>.xia</filename>), right-click on the
  127. attachment you want to decrypt and select <menuchoice><guimenuitem>Decrypt using Chiasmus
  128. </guimenuitem></menuchoice>. After you have chosen a key file to be used for decryption and
  129. entered the correct password for it, a file selection dialog will allow you
  130. to specify where the decrypted attachment should be saved.
  131. </para>
  132. </sect1>
  133. </chapter>