kernel config file added

dfsbuild: changed 'sarge' to 'stable'
fixed 'TEMPLATE_DIR' ambiguity
web user interface improved (more state dependent)
doc: update
minor language improvement
This commit is contained in:
lars 2005-09-14 01:57:56 +00:00
parent 0dad80f2b1
commit dd99c01b7a
14 changed files with 1433 additions and 351 deletions

View file

@ -8,7 +8,7 @@ SCAN_DEVICES="/dev/hda /dev/hdb /dev/hdc /dev/hde /dev/hdf /dev/hdg /dev/scd0 /d
# directories
LANGUAGE_DIR=/usr/share/cryptobox/lang
TEMPLATE_DIR=/usr/share/cryptobox/templates
HTML_TEMPLATE_DIR=/usr/share/cryptobox/templates
DOC_DIR=/usr/share/doc/cryptobox/html
CONFIG_DEFAULTS_DIR=/usr/share/cryptobox/defaults
CONFIG_DIR=/mnt/cb-etc

View file

@ -134,7 +134,7 @@ function create_crypto()
{
local device="$1"
# flood the crypto partition with noise
# - not needed -
# TODO: do we need "wipe"?
#$WIPE -kq -R /dev/urandom "${device}2"
# passphrase may be passed via command line

View file

@ -190,7 +190,7 @@ Lang {
NoSSL {
Title = Unverschlüsselte Verbindung
Text = Die CryptoBox akzeptiert nur verschlüsselte Verbindungen (https). So bleibt das Passwort vor neugierigen Augen geschützt.
Text = Die CryptoBox akzeptiert nur verschlüsselte Verbindungen (https). So bleibt das Passwort vor neugierigen Augen geschützt. In wenigen Sekunden wird eine verschlüsselte Verbindung hergestellt.
}
InitFailed {

View file

@ -3,73 +3,15 @@
<ol>
<li>
<a href="#head-83e76c6d82be992b637e79ec274326a77779ba0e">Some more dev-pages</a>
<a href="#head-73b6f7ae7db09b8e77e234854ce9c32d84ef23cb">Development documentation</a>
</li>
<li>
<a href="#head-6eb518f032b739c4ddc4336b19cefd3fa16e20aa">Komponenten</a>
<ol>
<li>
<a href="#head-734d8f8dd2dc75137657154aab53d33f64f891bd">dfsbuild</a>
<a href="#head-ecdf55e59e852c76061f53d058b3fa698652c6c9">Contact</a>
</li>
<li>
<a href="#head-693b97f1f140e361364dcc277c0afa779430f527">cbox-build</a>
<ol>
<li>
<a href="#head-5850d37242fe07221892c0126989304825831e5c">Beispiele</a>
</li>
</ol>
<li>
<a href="#head-b4a0271d176c624fda4d38f5c138aefe0a329bca">der CryptoBox-Kernel</a>
</li>
<li>
<a href="#head-d81befa59fe38bcf5ffae7c0c4c42141d74395eb">Verwendung des Subversion-Repositories</a>
</li>
</ol>
<li>
<a href="#head-488d495ca9bbbac0c903c2de823c13efa299cc43">Ablauf</a>
<ol>
<li>
<a href="#head-ccb175f65be28296434126b424a7d8d0ca40c4c5">der erste Bootvorgang</a>
</li>
<li>
<a href="#head-ae7819ff9abff3fbdc393673215b858ba4528109">per webfrontend mounten</a>
</li>
</ol>
<li>
<a href="#head-2968dfa19053089622a83f46a999c6d2f8d0c7de">Bugs</a>
</li>
<li>
<a href="#head-3627c73e59109bcdb97aeeb51d07efa784bb633e">Hints</a>
</li>
<li>
<a href="#head-4b1cd21b02476764e3cb220094117e69699f3ba9">andere Ansätze</a>
<ol>
<li>
<a href="#head-032dea2c5aba735742a9e935ee55629bf2739194">Knoppix</a>
</li>
<li>
<a href="#head-0eec3ed15826633b2667c982fb486e988514faac">Morphix / IBuild</a>
</li>
</ol>
<a href="#head-ff05e9c9617ceac43a54362db1e9045c13512416">Bug reports</a>
</li>
</ol>
@ -77,8 +19,9 @@
<hr>
<p> </p>
<h2 id="head-83e76c6d82be992b637e79ec274326a77779ba0e">Some more dev-pages</h2>
<h2 id="head-73b6f7ae7db09b8e77e234854ce9c32d84ef23cb">Development documentation</h2>
<p>The following pages are written for developers only. Users of the <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> should read <a class="nonexistent" href="/cryptobox?action=doc&page=CryptoBoxUser">?</a>CryptoBoxUser instead. </p>
<ul>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxDevPreparation">CryptoBoxDevPreparation</a> </p>
</li>
@ -90,281 +33,23 @@
</li>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxDevValidation">CryptoBoxDevValidation</a> </p>
</li>
</ul>
<h2 id="head-6eb518f032b739c4ddc4336b19cefd3fa16e20aa">Komponenten</h2>
<p>Eine <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> CD wird in wenigen Schritten erstellt. Die Basisarbeit erledigt 'dfsbuild' und die genaue Konfiguration macht 'cbox-build'. </p>
<h3 id="head-734d8f8dd2dc75137657154aab53d33f64f891bd">dfsbuild</h3>
<p>Das Linux Grundsystem für die <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> CD wird mit <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> gebaut. Das ist ein Programm, welches eine <a class="external" href="http://www.debian.org">Debian</a> Live-CD erzeugt.<br>
<em>(Wir entwickeln die <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> bisher auf Debian/Linux-Systemen. Prinzipiell dürfte es auch mit deiner Lieblingsdistro funktionieren, nur der anfängliche Einrichtungsaufwand wird dadurch größer.)</em> </p>
<p>Für "dfsbuild" bietet sich <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> an. Damit brauchst du nicht für jeden Bau des Grundsystems alle Debian-Pakete erneut herunter laden. </p>
<p>Installation: </p>
<ul>
<li><p> <tt>apt-get&nbsp;install&nbsp;dfsbuild&nbsp;apt-cacher</tt> </p>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxDevBackground">CryptoBoxDevBackground</a> </p>
</li>
</ul>
<p>Die <em>dfsbuild</em>-Dokumentation ist noch recht spärlich. Du kommst aber kaum in direkten Kontakt mit <em>dfsbuild</em>, da es durch 'scripts/cbox-build.sh' aufgerufen wird. Die folgenden Links helfen dir vielleicht trotzdem weiter: </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><p> <a href="/cryptobox?action=doc&page=CryptoBoxDevKnownProblems">CryptoBoxDevKnownProblems</a> </p>
</li>
</ul>
<h3 id="head-693b97f1f140e361364dcc277c0afa779430f527">cbox-build</h3>
<h2 id="head-ecdf55e59e852c76061f53d058b3fa698652c6c9">Contact</h2>
<p>Die wichtige Kleinarbeit, damit aus dem dfsbuild-System eine <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> wird, erledigt <em>scripts/cbox-build.sh</em>.<br>
Das Script und die bestehenden Konfigurationsdateien liegen im <a class="interwiki" title="SubVersion" href="/websvn/cryptobox">cryptobox-Repository</a>. </p>
<p>Mit diesem Script baust du deine eigene <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a>-CD. Hier ein verkürzter Überblick: </p>
<div>
<table>
<tr>
<td>
<p> <em>Aktion</em> </p>
</td>
<td>
<p> <em>Beschreibung</em> </p>
</td>
</tr>
<tr>
<td>
<p> dfsbuild </p>
</td>
<td>
<p> startet dfsbuild und legt eine Arbeitskopie an </p>
</td>
</tr>
<tr>
<td>
<p> config </p>
</td>
<td>
<p> konfiguriert das Basissystem </p>
</td>
</tr>
<tr>
<td>
<p> harden </p>
</td>
<td>
<p> entfernt das <em>devel-feature.sh</em> Skript und einige unnötige Pakete </p>
</td>
</tr>
<tr>
<td>
<p> iso </p>
</td>
<td>
<p> erstellt ein iso-image </p>
</td>
</tr>
<tr>
<td>
<p> chroot </p>
</td>
<td>
<p> für kleine Tests reicht auch chroot (<strong>Vorsicht</strong>: dabei riskierst du, deine reale Festplatte zu überschreiben) </p>
</td>
</tr>
<tr>
<td>
<p> qemu </p>
</td>
<td>
<p> startet das iso-image mit <em>qemu</em> (zum sicheren Testen) </p>
</td>
</tr>
<tr>
<td>
<p> revert </p>
</td>
<td>
<p> Wiederherstellung des dfsbuild-Endprodukts - falls mensch mit <em>config</em> die Arbeitskopie übertrieben verschmutzt hat </p>
</td>
</tr>
<tr>
<td>
<p> release </p>
</td>
<td>
<p> Abkürzung für <em>dfsbuild config harden iso</em> - es wird also eine Release-CD erstellt </p>
</td>
</tr>
</table>
</div>
<p>Das kannst mehrere Aktionen nacheinander als Parameter angeben. </p>
<p>Weitere Aktionen, die die Entwicklung erleichtern, werden unter <a href="/cryptobox?action=doc&page=CryptoBoxDevFeatures">CryptoBoxDevFeatures</a> beschrieben. </p>
<p>Das fertige iso-Image findest du unter <em>_builddir/cd1/cryptobox.iso</em>. </p>
<p>We are waiting for your emails to <em>cryptobox[at]systemausfall.org</em>. </p>
<h4 id="head-5850d37242fe07221892c0126989304825831e5c">Beispiele</h4>
<h2 id="head-ff05e9c9617ceac43a54362db1e9045c13512416">Bug reports</h2>
<dl>
<dt>Die erste Erstellung des Grundsystems</dt>
<dd><p><tt>./cbox-build.sh&nbsp;dfsbuild</tt> </p>
</dd>
<dt>Anpassungen vornehmen, ISO-Image erstellen und per ''qemu'' testen</dt>
<dd><p><tt>scripts/cbox-build.sh&nbsp;config&nbsp;iso;&nbsp;scripts/cbox-dev.sh&nbsp;qemu</tt> </p>
</dd>
</dl>
<ul>
<li style="list-style-type:none"><p>komplette Release-CD erstellen: <tt>scripts/cbox-build.sh&nbsp;release</tt> </p>
</li>
</ul>
<h3 id="head-b4a0271d176c624fda4d38f5c138aefe0a329bca">der CryptoBox-Kernel</h3>
<p>Der Kernel für die <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> wird statisch kompiliert. Wenn du ihn selbst bauen/verändern willst, dann am einfachsten so: </p>
<ul>
<li><p> apt-get install kernel-tree-2.6.8 </p>
</li>
<li><p> schnapp dir /boot/config-2.6.8 von einer gebauten <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> CD und verändere sie nach deinen Wünschen </p>
</li>
<li><p> zum Erstellen des Debian-Pakets: <tt>&nbsp;make-kpkg&nbsp;--revision=1.dfs&nbsp;--rootcmd=fakeroot&nbsp;kernel_image</tt> </p>
</li>
<li><p> nun musst du eventuell in der <em>dfsbuild.conf</em> den Namen des vorherigen Kernel-Pakets durch deinen neuen ersetzen </p>
</li>
</ul>
<h3 id="head-d81befa59fe38bcf5ffae7c0c4c42141d74395eb">Verwendung des Subversion-Repositories</h3>
<p>Erstellung einer lokalen Arbeitskopie des Entwickler-Repositories: <tt>svn&nbsp;checkout&nbsp;https://svn.systemausfall.org/svn/cryptobox&nbsp;deincryptoboxverzeichnis</tt> </p>
<p>Deine Änderungen an der <a href="/cryptobox?action=doc&page=CryptoBox">CryptoBox</a> klannst du per <tt>svn&nbsp;commit</tt> in unser Repository übertragen. Dazu musst du, aber vorher Schreibrechte erhalten (die wir gerne vergeben). <img src="/cryptobox-img/smile.png" alt=":)" height="15" width="15"> </p>
<h2 id="head-488d495ca9bbbac0c903c2de823c13efa299cc43">Ablauf</h2>
<p>Hier werden wichtige interne Abläufe der Cryptobox beschrieben. </p>
<h3 id="head-ccb175f65be28296434126b424a7d8d0ca40c4c5">der erste Bootvorgang</h3>
<ul>
<li><p> checken ob config partition auf der platte liegt </p>
<ul>
<li><p> testmount der ersten partition </p>
</li>
</ul>
</li>
<li><p> wenn ja, configs einlesen und system normal starten </p>
</li>
<li><p> wenn nicht: </p>
<ul>
<li><p> webserver starten und anbieten die gefundene platte "hinzurichten" </p>
<ul>
<li><p> nutzerdaten sammeln (ip adresse, netzwerkname usw.) </p>
</li>
<li><p> <em>abfrage ob wirklich: wipe -f -k -R /dev/urandom /dev/?d? (fortschritt anzeigen)</em> </p>
<ul>
<li><p> <em>wenn nicht, dann hilfeseite zeigen</em> </p>
</li>
</ul>
</li>
<li><p> partitionen anlegen </p>
<ul>
<li><p> erste part. mkfs &amp; mount (config) </p>
</li>
<li><p> fstab drauf schreiben </p>
</li>
<li><p> crypttab dito </p>
</li>
<li><p> interfaces dito </p>
</li>
<li><p> smb.conf dito </p>
</li>
</ul>
</li>
<li><p> kennwort abfrage per cgi </p>
</li>
<li><p> zweite part. cryptsetup &amp; mkfs &amp; mount (crypto) </p>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3 id="head-ae7819ff9abff3fbdc393673215b858ba4528109">per webfrontend mounten</h3>
<ul>
<li><p> pw abfrage </p>
</li>
<li><p> checken ob mount geklappt hat </p>
</li>
<li><p> samba starten </p>
</li>
<li><p> ... </p>
</li>
<li><p> nach timeout oder auf wunsch samba stoppen </p>
</li>
<li><p> cryptodevice entfernen </p>
</li>
</ul>
<hr>
<p> </p>
<h2 id="head-2968dfa19053089622a83f46a999c6d2f8d0c7de">Bugs</h2>
<ul>
<li><p> unter qemu trat immer wieder ein Fehler "interleaved files not (yet) supported" auf </p>
<ul>
<li><p> willkürlich waren manche Verzeichnisse ungültig (also hatten nur das Datei-Attribut) </p>
</li>
<li><p> die nicht-standardkonformen mkisofs-Optionen "-U -D" haben das Problem nicht behoben </p>
</li>
</ul>
</li>
<li><p> eventuell hängt dies mit dem vorherigen Fehler zusammen: das System verhält sich systematisch fehlerhaft (beispielsweise löst der Start von <em>nmbd</em> generell ein <em>segfault</em> aus) </p>
</li>
</ul>
<h2 id="head-3627c73e59109bcdb97aeeb51d07efa784bb633e">Hints</h2>
<ul>
<li><p> Du brauchst etwa 1GB Plattenplatz für den Bau einer Cryptobox. Das eigentliche CD-Image wird aber nur knapp 250MB groß. </p>
</li>
<li><p> Für <em>dfsbuild</em> bietet sich <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> an. Damit müssen die Debian-Pakete nicht bei jedem neuen <em>dfsbuild</em>-Vorgang erneut heruntergeladen werden. </p>
</li>
<li><p> cbox-build muss für folgende Vorgänge mit root Rechten laufen: <tt>dfsbuild,&nbsp;config,&nbsp;chroot,&nbsp;revert</tt> </p>
</li>
<li><p> <em>cbox-build.sh</em> verwendet relative Pfad-Angaben - du solltest es also aus dem Verzeichnis heraus starten, in dem sich beispielsweise auch <em>cbox-build.sh</em> befindet. </p>
</li>
<li><p> Netzwerk für <em>qemu</em>: </p>
<ul>
<li><p> dein Systemkernel muss das <em>tun/tap</em>-Netzwerkgerät unterstützen
</p>
<pre>
CONFIG_TUN=m</pre>
</li>
<li><p> eventuell musst du "misc/qemu-ifup.sh" an dein System anpassen </p>
</li>
</ul>
</li>
</ul>
<hr>
<p> </p>
<h2 id="head-4b1cd21b02476764e3cb220094117e69699f3ba9">andere Ansätze</h2>
<p>Hier findest du ältere Ideen, die zum Teil schon recht umfangreiche Gestalt angenommen haben aber momentan von uns nicht weiter verfolgt werden. </p>
<h3 id="head-032dea2c5aba735742a9e935ee55629bf2739194">Knoppix</h3>
<ul>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxKnoppixVerworfen">CryptoBoxKnoppixVerworfen</a> </p>
</li>
</ul>
<h3 id="head-0eec3ed15826633b2667c982fb486e988514faac">Morphix / IBuild</h3>
<ul>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxMorphixVerworfen">CryptoBoxMorphixVerworfen</a> </p>
</li>
</ul>
<p>Please use our issue tracker, if you discover problems: <a href="https://systemausfall.org/trac/cryptobox">https://systemausfall.org/trac/cryptobox</a> </p>
<a id="bottom"></a>
</div>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-08 14:56:51 by <span title="">lars</span></p>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-13 23:50:26 by <span title="">lars</span></p>
</div> <!-- end page -->

View file

@ -0,0 +1,74 @@
<a id="top"></a>
<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>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="/cryptobox?action=doc&page=CryptoBoxDev">CryptoBoxDev</a></em> </p>
<h2 id="head-2d71165918ee9e861cebf562e7f9be2c5c6328e4">dfsbuild</h2>
<p>The base system of the <a href="/cryptobox?action=doc&page=CryptoBox">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?action=doc&page=CryptoBox">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="/cryptobox?action=doc&page=CryptoBoxDevCustomBuild">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?action=doc&page=CryptoBox">CryptoBox</a>: </p>
<ul>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxKnoppixVerworfen">CryptoBoxKnoppixVerworfen</a> - Knoppix </p>
</li>
<li><p> <a href="/cryptobox?action=doc&page=CryptoBoxMorphixVerworfen">CryptoBoxMorphixVerworfen</a> - Morphix / IBuild </p>
</li>
</ul>
<a id="bottom"></a>
</div>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-13 23:03:58 by <span title="">lars</span></p>
</div> <!-- end page -->

View file

@ -0,0 +1,37 @@
<a id="top"></a>
<ol>
<li>
<a href="#head-3d279b986395c95455d4d831054f9664ac846790">qemu</a>
<ol>
<li>
<a href="#head-aa082f09cdb79c9a715826562efebd23cb8e9dfc">smbd: segfault</a>
</li>
</ol>
</li>
</ol>
<p> </p>
<hr>
<p> </p>
<h2 id="head-3d279b986395c95455d4d831054f9664ac846790">qemu</h2>
<p>== interleaved files not (yet) supported = 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>
<a id="bottom"></a>
</div>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-13 23:17:39 by <span title="">lars</span></p>
</div> <!-- end page -->

View file

@ -4,14 +4,24 @@
<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>
</ol>
<li>
<a href="#head-e988a63aa4744649892e3c85e239927edb01f336">Get the source</a>
</li>
<li>
<a href="#head-6524f2e3068fa6e4eb4e9fb3c4b84b34cf36b353">First try</a>
<a href="#head-3b183abdfebed7afdbbdbb7625f85081882beb70">First build</a>
</li>
<li>
@ -26,6 +36,9 @@
<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?action=doc&page=CryptoBox">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>
@ -46,6 +59,13 @@
</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?action=doc&page=CryptoBox">CryptoBox</a> in a virtual environment, then you will need the <em>tun/tap</em> kernel feature.
</p>
<pre>
CONFIG_TUN=m</pre>
<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:
@ -53,10 +73,10 @@
<pre>
svn checkout https://svn.systemausfall.org/svn/cryptobox/trunk </pre>
<h2 id="head-6524f2e3068fa6e4eb4e9fb3c4b84b34cf36b353">First try</h2>
<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="/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="/cryptobox?action=doc&page=CryptoBoxDevCustomBuild">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>
<p>Hint: This step will fail, if you did not install <em>apt-cacher</em>. See <a href="/cryptobox?action=doc&page=CryptoBoxDevCustomBuild">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>
@ -66,7 +86,7 @@ svn checkout https://svn.systemausfall.org/svn/cryptobox/trunk </pre>
<a id="bottom"></a>
</div>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-08 14:46:15 by <span title="">lars</span></p>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-13 23:52:54 by <span title="">lars</span></p>
</div> <!-- end page -->

View file

@ -18,6 +18,7 @@
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="/cryptobox?action=doc&page=CryptoBoxDev">CryptoBoxDev</a></em> </p>
<h2 id="head-5e20146fd39363329427c6251209cccb8d374f3e">Overview</h2>
@ -30,7 +31,7 @@
<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 at <em>validation/report</em>. </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>
@ -47,13 +48,16 @@
<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 a template for new tests. </p>
<p>Any logical branch of the web interface CGI should be validated by a test case. </p>
<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>
<a id="bottom"></a>
</div>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-08 14:52:42 by <span title="">lars</span></p>
<p id="pageinfo" class="info" lang="en" dir="ltr">last edited 2005-09-13 22:09:03 by <span title="">lars</span></p>
</div> <!-- end page -->

View file

@ -13,7 +13,7 @@ use ConfigFile;
my ($pagedata, $pagename);
my ($LANGUAGE_DIR, $LANGUAGE, $TEMPLATE_DIR, $DOC_DIR);
my ($LANGUAGE_DIR, $LANGUAGE, $HTML_TEMPLATE_DIR, $DOC_DIR);
my ($CB_SCRIPT, $LOG_FILE, $IS_DEV);
my $config = ConfigFile::read_config_file('/etc/cryptobox/cryptobox.conf');
@ -23,7 +23,7 @@ $LOG_FILE = $config->{LOG_FILE};
$LANGUAGE_DIR = $config->{LANGUAGE_DIR};
# language setting may be later overriden by "weblang"
$LANGUAGE = $config->{LANGUAGE};
$TEMPLATE_DIR = $config->{TEMPLATE_DIR};
$HTML_TEMPLATE_DIR = $config->{HTML_TEMPLATE_DIR};
$DOC_DIR = $config->{DOC_DIR};
$IS_DEV = ( -e $config->{DEV_FEATURES_SCRIPT});
@ -34,9 +34,9 @@ sub load_hdf
{
my $hdf = ClearSilver::HDF->new();
my $fname = "$TEMPLATE_DIR/main.cs";
my $fname = "$HTML_TEMPLATE_DIR/main.cs";
die ("Template directory is invalid ($fname not found)!") unless (-e "$fname");
$hdf->setValue("Settings.TemplateDir","$TEMPLATE_DIR");
$hdf->setValue("Settings.TemplateDir","$HTML_TEMPLATE_DIR");
die ("Documentation directory ($DOC_DIR) not found!") unless (-d "$DOC_DIR");
$hdf->setValue("Settings.DocDir","$DOC_DIR");
@ -147,7 +147,7 @@ sub get_admin_pw
sub render
{
$pagedata->setValue("PageName","$pagename");
my $pagefile = "$TEMPLATE_DIR/main.cs";
my $pagefile = "$HTML_TEMPLATE_DIR/main.cs";
print "Content-Type: text/html\n\n";
my $cs = ClearSilver::CS->new($pagedata);
@ -363,7 +363,7 @@ if ( ! &check_ssl()) {
$pagedata->setValue('Data.Action', 'mount_form');
} elsif (&check_mounted()) {
$pagedata->setValue('Data.Warning', 'IsMounted');
$pagedata->setValue('Data.Action', 'intro');
$pagedata->setValue('Data.Action', 'umount_form');
} else {
$pagedata->setValue('Data.Action', 'mount_form');
}
@ -382,7 +382,7 @@ if ( ! &check_ssl()) {
} elsif ($action eq 'init_ask') {
if (&check_init_running()) {
$pagedata->setValue('Data.Warning', 'InitNotFinished');
$pagedata->setValue('Data.Action', 'intro');
$pagedata->setValue('Data.Action', 'config_form');
} elsif (&check_config()) {
$pagedata->setValue('Data.Warning', 'AlreadyConfigured');
$pagedata->setValue('Data.Action', 'init_form');
@ -474,7 +474,11 @@ if ( ! &check_ssl()) {
} else {
$pagedata->setValue('Data.Success', 'ConfigSaved');
}
$pagedata->setValue('Data.Action', 'intro');
if (&check_mounted()) {
$pagedata->setValue('Data.Action', 'umount_form');
} else {
$pagedata->setValue('Data.Action', 'mount_form');
}
}
}
#################### show_log #######################
@ -508,7 +512,17 @@ if ( ! &check_ssl()) {
}
###################### default ##########################
} else {
$pagedata->setValue('Data.Action', 'intro');
if (&check_init_running()) {
$pagedata->setValue('Data.Action', 'intro');
} elsif (&check_config()) {
if (&check_mounted()) {
$pagedata->setValue('Data.Action', 'umount_form');
} else {
$pagedata->setValue('Data.Action', 'mount_form');
}
} else {
$pagedata->setValue('Data.Action', 'init_form');
}
}
# check state of the cryptobox

View file

@ -1 +0,0 @@
../../usr/share/doc/cryptobox/html

View file

@ -10,6 +10,9 @@
# the build directory (will be ERASED without warning)
BUILD_DIR="$ROOT_DIR/_builddir/cd1"
# the cryptobox development files
TEMPLATE_DIR="$ROOT_DIR/cbox-tree.d"
# the iso image
IMAGE_FILE="$BUILD_DIR/cryptobox.iso"

View file

@ -17,10 +17,10 @@ version = 0.0.1
builder = sense.lab
# Repositories to mirror. Details about each one are configured below.
dlrepos = sarge
dlrepos = stable
# Repository to build the CD with. Must be in above list.
suite = sarge
suite = stable
# Whether or not to use zftree compression on ISO image
compress = no

1246
kernel/config-2.6.11 Normal file

File diff suppressed because it is too large Load diff

View file

@ -9,7 +9,7 @@ set -u
ROOT_DIR="$(dirname $(dirname $0))"
# retrieve these pages from the wiki
PAGES="CryptoBox CryptoBoxDev CryptoBoxKonzept CryptoBoxEn CryptoBoxDevPreparation CryptoBoxDevCustomBuild CryptoBoxDevWorkFlow CryptoBoxDevValidation CryptoBoxDevCustomConfigure"
PAGES="CryptoBox CryptoBoxDev CryptoBoxKonzept CryptoBoxEn CryptoBoxDevPreparation CryptoBoxDevCustomBuild CryptoBoxDevWorkFlow CryptoBoxDevValidation CryptoBoxDevCustomConfigure CryptoBoxDevBackground CryptoBoxDevKnownProblems"
# base URL
WIKI_HOST="https://systemausfall.org"