cryptonas/cryptonas-branches
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

added all non-code changes between r281 and r300 to the new release candidate

Browse source
This commit is contained in:
lars 2005-10-17 14:36:12 +00:00
parent 3cad3c5ae8
commit 7260c63d86
107 changed files with 5526 additions and 4016 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
v0.2.1/README
View file

@ -1,21 +1,24 @@
TODO: write a good README :)
$Id$
CryptoBox version 0.2.1
1) Documentation
The documentation is available at https://systemausfall.org/toolforge/CryptoBox
The documentation is available at https://systemausfall.org/trac/cryptobox/wiki/CryptoBoxUser
2) Building a LiveCD
try: "scripts/cbox-build.sh release"
or look at the developer's documentation: https://systemausfall.org/toolforge/CryptoBoxDev
or look at the developer's documentation: https://systemausfall.org/trac/cryptobox/wiki/CryptoBoxDev
3) Bug reporting
Use our issue tracker at https://systemausfall.org/trac/cryptobox
Use our issue tracker at https://systemausfall.org/trac/cryptobox/newticket
4) Licence
All scripts are GPL code (v2.0 or above).
The documentation is licenced under "Creative Commons 2.0 non-commercial share-alike" (http://creativecommons.org/licenses/by-nc-sa/2.0/)
The documentation is licenced under "Creative Commons 2.5 share-alike" (http://creativecommons.org/licenses/by-sa/2.5/).
5) Contributors
Clavdia Horvat, Tadej Brce & Dušan Rebolj - slovenian translation
6) Contact
email us: cryptobox@systemausfall.org
email: cryptobox@systemausfall.org
The CryptoBox project is mainly driven by sense.lab (https://systemausfall.org/senselab).

210
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBox.html
View file

@ -29,142 +29,90 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-e50e9371b89733779dffda07519c0bdfb6c3cd19">Neuigkeiten</a>
</li>
<li>
<a href="#head-a6addcb037bbd74e8c3f533fcbc9b974c5008676">Überblick</a>
</li>
<li>
<a href="#head-5b1aae7bec38aaabf39d79875117c8c10c945603">Spezifikationen</a>
</li>
<li>
<a href="#head-2614272d10d2679e8451f66e39db184578ec3d7c">Nutzung</a>
</li>
<li>
<a href="#head-b1bdcd2edb5c97874f17e2830b40854662ae1ef6">Mitmachen</a>
</li>
<li>
<a href="#head-f8cc7f13417e1024c0e7f219cc43f0fd9000ad72">Rechtliches</a>
</li>
<li><a href="CryptoBox.html#Neuigkeiten">Neuigkeiten</a></li>
<li><a href="CryptoBox.html#berblick">Überblick</a></li>
<li><a href="CryptoBox.html#Download">Download</a></li>
<li><a href="CryptoBox.html#Support">Support</a></li>
<li><a href="CryptoBox.html#Entwicklung">Entwicklung</a></li>
<li><a href="CryptoBox.html#Mitwirkende">Mitwirkende</a></li>
<li><a href="CryptoBox.html#Rechtliches">Rechtliches</a></li>
<li><a href="CryptoBox.html#Kommentare">Kommentare</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>unter <a href="CryptoBoxIntro.html">CryptoBoxIntro/de</a> findest du einen sehr kurzen Überblick</em> </p>
<h2 id="head-e50e9371b89733779dffda07519c0bdfb6c3cd19">Neuigkeiten</h2>
<p>Das erste Release der <a href="CryptoBox.html">CryptoBox</a> wird im Oktober bei <a href="http://codecoop.org/projects/cryptobox/">http://codecoop.org/projects/cryptobox/</a> verfügbar sein. </p>
<h2 id="head-a6addcb037bbd74e8c3f533fcbc9b974c5008676">Überblick</h2>
<p>Die <a href="CryptoBox.html">CryptoBox</a> ist eine <a class="interwiki" title="WikiPediaDe" href="http://de.wikipedia.org/wiki/Live-cd">Live-CD</a> 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 <a class="interwiki" title="WikiPediaDe" href="http://de.wikipedia.org/wiki/Kryptografie">Kryptografie</a> wissen musst. </p>
<p>Die Dokumentation der <a href="CryptoBox.html">CryptoBox</a> ist bisher in folgenden Sprachen verfügbar: </p>
<ul>
<li><p> <a href="CryptoBox.html">deutsch</a> </p>
</li>
<li><p> <a href="CryptoBox.html">english</a> </p>
</li>
</ul>
<p>Wir freuen uns über weitere Übersetzugen <img src="../../../var/www/cryptobox-img/smile.png" alt=":)" height="15" width="15"> </p>
<h2 id="head-5b1aae7bec38aaabf39d79875117c8c10c945603">Spezifikationen</h2>
<div>
<table>
<tr>
<td>
<p>System</p>
</td>
<td>
<p>Debian/Linux basierte Live-CD</p>
</td>
</tr>
<tr>
<td>
<p>benötigter Computer</p>
</td>
<td>
<p> "ausrangierter" PC (i386 ab p1 mind. 32MB RAM)</p>
</td>
</tr>
<tr>
<td>
<p>unterstützte Clients</p>
</td>
<td>
<p><a class="interwiki" title="WikiPediaDe" href="http://de.wikipedia.org/wiki/Liste_der_Betriebssysteme">*nix; *bsd; Windows; Mac OS</a></p>
</td>
</tr>
<tr>
<td>
<p>interner Fileserver</p>
</td>
<td>
<p><a class="external" href="http://samba.org">samba</a> (Netzwerkfreigaben)</p>
</td>
</tr>
<tr>
<td>
<p>Benutzerschnittstelle</p>
</td>
<td>
<p>per Browser bedienbares Web-Interface</p>
</td>
</tr>
<tr>
<td>
<p>Verschlüsselung</p>
</td>
<td>
<p><a class="interwiki" title="WikiPediaDe" href="http://de.wikipedia.org/wiki/Advanced_Encryption_Standard">AES</a> via device-mapper</p>
</td>
</tr>
</table>
</div>
<p>Das Web-Interface der <a href="CryptoBox.html">CryptoBox</a> ünterstützt derzeit folgende Sprachen: </p>
<ul>
<li><p> deutsch </p>
</li>
<li><p> englisch </p>
</li>
<li><p> slowenisch </p>
</li>
</ul>
<p>Du kannst gern weitere <a class="interwiki" title="SubVersion" href="/websvn/cryptobox/trunk/cbox-tree.d/usr/share/cryptobox/lang/en.hdf">Übersetzungen</a> in andere Sprachen hinzufügen (idealerweise utf-encodiert). </p>
<h2 id="head-2614272d10d2679e8451f66e39db184578ec3d7c">Nutzung</h2>
<p>Das Nutzerhandbuch ist unter <a href="CryptoBoxUser.html">CryptoBoxUser/de</a> verfügbar. </p>
<h2 id="head-b1bdcd2edb5c97874f17e2830b40854662ae1ef6">Mitmachen</h2>
<p>Beteilige dich an der Entwicklung der <a href="CryptoBox.html">CryptoBox</a> und werde reich und schön! <img src="../../../var/www/cryptobox-img/smile4.png" alt=";)" height="15" width="15"> <br>
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 <em>cryptobox[at]systemausfall.org</em> und hab Spaß. </p>
<p>Fehler kannst du in unserer <a class="external" href="https://systemausfall.org/trac/cryptobox">Fehlerdatenbank</a> eintragen. </p>
<p>Die Entwickler-Doku findest du unter <a href="CryptoBoxDev.html">CryptoBoxDev</a> (bisher nur englisch). </p>
<h2 id="head-f8cc7f13417e1024c0e7f219cc43f0fd9000ad72">Rechtliches</h2>
<ol type="1">
<li><p>Alle Skripte unterliegen der <a class="external" href="http://www.fsf.org/licensing/licenses/gpl.html">GPL</a> - sie sind also quasi vollständig frei. </p>
</li>
<li><p>Die Dokumentation unterliegt einer <em><a class="external" href="http://creativecommons.org/licenses/by-sa-nc/2.0/">Creative Commons</a></em>-Lizenz, damit wird die Möglichkeit der freien Verbreitung des gesammelten Wissens gewährleistet. </p>
</li>
<li><p>Wir übernehmen keinerlei Haftung für eventuelle Folgen, die durch die Nutzung einer <a href="CryptoBox.html">CryptoBox</a> entstehen könnten. </p>
</li>
</ol>
</p>
<h1 id="DieCryptoBox">Die CryptoBox</h1>
<p>
<i><a href="CryptoBox.html">English version</a></i>
</p>
<h2 id="Neuigkeiten">Neuigkeiten</h2>
<p>
Das erste Release der <a href="CryptoBox.html">CryptoBox</a> ist bei <a class="ext-link" title="https://codecoop.org/projects/cryptobox/" href="https://codecoop.org/projects/cryptobox/">Codecoop.org</a> verfügbar.
</p>
<h2 id="berblick">Überblick</h2>
<p>
Die <a href="CryptoBox.html">CryptoBox</a> ist eine <a class="ext-link" title="http://de.wikipedia.org/wiki/Live-cd" href="http://de.wikipedia.org/wiki/Live-cd">Live-CD</a> 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 <a class="ext-link" title="http://de.wikipedia.org/wiki/Kryptografie" href="http://de.wikipedia.org/wiki/Kryptografie">Kryptografie</a> wissen musst.<br />
Die Bedienung erfolgt vollständig per Webbrowser. Wirf einen Blick auf die <a href="ScreenShots.html">ScreenShots</a>.
</p>
<table class="wiki">
<tr><td><i>Spezifikation</i>
</td></tr><tr><td>System</td><td>Debian GNU/Linux-basierte Live-CD
</td></tr><tr><td>benötigter Computer</td><td>&#34;ausrangierter&#34; PC (i386 ab p1 mind. 32MB RAM)
</td></tr><tr><td>unterstützte Clients</td><td><a class="ext-link" title="http://de.wikipedia.org/wiki/Liste_der_Betriebssysteme" href="http://de.wikipedia.org/wiki/Liste_der_Betriebssysteme">*nix; *bsd; Windows; Mac OS</a>
</td></tr><tr><td>interner Fileserver</td><td><a class="ext-link" title="http://samba.org" href="http://samba.org">samba</a> (Netzwerkfreigaben)
</td></tr><tr><td>Benutzerschnittstelle</td><td>per Browser bedienbares Web-Interface
</td></tr><tr><td>Verschlüsselung</td><td><a class="ext-link" title="http://de.wikipedia.org/wiki/Advanced_Encryption_Standard" href="http://de.wikipedia.org/wiki/Advanced_Encryption_Standard">AES</a> via device-mapper
</td></tr></table>
<p>
Das Web-Interface der <a href="CryptoBox.html">CryptoBox</a> unterstützt derzeit folgende Sprachen:
</p>
<ul><li>deutsch
</li><li>englisch
</li><li>slowenisch
</li></ul><p>
Wir suchen noch Übersetzungen in andere Sprachen. Wenn du dich beteiligen möchtest, wirf einen Blick in die <a href="/trac/cryptobox/browser/trunk/cbox-tree.d/usr/share/cryptobox/lang">Übersetzungen-Sektion</a>. Dort gibt es eine &#34;README&#34; Datei in der genauere Beschreibungen stehen.
</p>
<h2 id="Download">Download</h2>
<ul><li><a class="ext-link" title="http://codecoop.org/frs/download.php/32/cryptobox_0.2.iso" href="http://codecoop.org/frs/download.php/32/cryptobox_0.2.iso">Version 0.2</a> [104 MB] - <a href="/trac/cryptobox/wiki/ReleaseNotes/0.2">Release notes</a>
<ul><li><i>bereitgestellt durch <a class="ext-link" title="http://codecoop.org" href="http://codecoop.org">http://codecoop.org</a></i>
</li></ul></li></ul><h2 id="Support">Support</h2>
<ul><li>Das Nutzerhandbuch ist unter <a href="CryptoBoxUser.html">CryptoBoxUser</a> verfügbar.
</li><li>Probleme und Anregungen kannst du unser <a class="ext-link" title="https://systemausfall.org/trac/cryptobox/newticket" href="https://systemausfall.org/trac/cryptobox/newticket">Fehlerdatenbank</a> melden
</li><li>Für allgemeine Fragen, schreibe eine Email an <i>cryptobox[at]systemausfall.org</i>.
</li></ul><h2 id="Entwicklung">Entwicklung</h2>
<p>
Beteilige dich an der Entwicklung der <a href="CryptoBox.html">CryptoBox</a> und werde reich und schön! ;) <br />
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. <br />
Schreib eine Mail an <i>cryptobox[at]systemausfall.org</i> und hab Spaß.
</p>
<p>
Die englischsprachige Entwickler-Doku findest du unter <a href="CryptoBoxDev.html">CryptoBoxDev</a>.
</p>
<h2 id="Mitwirkende">Mitwirkende</h2>
<p>
<ul><li>Clavdia Horvat, Tadej Brce &amp; Dušan Rebolj - slovenian translation
</li><li><a class="ext-link" title="http://codecoop.org" href="http://codecoop.org">http://codecoop.org</a> - webspace
</li></ul>
</p>
<h2 id="Rechtliches">Rechtliches</h2>
<ol><li>Alle Skripte unterliegen der <a class="ext-link" title="http://www.fsf.org/licensing/licenses/gpl.html" href="http://www.fsf.org/licensing/licenses/gpl.html">GPL</a> - sie sind also quasi vollständig frei.
</li><li>Die Dokumentation unterliegt einer <i><a class="ext-link" title="http://creativecommons.org/licenses/by-sa-nc/2.0/" href="http://creativecommons.org/licenses/by-sa-nc/2.0/">Creative Commons</a></i>-Lizenz, damit wird die Möglichkeit der freien Verbreitung des gesammelten Wissens gewährleistet.
</li><li>Wir übernehmen keinerlei Haftung für eventuelle Folgen, die durch die Nutzung einer <a href="CryptoBox.html">CryptoBox</a> entstehen könnten.
</li></ol><hr />
<h2 id="Kommentare">Kommentare</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

132
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDev.html
View file

@ -29,54 +29,98 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-85f75330e62e5b1efc9f504fe9cb51a1b966dc3b">Development documentation</a>
</li>
<li>
<a href="#head-b8ce79abe983e1592235d0085dd6928b83811739">Contact</a>
</li>
<li>
<a href="#head-964f56b054273ed39bab34484f83ac053ac0f12e">Bug reports</a>
</li>
<li><a href="CryptoBoxDevPreparation.html#Preparationsfordevelopers">Preparations for developers</a></li>
<ol><li><a href="CryptoBoxDevPreparation.html#Softwarerequirements">Software requirements</a></li>
<li><a href="CryptoBoxDevPreparation.html#Getthesource">Get the source</a></li>
<li><a href="CryptoBoxDevPreparation.html#Firstbuild">First build</a></li>
<li><a href="CryptoBoxDevPreparation.html#Finished">Finished</a></li>
<li><a href="CryptoBoxDevPreparation.html#Comments">Comments</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<li><a href="CryptoBoxDevWorkFlow.html#Developmentworkflow">Development workflow</a></li>
<ol><li><a href="CryptoBoxDevWorkFlow.html#Preparations">Preparations</a></li>
<li><a href="CryptoBoxDevWorkFlow.html#CreateaCryptoBoxLiveCD">Create a CryptoBox-LiveCD</a></li>
<li><a href="CryptoBoxDevWorkFlow.html#TesttheCryptoBoxLiveCD">Test the CryptoBox-LiveCD</a></li>
<li><a href="CryptoBoxDevWorkFlow.html#Debuggingandmerging">Debugging and merging</a></li>
<li><a href="CryptoBoxDevWorkFlow.html#Comments">Comments</a></li>
</ol>
<li><a href="CryptoBoxDevCustomBuild.html#CustombuildsoftheCryptoBox">Custom builds of the CryptoBox</a></li>
<ol><li><a href="CryptoBoxDevCustomBuild.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#Settings">Settings</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#Comments">Comments</a></li>
</ol>
<li><a href="CryptoBoxDevCustomConfigure.html#CustomconfigurationoftheCryptoBox">Custom configuration of the CryptoBox</a></li>
<ol><li><a href="CryptoBoxDevCustomConfigure.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Locations">Locations</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Examples">Examples</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Comments">Comments</a></li>
</ol>
<li><a href="CryptoBoxDevValidation.html#ValidationoftheCryptoBox">Validation of the CryptoBox</a></li>
<ol><li><a href="CryptoBoxDevValidation.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevValidation.html#Validate">Validate</a></li>
<li><a href="CryptoBoxDevValidation.html#Howtocreateatest">How to create a test</a></li>
<li><a href="CryptoBoxDevValidation.html#Comments">Comments</a></li>
</ol>
<li><a href="CryptoBoxDevBackground.html#DetailsoftheCryptoBox">Details of the CryptoBox</a></li>
<ol><li><a href="CryptoBoxDevBackground.html#dfsbuild">dfsbuild</a></li>
<li><a href="CryptoBoxDevBackground.html#thekernel">the kernel</a></li>
<li><a href="CryptoBoxDevBackground.html#qemu">qemu</a></li>
<li><a href="CryptoBoxDevBackground.html#alternativeLiveCDs">alternative LiveCDs</a></li>
<li><a href="CryptoBoxDevBackground.html#Comments">Comments</a></li>
</ol>
<li><a href="CryptoBoxDevKnownProblems.html#Knownproblems">Known problems</a></li>
<ol><li><a href="CryptoBoxDevKnownProblems.html#qemu">qemu</a></li>
<li><a href="CryptoBoxDevKnownProblems.html#dfsbuild">dfsbuild</a></li>
<li><a href="CryptoBoxDevKnownProblems.html#Comments">Comments</a></li>
</ol>
</ol>
</div>
<h2 id="head-85f75330e62e5b1efc9f504fe9cb51a1b966dc3b">Development documentation</h2>
<p>The following pages are written for developers only. Users of the <a href="CryptoBox.html">CryptoBox</a> should read <a href="CryptoBoxUser.html">CryptoBoxUser</a> instead. </p>
<ul>
<li><p> <a href="CryptoBoxDevPreparation.html">CryptoBoxDevPreparation</a> </p>
</li>
<li><p> <a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a> </p>
</li>
<li><p> <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> </p>
</li>
<li><p> <a href="CryptoBoxDevCustomConfigure.html">CryptoBoxDevCustomConfigure</a> </p>
</li>
<li><p> <a href="CryptoBoxDevValidation.html">CryptoBoxDevValidation</a> </p>
</li>
<li><p> <a href="CryptoBoxDevBackground.html">CryptoBoxDevBackground</a> </p>
</li>
<li><p> <a href="CryptoBoxDevKnownProblems.html">CryptoBoxDevKnownProblems</a> </p>
</li>
</ul>
<h2 id="head-b8ce79abe983e1592235d0085dd6928b83811739">Contact</h2>
<p>We are waiting for your emails to <em>cryptobox[at]systemausfall.org</em>. </p>
<h2 id="head-964f56b054273ed39bab34484f83ac053ac0f12e">Bug reports</h2>
<p>Please use our issue tracker, if you discover problems: <a href="https://systemausfall.org/trac/cryptobox">https://systemausfall.org/trac/cryptobox</a> </p>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBox.html">CryptoBox/de</a>, <a href="CryptoBox.html">CryptoBox/en</a>)
</p>
<hr />
<h1 id="Developmentdocumentation">Development documentation</h1>
<p>
The following pages are written for developers only. <br />
Users of the <a href="CryptoBox.html">CryptoBox</a> should read <a href="CryptoBoxUser.html">CryptoBoxUser</a> instead.
</p>
<ul><li><a href="CryptoBoxDevPreparation.html">CryptoBoxDevPreparation</a>
</li><li><a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a>
</li><li><a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a>
</li><li><a href="CryptoBoxDevCustomConfigure.html">CryptoBoxDevCustomConfigure</a>
</li><li><a href="CryptoBoxDevValidation.html">CryptoBoxDevValidation</a>
</li><li><a href="CryptoBoxDevBackground.html">CryptoBoxDevBackground</a>
</li><li><a href="CryptoBoxDevKnownProblems.html">CryptoBoxDevKnownProblems</a>
</li></ul><h2 id="Source">Source</h2>
<p>
You may browse the <a href="/trac/cryptobox/browser/">source code</a>.
</p>
<h2 id="Contact">Contact</h2>
<p>
We are waiting for your emails to <i>cryptobox[at]systemausfall.org</i>.
</p>
<h2 id="Bugreports">Bug reports</h2>
<p>
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:
</p>
<ol><li>Have a look at <a href="/trac/cryptobox/report/1">Open bugs</a> that need to be fixed
</li><li>Create a <a class="ext-link" title="https://systemausfall.org/trac/cryptobox/newticket" href="https://systemausfall.org/trac/cryptobox/newticket">New Ticket</a>
</li></ol></div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

118
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevBackground.html
View file

@ -29,71 +29,69 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-2d71165918ee9e861cebf562e7f9be2c5c6328e4">dfsbuild</a>
</li>
<li>
<a href="#head-6e3d13fcf3a0765d2188125e9b0b0bcb95e50622">the kernel</a>
</li>
<li>
<a href="#head-e01e8e66ae77c00f4e9fa9bd190c3ff738540727">qemu</a>
</li>
<li>
<a href="#head-00c94b926ece7f2a601d696a8880f5e54155ce7a">alternative LiveCDs</a>
</li>
<li><a href="CryptoBoxDevBackground.html#dfsbuild">dfsbuild</a></li>
<li><a href="CryptoBoxDevBackground.html#thekernel">the kernel</a></li>
<li><a href="CryptoBoxDevBackground.html#qemu">qemu</a></li>
<li><a href="CryptoBoxDevBackground.html#alternativeLiveCDs">alternative LiveCDs</a></li>
<li><a href="CryptoBoxDevBackground.html#Comments">Comments</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
</div>
<h2 id="head-2d71165918ee9e861cebf562e7f9be2c5c6328e4">dfsbuild</h2>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>)
<p>The base system of the <a href="CryptoBox.html">CryptoBox</a> Live-CD is created by <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a>. </p>
<p>It is recommended to use some kind of caching tool for the retrieval of the debian packages (e.g.: <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=apt-cacher">apt-cacher</a> or <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=apt-proxy">apt-proxy</a>). This saves a lot of bandwidth and time. </p>
<p>The documentation for <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a> is sparse. But it is quite unlikely, that you will get in direct contact with it, as it is wrapped by <em>cbox-build</em>. However the following links may help you for specific problems: </p>
<ul>
<li><p> <a class="external" href="http://www.debian-administration.org/articles/125">Debian Administration: Building Debian CD-ROMS Part 1 - dfsbuild</a> </p>
</li>
<li><p> <a class="external" href="http://www.debian-administration.org/articles/149">Debian Administration: Getting in deep with dfsbuild</a> </p>
</li>
</ul>
<h2 id="head-6e3d13fcf3a0765d2188125e9b0b0bcb95e50622">the kernel</h2>
<p>The linux kernel for the <a href="CryptoBox.html">CryptoBox</a> is compiled statically. If you want to change it, you could follow this steps: </p>
<ol type="1">
<li><p>get the sources: <tt>apt-get&nbsp;install&nbsp;kernel-tree-2.6.11</tt> (or the version of your choice) </p>
</li>
<li><p>copy the exisiting config file <em>kernel/config-2.6.11</em> as <em>.config</em> into your kernel source directory </p>
</li>
<li><p>build the debian kernel package <tt>make-kpkg&nbsp;--revision=1.dfs&nbsp;--rootcmd=fakeroot&nbsp;kernel_image</tt> </p>
</li>
<li><p>change the kernel in the <em>unpackdebs</em> setting in <em>dfs-cbox.conf</em> (see <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> for details) </p>
</li>
</ol>
<h2 id="head-e01e8e66ae77c00f4e9fa9bd190c3ff738540727">qemu</h2>
<p><a class="external" href="http://fabrice.bellard.free.fr/qemu/">Qemu</a> 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. </p>
<h2 id="head-00c94b926ece7f2a601d696a8880f5e54155ce7a">alternative LiveCDs</h2>
<p>We tried some other LiveCDs before we decided to use <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a>. The following pages describe their advantages and disadvantages as the base system for the <a href="CryptoBox.html">CryptoBox</a>: </p>
<ul>
<li><p> <a href="CryptoBoxKnoppixVerworfen.html">CryptoBoxKnoppixVerworfen</a> - Knoppix </p>
</li>
<li><p> <a href="CryptoBoxMorphixVerworfen.html">CryptoBoxMorphixVerworfen</a> - Morphix / IBuild </p>
</li>
</ul>
</p>
<hr />
<h1 id="DetailsoftheCryptoBox">Details of the CryptoBox</h1>
<h2 id="dfsbuild">dfsbuild</h2>
<p>
The base system of the <a href="CryptoBox.html">CryptoBox</a> Live-CD is created by <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a>.
</p>
<p>
It is recommended to use some kind of caching tool for the retrieval of the debian packages (e.g.: <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-cacher" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-cacher">apt-cacher</a>, <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-proxy" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-proxy">apt-proxy</a> or <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=approx" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=approx">approx</a>). This saves a lot of bandwidth and time.
</p>
<p>
The documentation for <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a> is sparse. But it is quite unlikely, that you will get in direct contact with it, as it is wrapped by <a href="/trac/cryptobox/browser/trunk/scripts/cbox-build.sh">cbox-build</a>. However the following links may help you for specific problems:
</p>
<ul><li><a class="ext-link" title="http://www.debian-administration.org/articles/125" href="http://www.debian-administration.org/articles/125">Debian Administration: Building Debian CD-ROMS Part 1 - dfsbuild</a>
</li><li><a class="ext-link" title="http://www.debian-administration.org/articles/149" href="http://www.debian-administration.org/articles/149">Debian Administration: Getting in deep with dfsbuild</a>
</li></ul><h2 id="thekernel">the kernel</h2>
<p>
The linux kernel for the <a href="CryptoBox.html">CryptoBox</a> is compiled statically. If you want to change it, you could follow this steps:
</p>
<ol><li>get the sources: <tt>apt-get install kernel-tree-2.6.11</tt> (or the version of your choice)
</li><li>copy the exisiting config file <i>kernel/config-2.6.11</i> as <i>.config</i> into your kernel source directory
</li><li>build the debian kernel package <tt>make-kpkg --revision=1.dfs --rootcmd=fakeroot kernel_image</tt>
</li><li>change the kernel in the <i>unpackdebs</i> setting in <a href="/trac/cryptobox/browser/trunk/etc-defaults.d/dfs-cbox.conf">dfs-cbox.conf</a> (see <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> for details)
</li></ol><p>
See <a title="" href="/trac/cryptobox/browser/trunk/hints/kernel-build.txt">source:trunk/hints/kernel-build.txt</a> for more details.
</p>
<h2 id="qemu">qemu</h2>
<p>
<a class="ext-link" title="http://fabrice.bellard.free.fr/qemu/" href="http://fabrice.bellard.free.fr/qemu/">Qemu</a> 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.
</p>
<h2 id="alternativeLiveCDs">alternative LiveCDs</h2>
<p>
We tried some other LiveCDs before we decided to use <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a>. The following pages describe their advantages and disadvantages as the base system for the <a href="CryptoBox.html">CryptoBox</a>:
</p>
<ul><li><a href="CryptoBoxKnoppixVerworfen.html">CryptoBoxKnoppixVerworfen</a> - Knoppix
</li><li><a href="CryptoBoxMorphixVerworfen.html">CryptoBoxMorphixVerworfen</a> - Morphix / IBuild
</li></ul><hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

171
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevCustomBuild.html
View file

@ -29,103 +29,90 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-27ea5a3ee88c7c2dfcfd4124719aadd726f1e2da">Overview</a>
</li>
<li>
<a href="#head-737db576c5f42abc0c78574d0ce5077809f288cb">Settings</a>
<ol>
<li>
<a href="#head-9d97886ad41e38cb6afe343aa68ff652030ab06b">dfsbuild settings</a>
</li>
<li>
<a href="#head-c2ae24a50a3706711c1a42e26176768438d4f160">CryptoBox development configuration</a>
</li>
<li>
<a href="#head-90ac95d2e5a50160cbf72b884b7b469a29c2fea1">SSH connection</a>
</li>
<li>
<a href="#head-6798893e2e3fd89a72b5b6821a0d3d08125367b9">qemu network configuration</a>
</li>
<li><a href="CryptoBoxDevCustomBuild.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#Settings">Settings</a></li>
<ol><li><a href="CryptoBoxDevCustomBuild.html#dfsbuildsettings">dfsbuild settings</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#CryptoBoxdevelopmentconfiguration">CryptoBox development configuration</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#SSHconnection">SSH connection</a></li>
<li><a href="CryptoBoxDevCustomBuild.html#qemunetworkconfiguration">qemu network configuration</a></li>
</ol><li><a href="CryptoBoxDevCustomBuild.html#Comments">Comments</a></li>
</ol>
</div>
</li>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>, <a href="CryptoBoxDevBackground.html">CryptoBoxDevBackground</a>, <a href="/trac/cryptobox/wiki/CryptoBoxDevPreparation">CryptoBoxDevPreparation</a>, <a href="/trac/cryptobox/wiki/CryptoBoxDevWorkFlow">CryptoBoxDevWorkFlow</a>)
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
<h2 id="head-27ea5a3ee88c7c2dfcfd4124719aadd726f1e2da">Overview</h2>
<p>The following sections are useful, if you want to change the default settings of your personal <a href="CryptoBox.html">CryptoBox</a> development environment. </p>
<p>You should have completed the steps described in <a href="CryptoBoxDevPreparation.html">CryptoBoxDevPreparation</a>. </p>
<h2 id="head-737db576c5f42abc0c78574d0ce5077809f288cb">Settings</h2>
<h3 id="head-9d97886ad41e38cb6afe343aa68ff652030ab06b">dfsbuild settings</h3>
<p>All settings for <em>dfsbuild</em> can be found in <em>etc-defaults.d/dfs-cbox.conf</em>. </p>
<p>If you want to change any of them, you should do the following: </p>
<ol type="1">
<li><p>copy <em>etc-defaults.d/dfs-cbox.conf</em> file to <em>etc-local.d/</em> </p>
</li>
<li><p>change <em>etc-local.d/dfs-cbox.conf</em> according to your needs </p>
</li>
</ol>
<p>This allows you to use your own (personal) settings, without interfering with files under version control. </p>
<h3 id="head-c2ae24a50a3706711c1a42e26176768438d4f160">CryptoBox development configuration</h3>
<p>Some settings regarding the building, configuring and validating of the <a href="CryptoBox.html">CryptoBox</a> can be found in <em>etc-defaults.d/cbox-dev.conf</em>. </p>
<p>If you want to change any of them, you should do the following: </p>
<ol type="1">
<li><p>copy <em>etc-defaults.d/cbox-dev.conf</em> file to <em>etc-local.d/</em> </p>
</li>
<li><p>change <em>etc-local.d/cbox-dev.conf</em> according to your needs </p>
</li>
</ol>
<h3 id="head-90ac95d2e5a50160cbf72b884b7b469a29c2fea1">SSH connection</h3>
<p>The file <em>etc-defaults.d/ssh_config</em> is used to establish a connection to a running <a href="CryptoBox.html">CryptoBox</a> system. </p>
<p>It can be necessary to change these settings, if: </p>
<ul>
<li><p> you do not want to use the default IP for the <a href="CryptoBox.html">CryptoBox</a> </p>
</li>
<li><p> or the <a href="CryptoBox.html">CryptoBox</a> is not within your local network. </p>
</li>
</ul>
<p>If you want to change some settings, you should do the following: </p>
<ol type="1">
<li><p>copy <em>etc-defaults.d/ssh_config</em> file to <em>etc-local.d/</em> </p>
</li>
<li><p>change <em>etc-local.d/ssh_config</em> according to your needs </p>
</li>
</ol>
<h3 id="head-6798893e2e3fd89a72b5b6821a0d3d08125367b9">qemu network configuration</h3>
<p>The file <em>etc-defauolts.d/qemu-ifup</em> is used for the <a href="CryptoBox.html">CryptoBox</a> emulation with <em>qemu</em>. See <tt>man&nbsp;qemu</tt> for details. </p>
<p>If you want to change some settings, you should do the following: </p>
<ol type="1">
<li><p>copy <em>etc-defaults.d/qemu-ifup</em> file to <em>etc-local.d/</em> </p>
</li>
<li><p>change <em>etc-local.d/qemu-ifup</em> according to your needs </p>
</li>
</ol>
</p>
<hr />
<h1 id="CustombuildsoftheCryptoBox">Custom builds of the CryptoBox</h1>
<h2 id="Overview">Overview</h2>
<p>
The following sections are useful, if you want to change the default settings of your personal <a href="CryptoBox.html">CryptoBox</a> development environment.
</p>
<p>
You should have completed the steps described in <a href="CryptoBoxDevPreparation.html">CryptoBoxDevPreparation</a>.
</p>
<h2 id="Settings">Settings</h2>
<h3 id="dfsbuildsettings">dfsbuild settings</h3>
<p>
All settings for <i>dfsbuild</i> can be found in <a href="/trac/cryptobox/browser/trunk/etc-defaults.d/dfs-cbox.conf">etc-defaults.d/dfs-cbox.conf</a>.
</p>
<p>
If you want to change any of them, you should do the following:
</p>
<ol><li>copy <i>etc-defaults.d/dfs-cbox.conf</i> file to <i>etc-local.d/</i>
</li><li>change <i>etc-local.d/dfs-cbox.conf</i> according to your needs
</li></ol><p>
This allows you to use your own (personal) settings, without interfering with files under version control.
</p>
<h3 id="CryptoBoxdevelopmentconfiguration">CryptoBox development configuration</h3>
<p>
Some settings regarding the building, configuring and validating of the <a href="CryptoBox.html">CryptoBox</a> can be found in <a href="/trac/cryptobox/browser/trunk/etc-defaults.d/cbox-dev.conf">etc-defaults.d/cbox-dev.conf</a>.
</p>
<p>
If you want to change any of them, you should do the following:
</p>
<ol><li>copy <i>etc-defaults.d/cbox-dev.conf</i> file to <i>etc-local.d/</i>
</li><li>change <i>etc-local.d/cbox-dev.conf</i> according to your needs
</li></ol><h3 id="SSHconnection">SSH connection</h3>
<p>
The file <a href="/trac/cryptobox/browser/trunk/etc-defaults.d/ssh_config">ssh_config</a> is used to establish a connection to a running <a href="CryptoBox.html">CryptoBox</a> system.
</p>
<p>
It can be necessary to change these settings, if:
</p>
<ul><li>you do not want to use the default IP for the <a href="CryptoBox.html">CryptoBox</a>
</li><li>or the <a href="CryptoBox.html">CryptoBox</a> is not within your local network.
</li></ul><p>
If you want to change some settings, you should do the following:
</p>
<ol><li>copy <i>etc-defaults.d/ssh_config</i> file to <i>etc-local.d/</i>
</li><li>change <i>etc-local.d/ssh_config</i> according to your needs
</li></ol><h3 id="qemunetworkconfiguration">qemu network configuration</h3>
<p>
The file <a href="/trac/cryptobox/browser/trunk/etc-defauolts.d/qemu-ifup">etc-defauolts.d/qemu-ifup</a> is used for the <a href="CryptoBox.html">CryptoBox</a> emulation with <i>qemu</i>. See <i>man qemu</i> for details.
</p>
<p>
If you want to change some settings, you should do the following:
</p>
<ol><li>copy <i>etc-defaults.d/qemu-ifup</i> file to <i>etc-local.d/</i>
</li><li>change <i>etc-local.d/qemu-ifup</i> according to your needs
</li></ol><hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

108
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevCustomConfigure.html
View file

@ -29,65 +29,65 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-eaec6be4efea7b38c41712778bfd4fb8d2827d3c">Overview</a>
</li>
<li>
<a href="#head-51173f0423ca91d36cd0cfcdc75a06d90cc087ee">Locations</a>
</li>
<li>
<a href="#head-9b9b6463081c4d9d13e3aadebe9daaf61fa67b5c">Examples</a>
</li>
<li><a href="CryptoBoxDevCustomConfigure.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Locations">Locations</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Examples">Examples</a></li>
<li><a href="CryptoBoxDevCustomConfigure.html#Comments">Comments</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
</div>
<h2 id="head-eaec6be4efea7b38c41712778bfd4fb8d2827d3c">Overview</h2>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>)
<p>You may change nearly every aspect of the <a href="CryptoBox.html">CryptoBox</a> by using the custom configuration hook directory. </p>
<p>Any script inside of this directory will be executed after the default configuration procedure (see <a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a>). </p>
<p>The order of execution is defined by the names of the scripts (alphabetically). </p>
<h2 id="head-51173f0423ca91d36cd0cfcdc75a06d90cc087ee">Locations</h2>
<p>Some example customization scripts can be found in <em>configure-examples.d/</em>. </p>
<p>You may put your scripts into <em>configure-local.d/</em>. They will be sourced by <em>cbox-build.sh</em>. </p>
<h2 id="head-9b9b6463081c4d9d13e3aadebe9daaf61fa67b5c">Examples</h2>
<p>The examples in <em>configure-examples.d/</em> can be copied to <em>configure-local.d/</em> and adjusted to your needs. </p>
<dl>
<dt>set_default_ip</dt>
<dd><p>change the default IP address of the <a href="CryptoBox.html">CryptoBox</a> </p>
</dd>
<dt>set_default_language</dt>
<dd><p>set the default language </p>
</dd>
<dt>set_default_timeout</dt>
<dd><p>set the default idle time for automatic unmounting </p>
</dd>
<dt>set_hostname</dt>
<dd><p>change the default hostname </p>
</dd>
<dt>set_root_pw</dt>
<dd><p>change the password of root (only useful for a development <a href="CryptoBox.html">CryptoBox</a>) </p>
</dd>
<dt>import_authorized_keys</dt>
<dd><p>upload a <em>ssh</em> key for passwordless access to a development <a href="CryptoBox.html">CryptoBox</a> </p>
</dd>
<dt>set_scan_devices</dt>
<dd><p>where to look for usable harddisks </p>
</dd>
</dl>
</p>
<hr />
<h1 id="CustomconfigurationoftheCryptoBox">Custom configuration of the CryptoBox</h1>
<h2 id="Overview">Overview</h2>
<p>
You may change nearly every aspect of the <a href="CryptoBox.html">CryptoBox</a> by using the custom configuration hook directory.
</p>
<p>
Any script inside of this directory will be executed after the default configuration procedure (see <a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a>).
</p>
<p>
The order of execution is defined by the names of the scripts (alphabetically).
</p>
<h2 id="Locations">Locations</h2>
<p>
Some example customization scripts can be found in <a href="/trac/cryptobox/browser/trunk/configure-examples.d">configure-examples.d/</a>.
</p>
<p>
You may put your scripts into <i>configure-local.d/</i>. They will be sourced by <a href="/trac/cryptobox/browser/trunk/scripts/cbox-build.sh">cbox-build.sh</a>.
</p>
<h2 id="Examples">Examples</h2>
<p>
The examples in <a href="/trac/cryptobox/browser/trunk/configure-examples.d">configure-examples.d/</a> can be copied to <i>configure-local.d/</i> and adjusted to your needs.
</p>
<table class="wiki">
<tr><td>set_default_ip</td><td>change the default IP address of the CryptoBox
</td></tr><tr><td>set_default_language</td><td>set the default language
</td></tr><tr><td>set_default_timeout</td><td>set the default idle time for automatic unmounting
</td></tr><tr><td>set_hostname</td><td>change the default hostname
</td></tr><tr><td>set_root_pw</td><td>change the password of root (only useful for a development <a href="CryptoBox.html">CryptoBox</a>)
</td></tr><tr><td>import_authorized_keys</td><td>upload a <i>ssh</i> key for passwordless access to a development CryptoBox
</td></tr><tr><td>set_scan_devices</td><td>where to look for usable harddisks
</td></tr></table>
<hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

70
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevKnownProblems.html
View file

@ -29,41 +29,51 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-3d279b986395c95455d4d831054f9664ac846790">qemu</a>
<ol>
<li>
<a href="#head-9d223a1d9ee655c5a338f798fc08850a2b3694ba">interleaved files not (yet) supported</a>
</li>
<li>
<a href="#head-aa082f09cdb79c9a715826562efebd23cb8e9dfc">smbd: segfault</a>
</li>
<li><a href="CryptoBoxDevKnownProblems.html#qemu">qemu</a></li>
<ol><li><a href="CryptoBoxDevKnownProblems.html#interleavedfilesnotyetsupported">interleaved files not (yet) supported</a></li>
<li><a href="CryptoBoxDevKnownProblems.html#smbdsegfault">smbd: segfault</a></li>
</ol><li><a href="CryptoBoxDevKnownProblems.html#dfsbuild">dfsbuild</a></li>
<ol><li><a href="CryptoBoxDevKnownProblems.html#cantcdto_builddirtargetvarlibaptlists">can't cd to _builddir/target/var/lib/apt/lists</a></li>
</ol><li><a href="CryptoBoxDevKnownProblems.html#Comments">Comments</a></li>
</ol>
</div>
</li>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>)
</ol>
<p> </p>
<hr>
<p> </p>
<h2 id="head-3d279b986395c95455d4d831054f9664ac846790">qemu</h2>
<h3 id="head-9d223a1d9ee655c5a338f798fc08850a2b3694ba">interleaved files not (yet) supported</h3>
<p>You should update <em>qemu</em> to version 0.7 or higher. </p>
<h3 id="head-aa082f09cdb79c9a715826562efebd23cb8e9dfc">smbd: segfault</h3>
<p>This happens under certain circumstances. We do not know a solution for this problem. </p>
</p>
<hr />
<h1 id="Knownproblems">Known problems</h1>
<h2 id="qemu">qemu</h2>
<h3 id="interleavedfilesnotyetsupported">interleaved files not (yet) supported</h3>
<p>
You should update <i>qemu</i> to version 0.7 or higher.
</p>
<h3 id="smbdsegfault">smbd: segfault</h3>
<p>
This happens under certain circumstances. We do not know a solution for this problem.
</p>
<h2 id="dfsbuild">dfsbuild</h2>
<h3 id="cantcdto_builddirtargetvarlibaptlists">can't cd to _builddir/target/var/lib/apt/lists</h3>
<p>
This can be caused by a (strange) mix of debian package versions. Track this bug at <a class="ext-link" title="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320991" href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320991">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320991</a>.
</p>
<hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

147
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevPreparation.html
View file

@ -29,91 +29,82 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-5b50aeed8139c95e5a2670d4248978d942c5edd6">Software requirements</a>
<ol>
<li>
<a href="#head-143e3ec00a024bf2d9486f21dccab7ddc0ac3709">Packages</a>
</li>
<li>
<a href="#head-8abff5fecd19a74f1f5602aa82c8783c80b6862e">Kernel</a>
</li>
<li><a href="CryptoBoxDevPreparation.html#Softwarerequirements">Software requirements</a></li>
<ol><li><a href="CryptoBoxDevPreparation.html#Packages">Packages</a></li>
<li><a href="CryptoBoxDevPreparation.html#Kernel">Kernel</a></li>
</ol><li><a href="CryptoBoxDevPreparation.html#Getthesource">Get the source</a></li>
<li><a href="CryptoBoxDevPreparation.html#Firstbuild">First build</a></li>
<li><a href="CryptoBoxDevPreparation.html#Finished">Finished</a></li>
<li><a href="CryptoBoxDevPreparation.html#Comments">Comments</a></li>
</ol>
</div>
<li>
<a href="#head-e988a63aa4744649892e3c85e239927edb01f336">Get the source</a>
</li>
<li>
<a href="#head-3b183abdfebed7afdbbdbb7625f85081882beb70">First build</a>
</li>
<li>
<a href="#head-08bd0ad2103b9f58bd026d64c0bcb333f3bbd90b">Finished</a>
</li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
<h2 id="head-5b50aeed8139c95e5a2670d4248978d942c5edd6">Software requirements</h2>
<h3 id="head-143e3ec00a024bf2d9486f21dccab7ddc0ac3709">Packages</h3>
<p>We use <a class="external" href="http://debian.org">Debian</a> as our development environment. This was a natural choice, as the <a href="CryptoBox.html">CryptoBox</a>-LiveCD is also based on Debian. Other distributions should work too, of course - <a class="interwiki" title="Acronym" href="http://www.acronymfinder.com/af-query.asp?String=exact&amp;Acronym=YMMV">YMMV</a>. </p>
<p>required: </p>
<ul>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a> </p>
</li>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=subversion">subversion</a> </p>
</li>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=chroot">chroot</a> </p>
</li>
</ul>
<p>recommended: </p>
<ul>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=apt-cacher">apt-cacher</a>, <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=apt-proxy">apt-proxy</a> or <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=approx">approx</a> </p>
</li>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=qemu">qemu</a> </p>
</li>
<li><p> <a class="interwiki" title="DebianPackage" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=1&amp;version=all&amp;release=all&amp;keywords=curl">curl</a> </p>
</li>
</ul>
<h3 id="head-8abff5fecd19a74f1f5602aa82c8783c80b6862e">Kernel</h3>
<p>If you want to use <a class="external" href="http://fabrice.bellard.free.fr/qemu/">qemu</a> to test your <a href="CryptoBox.html">CryptoBox</a> in a virtual environment, then you will need the <em>tun/tap</em> kernel feature.
</p>
<pre>
CONFIG_TUN=m</pre>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>, <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a>, <a href="/trac/cryptobox/wiki/CryptoBoxDevWorkFlow">CryptoBoxDevWorkFlow</a>)
<h2 id="head-e988a63aa4744649892e3c85e239927edb01f336">Get the source</h2>
<p>Download the latest release from our <a class="external" href="http://subversion.tigris.org">subversion</a>-Repository:
</p>
<pre>
svn checkout https://svn.systemausfall.org/svn/cryptobox/trunk </pre>
<h2 id="head-3b183abdfebed7afdbbdbb7625f85081882beb70">First build</h2>
<p>run <tt>scripts/cbox-build.sh&nbsp;release</tt> as <em>root</em> - hopefully, there should be no errors <img src="../../../var/www/cryptobox-img/smile.png" alt=":)" height="15" width="15"> </p>
<p>Hint: This step will fail, if you did not install <em>apt-cacher</em>. See <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> for details on how to change the build-configuration settings (in this case: <em>mirror</em> in <em>dfs-cbox.conf</em>). </p>
<h2 id="head-08bd0ad2103b9f58bd026d64c0bcb333f3bbd90b">Finished</h2>
<p>Now you can start to pariticipate in the development of the <a href="CryptoBox.html">CryptoBox</a> or simply customize your own <a href="CryptoBox.html">CryptoBox</a>-LiveCD. </p>
<p>See <a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a> for details of how to use the developer's tools of the <a href="CryptoBox.html">CryptoBox</a>. </p>
<p><a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> shows some examples for local customizations of the <a href="CryptoBox.html">CryptoBox</a>. </p>
<hr />
<h1 id="Preparationsfordevelopers">Preparations for developers</h1>
<h2 id="Softwarerequirements">Software requirements</h2>
<h3 id="Packages">Packages</h3>
<p>
We use <a class="ext-link" title="http://debian.org" href="http://debian.org">Debian</a> as our development environment. This was a natural choice, as the CryptoBox-LiveCD is also based on Debian. Other distributions should work too, of course - <i>your mileage may vary</i>.
</p>
<p>
required:
</p>
<ul><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=dfsbuild">dfsbuild</a>
</li><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=subversion" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=subversion">subversion</a>
</li><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=chroot" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=chroot">chroot</a>
</li></ul><p>
recommended:
</p>
<ul><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-cacher" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-cacher">apt-cacher</a>, <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-proxy" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=apt-proxy"> apt-proxy</a> or <a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=approx" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=approx">approx</a>
</li><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=qemu" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=qemu">qemu</a>
</li><li><a class="ext-link" title="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=curl" href="http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&amp;subword=0&amp;version=all&amp;release=all&amp;keywords=curl">curl</a>
</li></ul><h3 id="Kernel">Kernel</h3>
<p>
If you want to use <a class="ext-link" title="http://fabrice.bellard.free.fr/qemu/" href="http://fabrice.bellard.free.fr/qemu/">qemu</a> to test your <a href="CryptoBox.html">CryptoBox</a> in a virtual environment, then you will need the <i>tun/tap</i> kernel feature.
</p>
<pre class="wiki">CONFIG_TUN=m
</pre><h2 id="Getthesource">Get the source</h2>
<p>
Download the latest release from our <a class="ext-link" title="http://subversion.tigris.org" href="http://subversion.tigris.org">subversion</a>-Repository:
</p>
<pre class="wiki">svn checkout https://svn.systemausfall.org/svn/cryptobox/trunk
</pre><h2 id="Firstbuild">First build</h2>
<p>
run <tt>scripts/cbox-build.sh release</tt> as <i>root</i> - hopefully, there should be no errors :)
</p>
<p>
Hint: This step will fail, if you did not install <i>apt-cacher</i>. See <a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> for details on how to change the build-configuration settings (in this case: <i>mirror</i> in <i>dfs-cbox.conf</i>).
</p>
<h2 id="Finished">Finished</h2>
<p>
Now you can start to pariticipate in the development of the <a href="CryptoBox.html">CryptoBox</a> or simply customize your own CryptoBox-LiveCD.
</p>
<p>
See <a href="CryptoBoxDevWorkFlow.html">CryptoBoxDevWorkFlow</a> for details of how to use the developer's tools of the <a href="CryptoBox.html">CryptoBox</a>.
</p>
<p>
<a href="CryptoBoxDevCustomBuild.html">CryptoBoxDevCustomBuild</a> shows some examples for local customizations of the <a href="CryptoBox.html">CryptoBox</a>.
</p>
<hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">

123
v0.2.1/cbox-tree.d/_offline/doc/de/CryptoBoxDevValidation.html
View file

@ -29,62 +29,83 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-5e20146fd39363329427c6251209cccb8d374f3e">Overview</a>
</li>
<li>
<a href="#head-6e1d416048c4d8ebfb5b3919b4d924c77e652a7b">Validate</a>
</li>
<li>
<a href="#head-5634566bd24f83d397b43525fc62685f6e678fbf">How to create a test</a>
</li>
<li><a href="CryptoBoxDevValidation.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevValidation.html#Validate">Validate</a></li>
<li><a href="CryptoBoxDevValidation.html#Howtocreateatest">How to create a test</a></li>
<li><a href="CryptoBoxDevValidation.html#Comments">Comments</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
</div>
<h2 id="head-5e20146fd39363329427c6251209cccb8d374f3e">Overview</h2>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>)
<p>The validation feature allows to check the programming logic of the <a href="CryptoBox.html">CryptoBox</a>. A lot of test cases are defined to test as many functions of the <a href="CryptoBox.html">CryptoBox</a> as possible. </p>
<p>The requests are processed with <a class="external" href="http://curl.haxx.se/">curl</a>. </p>
<p>The received web page is saved to allow a later design review or css debugging. </p>
<p>The current state of the <a href="CryptoBox.html">CryptoBox</a> is represented by ten single values (e.g.: <em>box is configured</em>, <em>IP of the box</em>, <em>current language setting</em>, ...), 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. </p>
<p>Similar test cases are pooled into test groups (e.g.: <em>initialization</em>, <em>configuration</em> and <em>mounting</em>). </p>
<h2 id="head-6e1d416048c4d8ebfb5b3919b4d924c77e652a7b">Validate</h2>
<p>Run <tt>scripts/validate.sh&nbsp;check_all</tt> to conduct all tests of all groups. See <tt>scripts/validate.sh&nbsp;help</tt> for other actions. </p>
<p>The results will be saved in <em>validation/report</em>. </p>
<p>In addition to every single retrieved page, a html page called <em>summary.html</em> is created, which contains the state checks of all tests in a group. </p>
<h2 id="head-5634566bd24f83d397b43525fc62685f6e678fbf">How to create a test</h2>
<p>All test cases can be found in <em>validation/test-cases</em>. </p>
<p>Every test consists of: </p>
<dl>
<dt>input.curl</dt>
<dd><p>the configuration file for the <em>curl</em> request </p>
</dd>
<dt>output</dt>
<dd><p>the predicted state of the <a href="CryptoBox.html">CryptoBox</a> after the call </p>
</dd>
<dt>description</dt>
<dd><p>a short description of the test (will be used for the summary) </p>
</dd>
<dt>delay</dt>
<dd><p>[optional] time to wait after this test </p>
</dd>
</dl>
<p>Use the existing test cases as templates for new tests. </p>
<p>Any logical path of the web interface CGI should be validated by a test case. </p>
</p>
<hr />
<h1 id="ValidationoftheCryptoBox">Validation of the CryptoBox</h1>
<h2 id="Overview">Overview</h2>
<p>
The validation feature helps you to check the programming logic of the <a href="CryptoBox.html">CryptoBox</a>. A lot of test cases are defined to verify as many functions of the <a href="CryptoBox.html">CryptoBox</a> as possible.
</p>
<p>
The requests are processed with <a class="ext-link" title="http://curl.haxx.se/" href="http://curl.haxx.se/">curl</a>.
</p>
<p>
The received web page is saved to allow a later design review or css debugging.
</p>
<p>
The current state of the <a href="CryptoBox.html">CryptoBox</a> is represented by ten single values (e.g.: <i>box is configured</i>, <i>IP of the box</i>, <i>current language setting</i>, ...), 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.
</p>
<p>
Similar test cases are pooled into test groups (e.g.: <i>initialization</i>, <i>configuration</i> and <i>mounting</i>).
</p>
<h2 id="Validate">Validate</h2>
<p>
Run <i><a href="/trac/cryptobox/browser/trunk/scripts/validate.sh">scripts/validate.sh</a>]</i> to conduct all tests of all groups. See <i>scripts/validate.sh help</i> for other actions.
</p>
<p>
The results will be saved in <i>validation/report</i>.
</p>
<p>
In addition to every single retrieved page, a html page called <i>summary-?.html</i> is created, which contains the state checks of all tests in a group.
</p>
<h2 id="Howtocreateatest">How to create a test</h2>
<p>
All test cases can be found in <i>validation/test-cases</i>.
</p>
<p>
Every test consists of the following files:
</p>
<table class="wiki">
<tr><td>input.curl</td><td>the configuration file for the <i>curl</i> request
</td></tr><tr><td>output</td><td>the predicted state of the <a href="CryptoBox.html">CryptoBox</a> after the call
</td></tr><tr><td>description</td><td>a short description of the test (will be used for the summary)
</td></tr><tr><td>delay</td><td>[optional] time to wait after this test
</td></tr></table>
<p>
Use the existing test cases as templates for new tests.
</p>
<p>
Read <a href="/trac/cryptobox/browser/trunk/validation/test-cases/README">validation/test-cases/README</a> for details.
</p>
<p>
Every logical path of the web interface CGI should be validated by a test case.
</p>
<hr />
<h2 id="Comments">Comments</h2>
<p>