{"id":4446,"date":"2014-10-23T23:55:10","date_gmt":"2014-10-23T21:55:10","guid":{"rendered":"http:\/\/blog.wenzlaff.de\/?p=4446"},"modified":"2021-11-22T17:15:13","modified_gmt":"2021-11-22T16:15:13","slug":"wie-wird-truecrypt-7-1auf-einem-raspberry-pi-installiert","status":"publish","type":"post","link":"http:\/\/blog.wenzlaff.de\/?p=4446","title":{"rendered":"Wie wird Truecrypt 7.1auf einem Raspberry Pi installiert?"},"content":{"rendered":"<p><a href=\"https:\/\/de.wikipedia.org\/wiki\/TrueCrypt\" title=\"truecrypt-wiki\" target=\"_blank\" rel=\"noopener noreferrer\">Truecrypt<\/a> 7.1 kann gut wie in dieser <a href=\"https:\/\/jankarres.de\/2013\/04\/raspberry-pi-truecrypt-installieren-und-mounten\/\" title=\"truecrypt\" target=\"_blank\" rel=\"noopener noreferrer\">Anleitung<\/a> beschrieben installiert werden.<\/p>\n<p>Hier in Kurzform wie die n\u00f6tigen Packages geladen, ausgepackt und selbst compiliert werden k\u00f6nnen, da es f\u00fcr den rPi keine fertigen Packages gibt. Der compile Vorgang dauert ca. 1 Stunde, dabei darf das Terminal Fenster nicht geschlossen werden.<\/p>\n<pre class=\"lang:sh decode:true \" >sudo apt-get update\r\nsudo apt-get upgrade\r\nsudo apt-get install libfuse-dev screen\r\n\r\nwget \"https:\/\/github.com\/AuditProject\/truecrypt-verified-mirror\/raw\/master\/Source\/TrueCrypt%207.1a%20Source.tar.gz\"\r\ntar xfz \"TrueCrypt 7.1a Source.tar.gz\"\r\n\r\ncd truecrypt-7.1a-source\r\nwget ftp:\/\/ftp.rsasecurity.com\/pub\/pkcs\/pkcs-11\/v2-20\/*.h\r\n\r\nwget http:\/\/prdownloads.sourceforge.net\/wxwindows\/wxWidgets-2.8.12.tar.gz\r\ntar xfz wxWidgets-2.8.12.tar.gz\r\n\r\nmake NOGUI=1 WX_ROOT=~\/truecrypt-7.1a-source\/wxWidgets-2.8.12 wxbuild\r\nmake NOGUI=1 WXSTATIC=1\r\n\r\ncp Main\/truecrypt \/usr\/local\/bin\/\r\nsudo chmod +x \/usr\/local\/bin\/truecrypt\r\n\r\nrm -rf truecrypt-7.1a-source\/\r\nrm TrueCrypt\\ 7.1a\\ Source.tar.gz\r\n\r\ntruecrypt --version<\/pre>\n<p>Ergebnis: <code>TrueCrypt 7.1a<\/code><\/p>\n<p>Nun alle Befehle ausgeben mit:<\/p>\n<pre class=\"lang:default decode:true \" >\r\ntruecrypt --help<\/pre>\n<p>liefert die Anleitung:<\/p>\n<pre class=\"lang:default decode:true \" >\r\nSynopsis:\r\n\r\ntruecrypt [OPTIONS] COMMAND\r\ntruecrypt [OPTIONS] VOLUME_PATH [MOUNT_DIRECTORY]\r\n\r\n\r\nCommands:\r\n\r\n--auto-mount=devices|favorites\r\n Auto mount device-hosted or favorite volumes.\r\n\r\n--backup-headers[=VOLUME_PATH]\r\n Backup volume headers to a file. All required options are requested from the\r\n user.\r\n\r\n-c, --create[=VOLUME_PATH]\r\n Create a new volume. Most options are requested from the user if not specified\r\n on command line. See also options --encryption, -k, --filesystem, --hash, -p,\r\n --random-source, --quick, --size, --volume-type. Note that passing some of the\r\n options may affect security of the volume (see option -p for more information).\r\n\r\n Inexperienced users should use the graphical user interface to create a hidden\r\n volume. When using the text user interface, the following procedure must be\r\n followed to create a hidden volume:\r\n  1) Create an outer volume with no filesystem.\r\n  2) Create a hidden volume within the outer volume.\r\n  3) Mount the outer volume using hidden volume protection.\r\n  4) Create a filesystem on the virtual device of the outer volume.\r\n  5) Mount the new filesystem and fill it with data.\r\n  6) Dismount the outer volume.\r\n  If at any step the hidden volume protection is triggered, start again from 1).\r\n\r\n--create-keyfile[=FILE_PATH]\r\n Create a new keyfile containing pseudo-random data.\r\n\r\n-C, --change[=VOLUME_PATH]\r\n Change a password and\/or keyfile(s) of a volume. Most options are requested\r\n from the user if not specified on command line. PKCS-5 PRF HMAC hash\r\n algorithm can be changed with option --hash. See also options -k,\r\n --new-keyfiles, --new-password, -p, --random-source.\r\n\r\n-d, --dismount[=MOUNTED_VOLUME]\r\n Dismount a mounted volume. If MOUNTED_VOLUME is not specified, all\r\n volumes are dismounted. See below for description of MOUNTED_VOLUME.\r\n\r\n--delete-token-keyfiles\r\n Delete keyfiles from security tokens. See also command --list-token-keyfiles.\r\n\r\n--export-token-keyfile\r\n Export a keyfile from a security token. See also command --list-token-keyfiles.\r\n\r\n--import-token-keyfiles\r\n Import keyfiles to a security token. See also option --token-lib.\r\n\r\n-l, --list[=MOUNTED_VOLUME]\r\n Display a list of mounted volumes. If MOUNTED_VOLUME is not specified, all\r\n volumes are listed. By default, the list contains only volume path, virtual\r\n device, and mount point. A more detailed list can be enabled by verbose\r\n output option (-v). See below for description of MOUNTED_VOLUME.\r\n\r\n--list-token-keyfiles\r\n Display a list of all available security token keyfiles. See also command\r\n --import-token-keyfiles.\r\n\r\n--mount[=VOLUME_PATH]\r\n Mount a volume. Volume path and other options are requested from the user\r\n if not specified on command line.\r\n\r\n--restore-headers[=VOLUME_PATH]\r\n Restore volume headers from the embedded or an external backup. All required\r\n options are requested from the user.\r\n\r\n--save-preferences\r\n Save user preferences.\r\n\r\n--test\r\n Test internal algorithms used in the process of encryption and decryption.\r\n\r\n--version\r\n Display program version.\r\n\r\n--volume-properties[=MOUNTED_VOLUME]\r\n Display properties of a mounted volume. See below for description of\r\n MOUNTED_VOLUME.\r\n\r\nMOUNTED_VOLUME:\r\n Specifies a mounted volume. One of the following forms can be used:\r\n 1) Path to the encrypted TrueCrypt volume.\r\n 2) Mount directory of the volume's filesystem (if mounted).\r\n 3) Slot number of the mounted volume (requires --slot).\r\n\r\n\r\nOptions:\r\n\r\n--display-password\r\n Display password characters while typing.\r\n\r\n--encryption=ENCRYPTION_ALGORITHM\r\n Use specified encryption algorithm when creating a new volume.\r\n\r\n--filesystem=TYPE\r\n Filesystem type to mount. The TYPE argument is passed to mount(8) command\r\n with option -t. Default type is 'auto'. When creating a new volume, this\r\n option specifies the filesystem to be created on the new volume (only 'FAT'\r\n and 'none' TYPE is allowed). Filesystem type 'none' disables mounting or\r\n creating a filesystem.\r\n\r\n--force\r\n Force mounting of a volume in use, dismounting of a volume in use, or\r\n overwriting a file. Note that this option has no effect on some platforms.\r\n\r\n--fs-options=OPTIONS\r\n Filesystem mount options. The OPTIONS argument is passed to mount(8)\r\n command with option -o when a filesystem on a TrueCrypt volume is mounted.\r\n This option is not available on some platforms.\r\n\r\n--hash=HASH\r\n Use specified hash algorithm when creating a new volume or changing password\r\n and\/or keyfiles. This option also specifies the mixing PRF of the random\r\n number generator.\r\n\r\n-k, --keyfiles=KEYFILE1[,KEYFILE2,KEYFILE3,...]\r\n Use specified keyfiles when mounting a volume or when changing password\r\n and\/or keyfiles. When a directory is specified, all files inside it will be\r\n used (non-recursively). Multiple keyfiles must be separated by comma.\r\n Use double comma (,,) to specify a comma contained in keyfile's name.\r\n Keyfile stored on a security token must be specified as\r\n token:\/\/slot\/SLOT_NUMBER\/file\/FILENAME. An empty keyfile (-k \"\") disables\r\n interactive requests for keyfiles. See also options --import-token-keyfiles,\r\n --list-token-keyfiles, --new-keyfiles, --protection-keyfiles.\r\n\r\n--load-preferences\r\n Load user preferences.\r\n\r\n-m, --mount-options=OPTION1[,OPTION2,OPTION3,...]\r\n Specifies comma-separated mount options for a TrueCrypt volume:\r\n  headerbak: Use backup headers when mounting a volume.\r\n  nokernelcrypto: Do not use kernel cryptographic services.\r\n  readonly|ro: Mount volume as read-only.\r\n  system: Mount partition using system encryption.\r\n  timestamp|ts: Do not restore host-file modification timestamp when a volume\r\n   is dismounted (note that the operating system under certain circumstances\r\n   does not alter host-file timestamps, which may be mistakenly interpreted\r\n   to mean that this option does not work).\r\n See also option --fs-options.\r\n\r\n--new-keyfiles=KEYFILE1[,KEYFILE2,KEYFILE3,...]\r\n Add specified keyfiles to a volume. This option can only be used with command\r\n -C.\r\n\r\n--new-password=PASSWORD\r\n Specifies a new password. This option can only be used with command -C.\r\n\r\n-p, --password=PASSWORD\r\n Use specified password to mount\/open a volume. An empty password can also be\r\n specified (-p \"\"). Note that passing a password on the command line is\r\n potentially insecure as the password may be visible in the process list\r\n (see ps(1)) and\/or stored in a command history file or system logs.\r\n\r\n--protect-hidden=yes|no\r\n Write-protect a hidden volume when mounting an outer volume. Before mounting\r\n the outer volume, the user will be prompted for a password to open the hidden\r\n volume. The size and position of the hidden volume is then determined and the\r\n outer volume is mounted with all sectors belonging to the hidden volume\r\n protected against write operations. When a write to the protected area is\r\n prevented, the whole volume is switched to read-only mode. Verbose list\r\n (-v -l) can be used to query the state of the hidden volume protection.\r\n Warning message is displayed when a volume switched to read-only is being\r\n dismounted.\r\n\r\n--protection-keyfiles=KEYFILE1[,KEYFILE2,KEYFILE3,...]\r\n Use specified keyfiles to open a hidden volume to be protected. This option\r\n may be used only when mounting an outer volume with hidden volume protected.\r\n See also options -k and --protect-hidden.\r\n\r\n--protection-password=PASSWORD\r\n Use specified password to open a hidden volume to be protected. This option\r\n may be used only when mounting an outer volume with hidden volume protected.\r\n See also options -p and --protect-hidden.\r\n\r\n--quick\r\n Do not encrypt free space when creating a device-hosted volume. This option\r\n must not be used when creating an outer volume.\r\n\r\n--random-source=FILE\r\n Use FILE as a source of random data (e.g., when creating a volume) instead\r\n of requiring the user to type random characters.\r\n\r\n--slot=SLOT\r\n Use specified slot number when mounting, dismounting, or listing a volume.\r\n\r\n--size=SIZE\r\n Use specified size in bytes when creating a new volume.\r\n\r\n-t, --text\r\n Use text user interface. Graphical user interface is used by default if\r\n available. This option must be specified as the first argument.\r\n\r\n--token-lib=LIB_PATH\r\n Use specified PKCS #11 security token library.\r\n\r\n--volume-type=TYPE\r\n Use specified volume type when creating a new volume. TYPE can be 'normal'\r\n or 'hidden'. See option -c for more information on creating hidden volumes.\r\n\r\n-v, --verbose\r\n Enable verbose output.\r\n\r\n\r\nIMPORTANT:\r\n\r\nIf you want to use TrueCrypt, you must follow the security requirements and\r\nsecurity precautions listed in chapter 'Security Requirements and Precautions'\r\nin the TrueCrypt documentation (file 'TrueCrypt User Guide.pdf').\r\n\r\n\r\nExamples:\r\n\r\nCreate a new volume:\r\ntruecrypt -t -c\r\n\r\nMount a volume:\r\ntruecrypt volume.tc \/media\/truecrypt1\r\n\r\nMount a volume as read-only, using keyfiles:\r\ntruecrypt -m ro -k keyfile1,keyfile2 volume.tc\r\n\r\nMount a volume without mounting its filesystem:\r\ntruecrypt --filesystem=none volume.tc\r\n\r\nMount a volume prompting only for its password:\r\ntruecrypt -t -k \"\" --protect-hidden=no volume.tc \/media\/truecrypt1\r\n\r\nDismount a volume:\r\ntruecrypt -d volume.tc\r\n\r\nDismount all mounted volumes:\r\ntruecrypt -d\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Truecrypt 7.1 kann gut wie in dieser Anleitung beschrieben installiert werden. Hier in Kurzform wie die n\u00f6tigen Packages geladen, ausgepackt und selbst compiliert werden k\u00f6nnen, da es f\u00fcr den rPi keine fertigen Packages gibt. Der compile Vorgang dauert ca. 1 Stunde, dabei darf das Terminal Fenster nicht geschlossen werden. sudo apt-get update sudo apt-get upgrade &hellip; <\/p>\n<p class=\"link-more\"><a href=\"http:\/\/blog.wenzlaff.de\/?p=4446\" class=\"more-link\"><span class=\"screen-reader-text\">\u201eWie wird Truecrypt 7.1auf einem Raspberry Pi installiert?\u201c <\/span>weiterlesen<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[220,1023,1319,7],"tags":[1379,451,1754,1755,2190,1753,449],"class_list":["post-4446","post","type-post","status-publish","format-standard","hentry","category-anleitung","category-raspberry-pi","category-sicherheit-2","category-tools","tag-compilieren","tag-crypt","tag-entcrypten","tag-geheim","tag-raspberry-pi","tag-truecrypt","tag-verschluesseln"],"_links":{"self":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts\/4446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4446"}],"version-history":[{"count":0,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=\/wp\/v2\/posts\/4446\/revisions"}],"wp:attachment":[{"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4446"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.wenzlaff.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}