From 333f46993ca5a46afe10b5d7f4a7136bebbec281 Mon Sep 17 00:00:00 2001
From: lars Table of Contents
-English version +English version
-Das erste Release der CryptoBox ist unter https://codecoop.org/projects/cryptobox/ verfügbar. +Die CryptoBox ist eine Live-CD mit der sich jeder alte Rechner in Sekundenschnelle in einen verschlüsselnden Server umwandeln lässt. Damit kannst du sensible Daten speichern, ohne dass du etwas über Kryptografie wissen musst.
--Die CryptoBox ist eine Live-CD mit der sich jeder alte Rechner in Sekundenschnelle in einen verschlüsselnden Server umwandeln lässt. Damit kannst du sensible Daten speichern, ohne dass du etwas über Kryptografie wissen musst. +Damit sprechen wir hauptsächlich Menschen an, die ihre Daten (Ideen, Werke, Geheimnisse ...) auf einfachem Wege vor unbefugtem Zugriff sichern wollen. Kurzum: Privatsphäre, als grundlegendes Menschenrecht sichern! +
++Die Bedienung erfolgt vollständig per Webbrowser. Wirf einen Blick auf die ScreenShots. +
++Nutze das Web-Interface der CryptoBox in deiner Lieblingssprache: +
++einige eher technische Details:
-System | Debian GNU/Linux-basierte Live-CD |
benötigter Computer | "ausrangierter" PC (i386 ab p1 mind. 32MB RAM) @@ -45,48 +61,71 @@ Die CryptoBox ist eine |
Benutzerschnittstelle | per Browser bedienbares Web-Interface |
Verschlüsselung | AES via device-mapper |
-Das Web-Interface der CryptoBox ünterstützt derzeit folgende Sprachen: +Wenn du die CryptoBox benutzen möchtest, kannst du ein aktuelles Image herunterladen und auf eine CD brennen.
--Du kannst gern weitere Übersetzungen in andere Sprachen hinzufügen (idealerweise utf-encodiert). +
+Denk bitte daran, dass dies ein Open Source Projekt ist! Wir bitten dich deshalb, deine Erfahrungen (vor allem auch negative) im Umgang mit der CryptoBox, mit uns zu teilen. So können wir etwaige Fehler schneller beheben und letztlich der Community ein besseres "Produkt" bereitstellen.
--Das Nutzerhandbuch ist unter CryptoBoxUser verfügbar. +Wir wollen dir, soweit wir können, beim Umgang mit der CryptoBox helfen.
-
-Beteilige dich an der Entwicklung der CryptoBox und werde reich und schön! ;)
-Nee im Ernst, wir freuen uns über jeden partizipierenden Menschen. Du wirst in einem entspannten Team reichlich Erfahrungen sammeln, eine nützliche Sache voranbringen und - wer weiß - vielleicht macht dich das auch schön. Schreib eine Mail an cryptobox[at]systemausfall.org und hab Spaß.
+Du bist nicht nur Konsument. Durch deine Taten kannst du anderen Menschen helfen.
+
-Probleme und Anregungen kannst du in unserer Fehlerdatenbank melden.
+Beteilige dich an der Entwicklung der CryptoBox und werde reich und schön! ;)
+Nee im Ernst, wir freuen uns über jeden partizipierenden Menschen. Du wirst in einem entspannten Team reichlich Erfahrungen sammeln, eine nützliche Sache voranbringen und - wer weiß - vielleicht macht dich das auch schön.
+Trage dich einfach in die Entwickler-Mailingliste ein: cryptobox-dev-subscribe@lists.systemausfall.org und hab Spaß.
-Die englischsprachige Entwickler-Doku findest du unter CryptoBoxDev. +Das Mailinglisten-Archiv ist verfügbar unter https://systemausfall.org/mail-archive.
-Die Quell-Daten kannst du hier begutachten. +Die englischsprachige Entwickler-Doku findest du unter CryptoBoxDev. Dort wird detailiert beschrieben, wie du die Entwicklungsumgebung der CryptoBox verwenden kannst.
-Für allgemeine Fragen, schreibe eine Email an cryptobox[at]systemausfall.org. +Unsere Enwticklungspläne kannst du dir in der Roadmap anschauen.
+Vielen Dank an alle HelferInnen - ihr macht die CryptoBox erst richtig rund! :) +
+
+Ein feines Projekt! +
++Das würde ich gerne in meinen Server integrieren. +Ein Howto für Debian wäre nicht schlecht. +
+++den Rest der Diskussion findest du in Ticket #84* +
+
diff --git a/doc/html/de/CryptoBoxDev.html b/doc/html/de/CryptoBoxDev.html index 33fc754..98072d8 100644 --- a/doc/html/de/CryptoBoxDev.html +++ b/doc/html/de/CryptoBoxDev.html @@ -8,99 +8,86 @@
-Navigation: ( CryptoBox/de, CryptoBox/en) +Navigation: ( CryptoBox/de, CryptoBox/en)
The following pages are written for developers only.
-Users of the CryptoBox should read CryptoBoxUser instead.
+Users of the CryptoBox should read CryptoBoxUser instead.
You may browse the source code.
-We are waiting for your emails to cryptobox[at]systemausfall.org. +Join the mailing list: cryptobox-dev-subscribe@lists.systemausfall.org.
-Please use our issue tracker, if you discover problems: https://systemausfall.org/trac/cryptobox/newticket +If you think you found a bug or you get an error message, please help us to fix the problem and file a ticket (a bug report). Follow these steps:
- +-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-The base system of the CryptoBox Live-CD is created by dfsbuild. +The base system of the CryptoBox Live-CD is created by dfsbuild.
It is recommended to use some kind of caching tool for the retrieval of the debian packages (e.g.: apt-cacher, apt-proxy or approx). This saves a lot of bandwidth and time. @@ -37,22 +37,25 @@ The documentation for Debian Administration: Getting in deep with dfsbuild
-The linux kernel for the CryptoBox is compiled statically. If you want to change it, you could follow this steps: +The linux kernel for the CryptoBox is compiled statically. If you want to change it, you could follow this steps:
+See source:trunk/hints/kernel-build.txt for more details. +
+Qemu is a portable system emulator. It is a convenient tool to ease the development workflow, as you do not need to burn LiveCDs for testing.
-We tried some other LiveCDs before we decided to use dfsbuild. The following pages describe their advantages and disadvantages as the base system for the CryptoBox: +We tried some other LiveCDs before we decided to use dfsbuild. The following pages describe their advantages and disadvantages as the base system for the CryptoBox:
-diff --git a/doc/html/de/CryptoBoxDevCustomBuild.html b/doc/html/de/CryptoBoxDevCustomBuild.html index 6607d93..1abfd92 100644 --- a/doc/html/de/CryptoBoxDevCustomBuild.html +++ b/doc/html/de/CryptoBoxDevCustomBuild.html @@ -8,29 +8,29 @@
-Navigation: ( CryptoBoxDev, CryptoBoxDevBackground, CryptoBoxDevPreparation, CryptoBoxDevWorkFlow) +Navigation: ( CryptoBoxDev, CryptoBoxDevBackground, CryptoBoxDevPreparation, CryptoBoxDevWorkFlow)
-The following sections are useful, if you want to change the default settings of your personal CryptoBox development environment. +The following sections are useful, if you want to change the default settings of your personal CryptoBox development environment.
-You should have completed the steps described in CryptoBoxDevPreparation. +You should have completed the steps described in CryptoBoxDevPreparation.
-Some settings regarding the building, configuring and validating of the CryptoBox can be found in etc-defaults.d/cbox-dev.conf. +Some settings regarding the building, configuring and validating of the CryptoBox can be found in etc-defaults.d/cbox-dev.conf.
If you want to change any of them, you should do the following: @@ -56,13 +56,13 @@ If you want to change any of them, you should do the following:
-The file ssh_config is used to establish a connection to a running CryptoBox system. +The file ssh_config is used to establish a connection to a running CryptoBox system.
It can be necessary to change these settings, if:
-If you want to change some settings, you should do the following:
@@ -70,7 +70,7 @@ If you want to change some settings, you should do the following:-The file etc-defauolts.d/qemu-ifup is used for the CryptoBox emulation with qemu. See man qemu for details. +The file etc-defauolts.d/qemu-ifup is used for the CryptoBox emulation with qemu. See man qemu for details.
If you want to change some settings, you should do the following: diff --git a/doc/html/de/CryptoBoxDevCustomConfigure.html b/doc/html/de/CryptoBoxDevCustomConfigure.html index 9b93359..67d3fb1 100644 --- a/doc/html/de/CryptoBoxDevCustomConfigure.html +++ b/doc/html/de/CryptoBoxDevCustomConfigure.html @@ -8,26 +8,26 @@
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-You may change nearly every aspect of the CryptoBox by using the custom configuration hook directory. +You may change nearly every aspect of the CryptoBox by using the custom configuration hook directory.
-Any script inside of this directory will be executed after the default configuration procedure (see CryptoBoxDevWorkFlow). +Any script inside of this directory will be executed after the default configuration procedure (see CryptoBoxDevWorkFlow).
The order of execution is defined by the names of the scripts (alphabetically).
@@ -48,7 +48,7 @@ The examples in con
set_default_language set the default language
set_default_timeout set the default idle time for automatic unmounting
set_hostname change the default hostname
- set_root_pw change the password of root (only useful for a development CryptoBox)
+ set_root_pw change the password of root (only useful for a development CryptoBox)
import_authorized_keys upload a ssh key for passwordless access to a development CryptoBox
diff --git a/doc/html/de/CryptoBoxDevKnownProblems.html b/doc/html/de/CryptoBoxDevKnownProblems.html
index 787bc2f..861b783 100644
--- a/doc/html/de/CryptoBoxDevKnownProblems.html
+++ b/doc/html/de/CryptoBoxDevKnownProblems.html
@@ -8,16 +8,18 @@
set_scan_devices where to look for usable harddisks
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
This happens under certain circumstances. We do not know a solution for this problem.
++Try to downgrade cdebootstrap to v0.3.4 (for debian: apt-get install cdebootstrap/stable). This problem occours at least up to v0.3.8 of cdebootstrap. +
diff --git a/doc/html/de/CryptoBoxDevPreparation.html b/doc/html/de/CryptoBoxDevPreparation.html index 64be90c..849b714 100644 --- a/doc/html/de/CryptoBoxDevPreparation.html +++ b/doc/html/de/CryptoBoxDevPreparation.html @@ -8,19 +8,19 @@
-Navigation: ( CryptoBoxDev, CryptoBoxDevCustomBuild, CryptoBoxDevWorkFlow) +Navigation: ( CryptoBoxDev, CryptoBoxDevCustomBuild, CryptoBoxDevWorkFlow)
-If you want to use qemu to test your CryptoBox in a virtual environment, then you will need the tun/tap kernel feature. +If you want to use qemu to test your CryptoBox in a virtual environment, then you will need the tun/tap kernel feature.
CONFIG_TUN=m
-Now you can start to pariticipate in the development of the CryptoBox or simply customize your own CryptoBox-LiveCD. +Now you can start to pariticipate in the development of the CryptoBox or simply customize your own CryptoBox-LiveCD.
-See CryptoBoxDevWorkFlow for details of how to use the developer's tools of the CryptoBox. +See CryptoBoxDevWorkFlow for details of how to use the developer's tools of the CryptoBox.
-CryptoBoxDevCustomBuild shows some examples for local customizations of the CryptoBox. +CryptoBoxDevCustomBuild shows some examples for local customizations of the CryptoBox.
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-The validation feature helps you to check the programming logic of the CryptoBox. A lot of test cases are defined to verify as many functions of the CryptoBox as possible. +The validation feature helps you to check the programming logic of the CryptoBox. A lot of test cases are defined to verify as many functions of the CryptoBox as possible.
The requests are processed with curl.
@@ -33,7 +33,7 @@ The requests are processed with
-The current state of the CryptoBox is represented by ten single values (e.g.: box is configured, IP of the box, current language setting, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case.
+The current state of the CryptoBox is represented by ten single values (e.g.: box is configured, IP of the box, current language setting, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case.
Similar test cases are pooled into test groups (e.g.: initialization, configuration and mounting).
@@ -57,7 +57,7 @@ Every test consists of the following files:
input.curl | the configuration file for the curl request - |
output | the predicted state of the CryptoBox after the call + |
output | the predicted state of the CryptoBox after the call |
description | a short description of the test (will be used for the summary) |
delay | [optional] time to wait after this test |
-Navigation: ( CryptoBoxDev, CryptoBoxDevCustomConfigure, CryptoBoxDevPreparation) +Navigation: ( CryptoBoxDev, CryptoBoxDevCustomConfigure, CryptoBoxDevPreparation)
-You should have completed the steps described in CryptoBoxDevPreparation. +You should have completed the steps described in CryptoBoxDevPreparation.
The following steps can be executed in the order of their appearance.
-Usually there is no need to repeat the whole process, after you changed some parts of the CryptoBox. Especially the first step (building of the base system with dfsbuild) may usually be skipped. +Usually there is no need to repeat the whole process, after you changed some parts of the CryptoBox. Especially the first step (building of the base system with dfsbuild) may usually be skipped.
Every step of the building process must be executed as root. @@ -54,7 +55,7 @@ Run scripts/cbox-build.sh dfsbuild to create the base system for the Live The result can be found in _builddir/cd1/image.
-If you do not want to use the apt-cacher to save bandwidth and time, then you should modify the mirror-setting in dfs-cbox.conf (see CryptoBoxDevCustomBuild for details). +If you do not want to use the apt-cacher to save bandwidth and time, then you should modify the mirror-setting in dfs-cbox.conf (see CryptoBoxDevCustomBuild for details).
@@ -86,18 +87,18 @@ Do it manually: (change the dev setting according to your setup).
-Let the script do it for you: scripts/cbox-build.sh burn (maybe you have to change the CDWRITER setting in cbox-dev.conf - see CryptoBoxDevCustomBuild). +Let the script do it for you: scripts/cbox-build.sh burn (maybe you have to change the CDWRITER setting in cbox-dev.conf - see CryptoBoxDevCustomBuild).
Of course, it is not wise to use CD-R media. CD-RW consume less resources.
-This section is only useful for developers, who want to improve or change the CryptoBox system. +This section is only useful for developers, who want to improve or change the CryptoBox system.
-If you modified the perl- or shell-scripts of the CryptoBox, then you can check for syntax errors by running them in a chroot environment. Be careful: you have access to all ressources of your computer, while you are working within a chroot environment - so you can easily repartition your real disk ... +If you modified the perl- or shell-scripts of the CryptoBox, then you can check for syntax errors by running them in a chroot environment. Be careful: you have access to all ressources of your computer, while you are working within a chroot environment - so you can easily repartition your real disk ...
To start a chroot environment, you can execute scripts/cbox-dev.sh chroot. @@ -107,7 +108,7 @@ For more intensive tests, you may use qemu (see below) or burn real LiveC
-The processor emulator qemu allows you test the CryptoBox in a virtual environment, that is completely separated from your real computer's resources. It is the tool of choice, if you do nat have a real computer around for testing. +The processor emulator qemu allows you test the CryptoBox in a virtual environment, that is completely separated from your real computer's resources. It is the tool of choice, if you do nat have a real computer around for testing.
Beware - there are some problems, when using qemu: @@ -120,10 +121,10 @@ To start a qemu emulation of the iso image, you may type:
scripts/cbox-dev.sh qemu
-This section is only useful for developers, who want to develop on a running CryptoBox system (emulated or real). +This section is only useful for developers, who want to develop on a running CryptoBox system (emulated or real).
-You may access the CryptoBox directly or you can use ssh to open a remote session: +You may access the CryptoBox directly or you can use ssh to open a remote session:
./cbox-dev.sh ssh
-Type scripts/cbox-dev.sh diff to see the changes, you made on the running CryptoBox system. +Type scripts/cbox-dev.sh diff to see the changes, you made on the running CryptoBox system.
Type scripts/cbox-dev.sh merge to merge these changes to your local working copy.
--Alternatively you may also upload a new version of your local working copy to the running CryptoBox system. +Alternatively you may also upload a new version of your local working copy to the running CryptoBox system.
-Type scripts/cbox-dev.sh upload - beware: all recent changes you made to the running CryptoBox system, are lost. +Type scripts/cbox-dev.sh upload - beware: all recent changes you made to the running CryptoBox system, are lost. +
++Once you finished your development, you surely want to make a new release. Please read the instructions in the releas-policy.txt it will save you a lot of time! Then you basically just have to run scripts/cbox-build.sh release and get yourself a good coffee. After the command has finished you'll see the releasefiles in _buildir.
-Navigation: ( CryptoBox/de) +Navigation: ( CryptoBox/de)
-Die folgenden Seiten beschreiben die Nutzung der CryptoBox. +Die folgenden Seiten beschreiben die Nutzung der CryptoBox.
-Die online-Version dieses Handbuchs ist ein Wiki. Das bedeutet, dass du diese Seiten verändern kannst. Falls du also Fragen oder Anregungen hast, schreibe bitte deine Anmerkungen in den Kommentar-Abschnitt am Ende der jeweiligen Seite. Die Entwickler werden deine Fragen beantworten und das Handbuch schnellstmöglich aktualisieren. Auf diese Art und Weise kannst du die Nutzbarkeit der CryptoBox für alle Nutzer verbessern! +Die online-Version dieses Handbuchs ist ein Wiki. Das bedeutet, dass du diese Seiten verändern kannst. Falls du also Fragen oder Anregungen hast, schreibe bitte deine Anmerkungen in den Kommentar-Abschnitt am Ende der jeweiligen Seite. Die Entwickler werden deine Fragen beantworten und das Handbuch schnellstmöglich aktualisieren. Auf diese Art und Weise kannst du die Nutzbarkeit der CryptoBox für alle Nutzer verbessern!
-Die online-Version dieses Handbuchs befindet sich unter https://systemausfall.org/trac/cryptobox/wiki/CryptoBoxUser/de.
diff --git a/doc/html/de/CryptoBoxUserConfiguration.html b/doc/html/de/CryptoBoxUserConfiguration.html index fccc749..5ee43de 100644 --- a/doc/html/de/CryptoBoxUserConfiguration.html +++ b/doc/html/de/CryptoBoxUserConfiguration.html @@ -8,44 +8,60 @@-Navigation: ( CryptoBoxUser/de) +Navigation: ( CryptoBoxUser/de)
-Alle Funktionen der CryptoBox können durch das komfortable Web-Interface bedient werden. Zur Erst-Einrichtung der CryptoBox folge einfach den folgenden Schritten. +Alle Funktionen der CryptoBox können durch das komfortable Web-Interface bedient werden. Zur Erst-Einrichtung der CryptoBox folge einfach den folgenden Schritten.
-Falls du in Eile bist, kannst du das Vorwort überspringen. +Falls du in Eile bist, kannst du das Vorwort überspringen.
-Die Initialisierung erklärt die Einrichtung der Festplatte. Dieser Schritt ist nur bei der ersten Einrichtung oder nach einem Festplattenwechsel notwendig. +Die Initialisierung erklärt die Einrichtung der Festplatte. Dieser Schritt ist nur bei der ersten Einrichtung oder nach einem Festplattenwechsel notwendig.
-Im Konfigurations-Abschnitt werden die verfügbaren Einstellungen der CryptoBox beschrieben. Hier kannst du beispielsweise die Sprache des Web-Interfaces oder die Netzwerkadresse deiner CryptoBox einstellen. +Im Konfigurations-Abschnitt werden die verfügbaren Einstellungen der CryptoBox beschrieben. Hier kannst du beispielsweise die Sprache des Web-Interfaces oder die Netzwerkadresse deiner CryptoBox einstellen.
-Vergiss nicht, auch den Hinweise/Fallstricke-Abschnitt zu lesen. +Vergiss nicht, auch den Hinweise/Fallstricke-Abschnitt zu lesen.
-Du bist den Anweisungen aus CryptoBoxUserGettingStarted gefolgt und sitzt nun vor deinem Arbeits-Rechner. Nun kannst du in deinem Web-Browser das Web-Interface der CryptoBox ansteuern: https://192.168.0.23. +Du bist den Anweisungen aus CryptoBoxUserGettingStarted gefolgt und sitzt nun vor deinem Arbeits-Rechner. Nun kannst du in deinem Web-Browser das Web-Interface der CryptoBox ansteuern: https://192.168.0.23.
-Bevor du Daten auf deiner CryptoBox speichern kannst, muss die Festplatte mit einem verschlüsselten Dateisystem versehen werden. Das klingt kompliziert, ist jedoch mit einem Klick erledigt. :) +Bevor du Daten auf deiner CryptoBox speichern kannst, muss die Festplatte mit einem verschlüsselten Dateisystem versehen werden. Das klingt kompliziert, ist jedoch mit einem Klick erledigt. :)
@@ -55,17 +71,17 @@ Klicke auf Initialisierung in der Menü-Zeile. Jetzt wirst du zur Eingabe zweier Passworte aufgefordert (jeweils mit Wiederholung - zum Training deiner Tipp-Fertigkeiten ;)).
Das war es dann auch schon. Kryptographie war wohl nie einfacher zu verwenden, oder? ;) @@ -78,7 +94,7 @@ Der Initialisierungsvorgang läuft nun im Hintergrund ab und wird nach wenigen M Im Gegensatz zur Initialisierung, die nur einmal durchgeführt werden muss, kannst du die Konfiguration jederzeit deinen Wünschen anpassen. Dazu klickst du einfach auf Konfiguration in der Menü-Zeile des Web-Interfaces. Nun wird dir ein Formular mit vier Feldern präsentiert:
-Das ist alles - deine CryptoBox ist jetzt bereit für die tägliche Nutzung! +Das ist alles - deine CryptoBox ist jetzt bereit für die tägliche Nutzung!
-zurück zu CryptoBoxUser +zurück zu CryptoBoxUser
-Navigation: ( CryptoBoxUser/de, CryptoBoxUserConfiguration/de) +Navigation: ( CryptoBoxUser/de, CryptoBoxUserConfiguration/de)
Du kannst dein verschlüsseltes Dateisystem mit folgenden Schritten aktivieren:
--Nun ist das verschlüsselte Dateisystem verfügbar. Um es zu nutzen, suche in deiner Netzwerkumgebung nach der Netzwerk-Adresse deiner CryptoBox (Voreinstellung: 192.168.0.23). Nun kannst du das Netzlaufwerk wie üblich verwenden. +Nun ist das verschlüsselte Dateisystem verfügbar. Um es zu nutzen, suche in deiner Netzwerkumgebung nach der Netzwerk-Adresse deiner CryptoBox (Voreinstellung: 192.168.0.23). Nun kannst du das Netzlaufwerk wie üblich verwenden.
-Trage unter Pfad die Adresse des Verzeichnisse der CryptoBox ein, auf das du zugreifen willst (Standard: \\192.168.0.23\public). Soll die Verbindung beim jedem Start von Windows wiederhergestellt werden, aktiviere Verbindung beim Start wiederherstellen. +Trage unter Pfad die Adresse des Verzeichnisse der CryptoBox ein, auf das du zugreifen willst (Standard: \\192.168.0.23\public). Soll die Verbindung beim jedem Start von Windows wiederhergestellt werden, aktiviere Verbindung beim Start wiederherstellen.
Nun kannst du auf das verschlüsselte Dateisystem wie jedes andere Laufwerk benutzen.
-Du kannst das verschlüsselte Dateisystem abschalten, indem du in der Menü-Zeile des Web-Interfaces der CryptoBox auf Deaktivierung der Crypto-Daten klickst. +Du kannst das verschlüsselte Dateisystem abschalten, indem du in der Menü-Zeile des Web-Interfaces der CryptoBox auf Deaktivierung der Crypto-Daten klickst.
Deine Daten sind nun wieder vor jedem Zugriff geschützt. @@ -81,22 +96,22 @@ Falls dein CryptoBox-Rechner relativ neu ist (ungefähr ab Baujahr 02000), wird
-Falls du deine Daten wirklich schnell vor neugierigen Augen schützen musst, dann ziehe einfach den Stecker der CryptoBox. Dies ist nicht besonders sauber und kann (in sehr seltenen Ausnahmefällen) geöffnete Dateien beschädigen. Es ist jedoch die schnellste Methode zur Sicherung deiner Daten vor unbefugtem Zugriff. +Falls du deine Daten wirklich schnell vor neugierigen Augen schützen musst, dann ziehe einfach den Stecker der CryptoBox. Dies ist nicht besonders sauber und kann (in sehr seltenen Ausnahmefällen) geöffnete Dateien beschädigen. Es ist jedoch die schnellste Methode zur Sicherung deiner Daten vor unbefugtem Zugriff.
-zurück zu CryptoBoxUser +zurück zu CryptoBoxUser
Erscheint diese Fehlermeldung, hast du dich beim Start von Windows nicht angemeldet bzw. das Anmeldefenster mit der Taste Esc (Escape) verschwinden lassen. Klicke auf Start und Abmelden und melde dich neu an - sobald das Anmeldefenster erscheint, klicke auf OK:
diff --git a/doc/html/de/CryptoBoxUserGettingStarted.html b/doc/html/de/CryptoBoxUserGettingStarted.html index 3c74e14..04ffe7a 100644 --- a/doc/html/de/CryptoBoxUserGettingStarted.html +++ b/doc/html/de/CryptoBoxUserGettingStarted.html @@ -8,31 +8,50 @@
-Navigation: ( CryptoBoxUser/de, CryptoBoxUserConfiguration/de) +Navigation: ( CryptoBoxUser/de, CryptoBoxUserConfiguration/de, CryptoBoxUserDailyUse/de)
-Die CryptoBox ist schnell aufgebaut: +Die CryptoBox ist schnell aufgebaut:
Wenn der Computer jetzt von der CD startet, hast du alle Anforderungen erfüllt.
@@ -40,10 +59,10 @@ Wenn der Computer jetzt von der CD startet, hast du alle Anforderungen erfüllt. Du kannst nun zu deinem Arbeits-Rechner in demselben Netzwerk gehen und "https://192.168.0.23" ansurfen. Dort sollte die CryptoBox-Konfigurationsseite erscheinen. Ist doch kinderleicht, oder?-Die weiteren Schritte werden unter CryptoBoxUserConfiguration beschrieben. +Die weiteren Schritte werden unter CryptoBoxUserConfiguration beschrieben.
-deutsche Version +deutschsprachige Version
-The first release of the CryptoBox is available at https://codecoop.org/projects/cryptobox/
+The CryptoBox is a Debian/Linux based live-cd. This CD boots up, starting a secure fileserver. Even non-technical users are able to store their data on its encrypted harddisk. There is no special knowledge about cryptography or servers required at all.
+The CryptoBox is fully controllable via your web browser. Have a look at the ScreenShots.
-The CryptoBox is a Debian/Linux based live-cd. This CD boots up, starting a secure fileserver. Even non-technical users are able to store their data on its encrypted harddisk. There is no special knowledge about cryptography or servers required at all. +Use the web interface of the CryptoBox in your favourite language: +
++some rather technical details:
-system | Debian/Linux based Live-CD |
needed hardware | "outdated" PC (i386 p1-100 32MB RAM minimum) @@ -45,44 +56,98 @@ The CryptoBox is a Debian/Lin |
userinterface | fully remote controlled via webbrowser |
encryption | AES via device-mapper |
-The web interface of the CryptoBox supports the following languages: +We do our best to help you using the CryptoBox.
--Feel free to contribute a translation for another language (preferably utf-encoded). +
+You are not just a consumer. You can help others with your knowledge. +
--The user documentation has its home at CryptoBoxUser. +
-Take a look at the developer's documentation at CryptoBoxDev. +Let me just make sure I understand correctly. +The protected data is encrypted on the Cryptobox drive, +but is available in clear on the network, between the cryptobox and the user. Right?
++-Report bugs to https://systemausfall.org/trac/cryptobox/newticket. +see the whole discussion at ticket #83*
+
-Browse the source code. +Do you have suggestions on how to secure the file transfer in a platform independent way?
-Anything else? Write us an email: cryptobox[at]systemausfall.org +Perhaps the simplest thing to do would be make (one version of) CryptoBox be a https (secure web server). +(Instead of, or in addition to, being a samba file server).
--
+All https servers use encryption when they download files, right? +So another (dynamic) web page on that server lists all of that user's files. Each one is hotlinked, so the user simply clicks on it to download / view it. +
++Perhaps a bit kludgy, but I think even unexperienced users could figure it out. +
++++see the whole discussion at ticket #83*, too +
+
+What happens when there are multiple hard drives in the machine? Will it erase all? Does it combine them to one share with something like raid or lvm, or will they be mountable as different shares? I'd try myself, but I currently only have one free hdd to test with. +btw, wonderful tool, keep up the good work, and tell us if you need more testers :-) +
++++If there are multiple harddisks available, then it will use only the first.
+
+We are going to implement an interface to manually partition harddisks and choose more than one of them for (seperated) encrypted containers. This feature should be available in the next release (v0.3).
+If you would like to help us (e.g. by testing), then you could subscribe to the mailing list. +
+Could the hdd be external usb or firewire? +
+++yes - version 2.1 should support usb drives (firewire will work with 3.0) +
+
diff --git a/doc/html/en/CryptoBoxDev.html b/doc/html/en/CryptoBoxDev.html index ced5e8a..4690ee3 100644 --- a/doc/html/en/CryptoBoxDev.html +++ b/doc/html/en/CryptoBoxDev.html @@ -8,99 +8,86 @@
-Navigation: ( CryptoBox/de, CryptoBox/en) +Navigation: ( CryptoBox/de, CryptoBox/en)
The following pages are written for developers only.
-Users of the CryptoBox should read CryptoBoxUser instead.
+Users of the CryptoBox should read CryptoBoxUser instead.
You may browse the source code.
-We are waiting for your emails to cryptobox[at]systemausfall.org. +Join the mailing list: cryptobox-dev-subscribe@lists.systemausfall.org.
-Please use our issue tracker, if you discover problems: https://systemausfall.org/trac/cryptobox/newticket +If you think you found a bug or you get an error message, please help us to fix the problem and file a ticket (a bug report). Follow these steps:
- +-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-The base system of the CryptoBox Live-CD is created by dfsbuild. +The base system of the CryptoBox Live-CD is created by dfsbuild.
It is recommended to use some kind of caching tool for the retrieval of the debian packages (e.g.: apt-cacher, apt-proxy or approx). This saves a lot of bandwidth and time. @@ -37,22 +37,25 @@ The documentation for Debian Administration: Getting in deep with dfsbuild
-The linux kernel for the CryptoBox is compiled statically. If you want to change it, you could follow this steps: +The linux kernel for the CryptoBox is compiled statically. If you want to change it, you could follow this steps:
+See source:trunk/hints/kernel-build.txt for more details. +
+Qemu is a portable system emulator. It is a convenient tool to ease the development workflow, as you do not need to burn LiveCDs for testing.
-We tried some other LiveCDs before we decided to use dfsbuild. The following pages describe their advantages and disadvantages as the base system for the CryptoBox: +We tried some other LiveCDs before we decided to use dfsbuild. The following pages describe their advantages and disadvantages as the base system for the CryptoBox:
-diff --git a/doc/html/en/CryptoBoxDevCustomBuild.html b/doc/html/en/CryptoBoxDevCustomBuild.html index b975168..f364dbe 100644 --- a/doc/html/en/CryptoBoxDevCustomBuild.html +++ b/doc/html/en/CryptoBoxDevCustomBuild.html @@ -8,29 +8,29 @@
-Navigation: ( CryptoBoxDev, CryptoBoxDevBackground, CryptoBoxDevPreparation, CryptoBoxDevWorkFlow) +Navigation: ( CryptoBoxDev, CryptoBoxDevBackground, CryptoBoxDevPreparation, CryptoBoxDevWorkFlow)
-The following sections are useful, if you want to change the default settings of your personal CryptoBox development environment. +The following sections are useful, if you want to change the default settings of your personal CryptoBox development environment.
-You should have completed the steps described in CryptoBoxDevPreparation. +You should have completed the steps described in CryptoBoxDevPreparation.
-Some settings regarding the building, configuring and validating of the CryptoBox can be found in etc-defaults.d/cbox-dev.conf. +Some settings regarding the building, configuring and validating of the CryptoBox can be found in etc-defaults.d/cbox-dev.conf.
If you want to change any of them, you should do the following: @@ -56,13 +56,13 @@ If you want to change any of them, you should do the following:
-The file ssh_config is used to establish a connection to a running CryptoBox system. +The file ssh_config is used to establish a connection to a running CryptoBox system.
It can be necessary to change these settings, if:
-If you want to change some settings, you should do the following:
@@ -70,7 +70,7 @@ If you want to change some settings, you should do the following:-The file etc-defauolts.d/qemu-ifup is used for the CryptoBox emulation with qemu. See man qemu for details. +The file etc-defauolts.d/qemu-ifup is used for the CryptoBox emulation with qemu. See man qemu for details.
If you want to change some settings, you should do the following: diff --git a/doc/html/en/CryptoBoxDevCustomConfigure.html b/doc/html/en/CryptoBoxDevCustomConfigure.html index c823caf..536ae8a 100644 --- a/doc/html/en/CryptoBoxDevCustomConfigure.html +++ b/doc/html/en/CryptoBoxDevCustomConfigure.html @@ -8,26 +8,26 @@
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-You may change nearly every aspect of the CryptoBox by using the custom configuration hook directory. +You may change nearly every aspect of the CryptoBox by using the custom configuration hook directory.
-Any script inside of this directory will be executed after the default configuration procedure (see CryptoBoxDevWorkFlow). +Any script inside of this directory will be executed after the default configuration procedure (see CryptoBoxDevWorkFlow).
The order of execution is defined by the names of the scripts (alphabetically).
@@ -48,7 +48,7 @@ The examples in con
set_default_language set the default language
set_default_timeout set the default idle time for automatic unmounting
set_hostname change the default hostname
- set_root_pw change the password of root (only useful for a development CryptoBox)
+ set_root_pw change the password of root (only useful for a development CryptoBox)
import_authorized_keys upload a ssh key for passwordless access to a development CryptoBox
diff --git a/doc/html/en/CryptoBoxDevKnownProblems.html b/doc/html/en/CryptoBoxDevKnownProblems.html
index abe55bd..3dcc08e 100644
--- a/doc/html/en/CryptoBoxDevKnownProblems.html
+++ b/doc/html/en/CryptoBoxDevKnownProblems.html
@@ -8,16 +8,18 @@
set_scan_devices where to look for usable harddisks
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
This happens under certain circumstances. We do not know a solution for this problem.
++Try to downgrade cdebootstrap to v0.3.4 (for debian: apt-get install cdebootstrap/stable). This problem occours at least up to v0.3.8 of cdebootstrap. +
diff --git a/doc/html/en/CryptoBoxDevPreparation.html b/doc/html/en/CryptoBoxDevPreparation.html index e8a78d7..a5e9ba8 100644 --- a/doc/html/en/CryptoBoxDevPreparation.html +++ b/doc/html/en/CryptoBoxDevPreparation.html @@ -8,19 +8,19 @@
-Navigation: ( CryptoBoxDev, CryptoBoxDevCustomBuild, CryptoBoxDevWorkFlow) +Navigation: ( CryptoBoxDev, CryptoBoxDevCustomBuild, CryptoBoxDevWorkFlow)
-If you want to use qemu to test your CryptoBox in a virtual environment, then you will need the tun/tap kernel feature. +If you want to use qemu to test your CryptoBox in a virtual environment, then you will need the tun/tap kernel feature.
CONFIG_TUN=m
-Now you can start to pariticipate in the development of the CryptoBox or simply customize your own CryptoBox-LiveCD. +Now you can start to pariticipate in the development of the CryptoBox or simply customize your own CryptoBox-LiveCD.
-See CryptoBoxDevWorkFlow for details of how to use the developer's tools of the CryptoBox. +See CryptoBoxDevWorkFlow for details of how to use the developer's tools of the CryptoBox.
-CryptoBoxDevCustomBuild shows some examples for local customizations of the CryptoBox. +CryptoBoxDevCustomBuild shows some examples for local customizations of the CryptoBox.
-Navigation: ( CryptoBoxDev) +Navigation: ( CryptoBoxDev)
-The validation feature helps you to check the programming logic of the CryptoBox. A lot of test cases are defined to verify as many functions of the CryptoBox as possible. +The validation feature helps you to check the programming logic of the CryptoBox. A lot of test cases are defined to verify as many functions of the CryptoBox as possible.
The requests are processed with curl.
@@ -33,7 +33,7 @@ The requests are processed with
-The current state of the CryptoBox is represented by ten single values (e.g.: box is configured, IP of the box, current language setting, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case.
+The current state of the CryptoBox is represented by ten single values (e.g.: box is configured, IP of the box, current language setting, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case.
Similar test cases are pooled into test groups (e.g.: initialization, configuration and mounting).
@@ -57,7 +57,7 @@ Every test consists of the following files:
input.curl | the configuration file for the curl request - |
output | the predicted state of the CryptoBox after the call + |
output | the predicted state of the CryptoBox after the call |
description | a short description of the test (will be used for the summary) |
delay | [optional] time to wait after this test |
-Navigation: ( CryptoBoxDev, CryptoBoxDevCustomConfigure, CryptoBoxDevPreparation) +Navigation: ( CryptoBoxDev, CryptoBoxDevCustomConfigure, CryptoBoxDevPreparation)
-You should have completed the steps described in CryptoBoxDevPreparation. +You should have completed the steps described in CryptoBoxDevPreparation.
The following steps can be executed in the order of their appearance.
-Usually there is no need to repeat the whole process, after you changed some parts of the CryptoBox. Especially the first step (building of the base system with dfsbuild) may usually be skipped. +Usually there is no need to repeat the whole process, after you changed some parts of the CryptoBox. Especially the first step (building of the base system with dfsbuild) may usually be skipped.
Every step of the building process must be executed as root. @@ -54,7 +55,7 @@ Run scripts/cbox-build.sh dfsbuild to create the base system for the Live The result can be found in _builddir/cd1/image.
-If you do not want to use the apt-cacher to save bandwidth and time, then you should modify the mirror-setting in dfs-cbox.conf (see CryptoBoxDevCustomBuild for details). +If you do not want to use the apt-cacher to save bandwidth and time, then you should modify the mirror-setting in dfs-cbox.conf (see CryptoBoxDevCustomBuild for details).
@@ -86,18 +87,18 @@ Do it manually: (change the dev setting according to your setup).
-Let the script do it for you: scripts/cbox-build.sh burn (maybe you have to change the CDWRITER setting in cbox-dev.conf - see CryptoBoxDevCustomBuild). +Let the script do it for you: scripts/cbox-build.sh burn (maybe you have to change the CDWRITER setting in cbox-dev.conf - see CryptoBoxDevCustomBuild).
Of course, it is not wise to use CD-R media. CD-RW consume less resources.
-This section is only useful for developers, who want to improve or change the CryptoBox system. +This section is only useful for developers, who want to improve or change the CryptoBox system.
-If you modified the perl- or shell-scripts of the CryptoBox, then you can check for syntax errors by running them in a chroot environment. Be careful: you have access to all ressources of your computer, while you are working within a chroot environment - so you can easily repartition your real disk ... +If you modified the perl- or shell-scripts of the CryptoBox, then you can check for syntax errors by running them in a chroot environment. Be careful: you have access to all ressources of your computer, while you are working within a chroot environment - so you can easily repartition your real disk ...
To start a chroot environment, you can execute scripts/cbox-dev.sh chroot. @@ -107,7 +108,7 @@ For more intensive tests, you may use qemu (see below) or burn real LiveC
-The processor emulator qemu allows you test the CryptoBox in a virtual environment, that is completely separated from your real computer's resources. It is the tool of choice, if you do nat have a real computer around for testing. +The processor emulator qemu allows you test the CryptoBox in a virtual environment, that is completely separated from your real computer's resources. It is the tool of choice, if you do nat have a real computer around for testing.
Beware - there are some problems, when using qemu: @@ -120,10 +121,10 @@ To start a qemu emulation of the iso image, you may type:
scripts/cbox-dev.sh qemu
-This section is only useful for developers, who want to develop on a running CryptoBox system (emulated or real). +This section is only useful for developers, who want to develop on a running CryptoBox system (emulated or real).
-You may access the CryptoBox directly or you can use ssh to open a remote session: +You may access the CryptoBox directly or you can use ssh to open a remote session:
./cbox-dev.sh ssh
-Type scripts/cbox-dev.sh diff to see the changes, you made on the running CryptoBox system. +Type scripts/cbox-dev.sh diff to see the changes, you made on the running CryptoBox system.
Type scripts/cbox-dev.sh merge to merge these changes to your local working copy.
--Alternatively you may also upload a new version of your local working copy to the running CryptoBox system. +Alternatively you may also upload a new version of your local working copy to the running CryptoBox system.
-Type scripts/cbox-dev.sh upload - beware: all recent changes you made to the running CryptoBox system, are lost. +Type scripts/cbox-dev.sh upload - beware: all recent changes you made to the running CryptoBox system, are lost. +
++Once you finished your development, you surely want to make a new release. Please read the instructions in the releas-policy.txt it will save you a lot of time! Then you basically just have to run scripts/cbox-build.sh release and get yourself a good coffee. After the command has finished you'll see the releasefiles in _buildir.
-Navigation: ( CryptoBox/en, CryptoBoxUser) +Navigation: ( CryptoBox/en, CryptoBoxUser)
-The following pages describe the easy use of the CryptoBox. +The following pages describe the easy use of the CryptoBox.
-The online version of this manual is a wiki, which means you can edit the pages. So if you have a question or you perceive a description as unclear, please post it on the bottom of the relevant page. The developers will answer your questions and update the manual as fast as possible. This way you can contribute in making the CryptoBox a better experience for everyone! +The online version of this manual is a wiki, which means you can edit the pages. So if you have a question or you perceive a description as unclear, please post it on the bottom of the relevant page. The developers will answer your questions and update the manual as fast as possible. This way you can contribute in making the CryptoBox a better experience for everyone!
-The online version of this manual can be found at https://systemausfall.org/trac/cryptobox/wiki/CryptoBoxUser/en.
diff --git a/doc/html/en/CryptoBoxUserConfiguration.html b/doc/html/en/CryptoBoxUserConfiguration.html index 88236ba..7664310 100644 --- a/doc/html/en/CryptoBoxUserConfiguration.html +++ b/doc/html/en/CryptoBoxUserConfiguration.html @@ -8,55 +8,74 @@-Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration) +Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration)
-All parts of administration of the CryptoBox are done through a comfortable web interface. If this is the first time you use the CryptoBox, just follow the steps below. +All parts of administration of the CryptoBox are done through a comfortable web interface. If this is the first time you use the CryptoBox, just follow the steps below.
-You can safely ignore the Foreword if you are in a hurry. +You can safely ignore the Foreword if you are in a hurry.
-Initialization describes the process of integrating a new harddisk. You usually have to perform this steps if you start with a new CryptoBox or after replacing the harddisk. +Initialization describes the process of integrating a new harddisk. You usually have to perform this steps if you start with a new CryptoBox or after replacing the harddisk.
-In the Configuration section, you can configure the CryptoBox according to your personal needs, e.g. change your desired language for the web interface or change the IP address of the CryptoBox. +In the Configuration section, you can configure the CryptoBox according to your personal needs, e.g. change your desired language for the web interface or change the IP address of the CryptoBox.
-Do not forget to read the Hints / Caveats section too. +Do not forget to read the Hints / Caveats section too.
-Okay, you finished the CryptoBoxUserGettingStarted and are now sitting in front of a computer that is connected via network with your CryptoBox. You point a browser to "https://192.168.0.23" and the CryptoBox interface appears. +Okay, you finished the CryptoBoxUserGettingStarted and are now sitting in front of a computer that is connected via network with your CryptoBox. You point a browser to "https://192.168.0.23" and the CryptoBox interface appears.
-Before you can save data on your CryptoBox, its harddisk has to be formatted with a cryptographic filesystem. Sounds complicated but don't be scared - it's really a "one click" thing. :) +Before you can save data on your CryptoBox, its harddisk has to be formatted with a cryptographic filesystem. Sounds complicated but don't be scared - it's really a "one click" thing. :)
-Click on Initialize CryptoBox in the title bar. +Click on Initialize CryptoBox in the title bar. +
+Now you are promted to enter two passwords twice (because we want to train your typing skills ;).
While the initialization is usually done only once, the configuration can be changed at any time you want. You can reach it by clicking at Configuration in the menu bar of the website. Now you see a form with four fields:
-Complete your changes by clicking on Save configuration.
-That's all - your CryptoBox is now ready for daily use! +That's all - your CryptoBox is now ready for daily use!
-back to CryptoBoxUser +back to CryptoBoxUser
-Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration/en, CryptoBoxUserDailyUse) +Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration/en, CryptoBoxUserDailyUse)
You can activate your encrypted filesystem by doing following these steps:
-@@ -51,16 +66,19 @@ resp. unmount:
smbumount /mnt
-Run the the Windows Explorer and choose Map network drive in the Extras menu: +Run the the Windows Explorer and choose Map network drive in the Tools menu:
Now you can use your encrypted data like any other network resource.
-You can deactivate the encrypted filesystem by clicking at Deactivation of encrypted data in the web interface of your CryptoBox. +You can deactivate the encrypted filesystem by clicking at Deactivation of encrypted data in the web interface of your CryptoBox.
Your data is now protected again. @@ -70,24 +88,30 @@ Your data is now protected again. Click at the Shutdown link in the menu of the web interface. There you can choose poweroff or reboot. The shutdown takes some seconds.
-If the hardware of your CryptoBox is quite recent, it will power-off automatically. Otherwise you have to do it manually. +If the hardware of your CryptoBox is quite recent, it will power-off automatically. Otherwise you have to do it manually.
-If you have to protect the drive really fast, just power-off the CryptoBox machine instantly by pulling the plug or pushing the power button. This is not very clean and can (in very rare circumstances) corrupt open files, but it is the fasted method to secure your data. +If you have to protect the drive really fast, just power-off the CryptoBox machine instantly by pulling the plug or pushing the power button. This is not very clean and can (in very rare circumstances) corrupt open files, but it is the fastest method to secure your data.
-back to CryptoBoxUser +back to CryptoBoxUser
This error message may appear, if you did not login during the booting of you windows machine (or you closed the login dialog by pressing ESC).
Solution: Choose Logout in the Start menu and login again.
+You can't unmount the partition with umount. diff --git a/doc/html/en/CryptoBoxUserGettingStarted.html b/doc/html/en/CryptoBoxUserGettingStarted.html index 0ee4f8e..3a37b84 100644 --- a/doc/html/en/CryptoBoxUserGettingStarted.html +++ b/doc/html/en/CryptoBoxUserGettingStarted.html @@ -8,53 +8,72 @@
-Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration/en, CryptoBoxUserGettingStarted) +Navigation: ( CryptoBoxUser/en, CryptoBoxUserConfiguration/en, CryptoBoxUserDailyUse/en, CryptoBoxUserGettingStarted)
-Getting the CryptoBox started doesn't take much: +Getting the CryptoBox started doesn't take much:
If it now boots from the CD, you accomplished all of the requirements.
-Now you can just go to your current desktop computer and point your browser to https://192.168.0.23 where the CryptoBox interface should be displayed. Easy - isn't it? +Now you can just go to your current desktop computer and point your browser to https://192.168.0.23 where the CryptoBox interface should be displayed. Easy - isn't it?
-For further steps go to CryptoBoxUserConfiguration. +For further steps go to CryptoBoxUserConfiguration.
-
-back to CryptoBoxUser +back to CryptoBoxUser