diff --git a/config/chroot_local-includes/_offline/doc/Crypto0.html b/config/chroot_local-includes/_offline/doc/Crypto0.html new file mode 100644 index 0000000..39add92 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/Crypto0.html @@ -0,0 +1,79 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

User Documentation

+

+The following pages are describing the basic usage of the CryptoBox live-CD. +

+

+The online version of this manual is a wiki, which means you can help improving the pages. If you have a question regarding the documentation, please post it on the bottom of the relevant page. The developers will answer your questions and update the manual as fast as possible. +

+

Documentation for 0.3.x releases

+
  1. CryptoBoxUserGettingStarted -- first steps to get the Cryptobox up and running +
  2. CryptoBoxUserDailyUse -- how to access your encrypted data +
+

+At the moment there is no automatic way of using an encrypted disk of the 0.2 series in a !Cryptobox running the 0.3 series. That's because we did a major redesign of the CryptoBox functionality within the last year. We're sorry for the unconveniance! +

+

Frequently Asked Questions

+
+
+ +
+ + + + + + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/activa0.png b/config/chroot_local-includes/_offline/doc/activa0.png new file mode 100644 index 0000000..d18fe90 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/activa0.png differ diff --git a/config/chroot_local-includes/_offline/doc/cartoon.html b/config/chroot_local-includes/_offline/doc/cartoon.html new file mode 100644 index 0000000..79c0043 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/cartoon.html @@ -0,0 +1,93 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

What does the CryptoBox do?

+

Usually all your files like phone numbers, love letters, bank + account data etc. are stored in plaintext on your computer's + harddisk. + All the data is accessible for everyone who has access to the harddisk. + This is very bad in case someone you don't trust gets your harddisk. + E.g. a thief that steals your notebook, or breaks into your house or company. + If the thief has your disk he/she can also read all the files that + where saved on it, no matter whether you have a login password or not - + the files are always stored in plaintext. +

+ +

The CryptoBox brings easy-to-use data encryption to your + computer. This works out of the box and does not need complicated + configuration steps.

+ +

Here comes a small usage example for the CryptoBox with an obsolete + PC as a fileserver:

+ +

Boot up the old PC with the CryptoBox live-CD. + Now you can access it with your browser via the network. + Then you partition and reformat the harddisk of the old + PC with encryption support. Therefore you provide a passphrase. + This is all done through the user friendly webinterface. + You can also plug in an external harddisk and use this to store + your encrypted data. + Afterwards you copy your sensitive data over the local + network to the CryptoBox. + It is stored on its harddisk in a secure way. + Nobody can access your data without the right passphrase. +

+
+ + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/details.html b/config/chroot_local-includes/_offline/doc/details.html new file mode 100644 index 0000000..2e7da65 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/details.html @@ -0,0 +1,135 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+ +
+

You are server admin?

+

Take a look at the README + file. There you find more detailed information about the + installation and configuration of the CryptoBox-Server + package.

+
+ +
+ +
+

Requirements for the CryptoBox live-CD

+

The CryptoBox live-CD runs on any x86 compatible PC with:

+ +

The harddisk does not need to inside the of CryptoBox computer. You + can also use external devices like USB-drives. + All drives supported by the Linux kernel (2.6.20) can be used: IDE, + SCSI, USB, FireWire, SATA, RAID, ...

+

Because of the high number of different supported storage media + we call an encrypted disk a volume. + This includes (e.g.): USB-sticks, firewire-disks, flash-drives, digital cameras, + MP3-player, MMC/SD-cards.

+
+ +
+

Requirements of the CryptoBox-Server

+

The CryptoBox-Server package can be installed on any system with at least:

+ +

In general a server package should run on any Linux + distribution, but we only provide Debian packages. So you have to + install the necessary files on your own to the right places if + you are using a different linux distribution.

+
+ +
+

File access

+

Once you openend an encrypted volume through the web frontend of + the CryptoBox you can access the volume's data within your local + network via:

+ +

The CryptoBox-Server package will smoothly integrate into your existing + fileserver. It provides mount points which can be shared via your + favourite protocols (e.g.: WebDAV or NFS).

+
+ +
+

Encryption

+

The encrypted disk partitions are LUKS + volumes. This makes it also possible to access your data directly with + every modern linux system or via FreeOTFE + (for Microsoft products).

+

You can select your favourite encryption algorithm from all + ciphers supported by the linux kernel. The default is + aes-cbc-essiv:sha256 (AES in CBC mode with ESSIV based on + SHA256).

+
+ + + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/develo0.html b/config/chroot_local-includes/_offline/doc/develo0.html new file mode 100644 index 0000000..2479fea --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/develo0.html @@ -0,0 +1,173 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

Contribute

+

You are not just a consumer. At least not in the Open Source world.

+

There are various ways to take part in improving the CryptoBox + for all of us ...

+
+ +
+ + +
+

Recent changes

+ + +
+ +
+ + +
+

Translation center

+

We want you to translate the CryptoBox!

+

This way you can help others to access the CryptoBox in their native language. + The translation center serves + this purpose. Just register and use the webinterface for translations. + It features a nice, motivating progress bar.

+

For any questions send a mail to info@cryptobox.org.

+
+ +
+

Development

+

If you are interested in what happens under the hood, visit the development corner. You can also report + bugs there.

+

The roadmap shows our goals + for the next release and the estimated release date.

+

Join + the development mailing list or participate via gmane.

+

You can also just browse the mailing list archive.

+
+ +
+

Bleeding edge source code

+

The current source code of the CryptoBox-Server package is always + available via our Subversion repository.

+

Read more ...

+
+ +
+

Thank you!

+

The whole is nothing without its parts. We would like to thank + all the people for their help (in order of appearance). So, thank you! + :)

+ +
+ +
+

Acknowledgements

+

The CryptoBox project heavily depends on the following Free Software + projects. Thanks for your hard work!

+ +

This list is by far incomplete - so: thanks to everyone involved in + improving Free Software!

+
+ + +
+ + + + + + + + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/disks_0.jpg b/config/chroot_local-includes/_offline/doc/disks_0.jpg new file mode 100644 index 0000000..d6061ee Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/disks_0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/doc_0.0.html b/config/chroot_local-includes/_offline/doc/doc_0.0.html new file mode 100644 index 0000000..9a0a2b4 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/doc_0.0.html @@ -0,0 +1,116 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

Getting started

+

+Read the following and you'll be able to set up your own CryptoBox within half an hour. +

+

+It's pretty straight forward as we're always trying to make things as easy as possible for you. +

+

Step by Step

+
  1. You need: +
    • an old computer (remove the dust first) +
    • this PC needs a network card and a CD drive +
    • a medium to store your files on (e.g. a harddisk) +
    • we will call this PC from now on CryptoBox-PC +
  2. You don't need: +
    • a monitor, keyboard and mouse (with one exception, see below). +
    • deeper knowledge of cryptography or server administration +
  3. Download the latest version of the CryptoBox live-CD from CodeCoop. It's an ~100MB iso-image. +
  4. Burn the iso-image onto a CD. +
  5. Connect the CryptoBox-PC to your local area network. +
  6. Configure the CryptoBox-PC, so that it can boot the live-CD. Therefore you may have to enter the BIOS and configure the CD-ROM as boot device. +
  7. Put the burned CryptoBox live-CD into the CD drive and start the CryptoBox-PC. +
  8. Now go to your current desktop computer which must be connected to the same network as the CryptoBox-PC is and point your browser to http://192.168.0.23. +
+

+Now, if you see a website similar to the screenshots you're ready. :) Congratulations! +Otherwise check the last steps again and take a look in the caveats section below. +

+

+Follow this link for further user documentation. There you'll find a detailed desription, how to work with the CryptoBox. +

+

+Some sites of your brand new CryptoBox require an administrative password. The default is admin as username _and_ as password. For your own sake change this as soon as possible (under "Preferences" -> "Users"). +

+

Hints

+
  • The CryptoBox has an integrated help system. Enable it by clicking on the top-right help icon. It displays some useful tips. You can disable it again, as soon as you know how things work. +
  • The CryptoBox-PC should at least have a 200MHz CPU and 64MB RAM (rule of thumb: bought after 1997) +
  • Every modern PC system should work as a CryptoBox-PC. Try to get one with low energy consumption, there is not much CPU performance necessary. +
  • The data storage media can be an internal harddisk or any external drive. +
  • You can change external drives while the !CryptoBox-PC is running or even leave it running without a connected drive at all. +
  • The "drive" may also be a USB-stick, firewire-disk, flash-drive, MMC/SD-card, MP3-player or a digital camera. +
  • If you are going to buy a new harddisk and are using a very, very old PC as CryptoBox, please keep in mind that it probably cannot handle current disk sizes! +

Caveats

+
  • Some old PCs are not able to boot from CD drives. In this case you cannot use it as CryptoBox. +
  • If you want to change the default boot device but don't know what a BIOS is, ask somebody for help! It doesn't hurt. ;) +
  • To configure the BIOS, you need a keyboard and a monitor. But this has to be done only once. +
  • Don't forget to connect your PC to your local area network! Also don't forget to connect your desktop computer to the same network, if it isn't yet. +
  • Make sure your desktop computer has a 192.168.0.x IP address (at least for the first configuration). If this says nothing to you, again ask somebody for help! +
  • If you're unsure about the network, you can also try to connect the CryptoBox-PC and your desktop computer directly with a crossover network cable. +

+

+Move on to further user documentation. +

+

+Or go back to user documentation overview. +

+
+ + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/doc_0.1.html b/config/chroot_local-includes/_offline/doc/doc_0.1.html new file mode 100644 index 0000000..ec2aa9e --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/doc_0.1.html @@ -0,0 +1,204 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

How to use the CryptoBox

+

+

Table of Contents

+
    +
  1. Basics of the web interface
  2. +
    1. Online Help
    2. +
    3. Navigation
    4. +
    5. Configuration
    6. +
    7. Shutdown
    8. +
    +
  3. Preparing Volumes
  4. +
  5. Accessing Data
  6. +
  7. Using your Harddisks without reformatting
  8. +
+ + +

+
+

Basics of the web interface

+

+Here comes a detailed description of the web interface. We usually just call it CryptoBox as it is the part you'll have most contact with. It's basically the website you're browsing through after you typed http://192.168.0.23 into your browser. +

+

Online Help

+

+The new (0.3) version of the CryptoBox is self explaining. Just follow the menu and click through the pages. +

+

+The integrated help system may support you while using the CryptoBox. It displays some useful tips (e.g. what a single form is for). Enable it by clicking on the top-right help icon. You can disable it again, as soon as you know how things work. +

+
  • help system is disabled by default: +
+

+website/screenshots/doc-0.3.x/help_d0.jpg +

+
+
  • looks like this, when enabled: +
+

+website/screenshots/doc-0.3.x/help_e0.jpg +

+
+ +

+The central place of the CryptoBox is the "Disks" section, where you manage all your encrypted and unencrypted volumes. Every single storage medium is called a volume. +

+

+You are able to use whole disks, partitions, usb-storage devices like (usb-sticks, flash-media etc.), firewire-storage devices, logical partitions and a lot more as a volume. There is a simple rule for the devices: everything that is supported by a recent Linux kernel, is also supported by the CryptoBox. +

+
  • disk overview with one volume: +
+

+website/screenshots/doc-0.3.x/disks_0.jpg +

+
+

+Each disk-symbol is representing a volume with its name underlaying. Small icons on the disk-symbol give you some more information about the volume. A red cross means, that the volume currently is not activated. A lock symbolzises an encrypted partition. If the lock is closed the volume is not activated. If an encryted volume is activated there shows up an open lock and the CryptoBox Logo in the top-right corner opens itself, too. +

+

Configuration

+

+In the "Preferences" section you can adapt the CryptoBox to your personal needs. You may set the date/time of the CryptoBox there, as well as its network address and so on. You also find the log messages there - this is very helpful in case something unexpected happened. +

+
  • preferences overview: +
+

+website/screenshots/doc-0.3.x/prefer0.jpg +

+
+

Shutdown

+

+Follow the link to the "Shutdown" section and you can reboot the CryptoBox or just turn it off. +

+
+

Preparing Volumes

+

+Every drive you connect to the CryptoBox will be shown as one or more volumes. If the device was previously formatted with a rather exotic filesystem, then you may have to format it, before you can use it via the CryptoBox. BEWARE: all data of a volume will be deleted while formatting. +

+

+If you want to store encrypted data on a volume (you should, as this is the key feature of the CryptoBox :) ), you also have to format it initially, too. +

+
  • initialization of a disk: +
+

+website/screenshots/doc-0.3.x/prepar0.jpg +

+
+

+If you format a volume with encryption support, you have to provide a good passphrase (requiered in the next step). This passphrase protects your files from curious or evil eyes. +

+

+It is good practice to give every volume a unique name (e.g.: "photo collection" or "my important files"), depending on what you're using it for. So you won't have trouble if you later connect more than one drive to the CryptoBox. +

+

+If you don't like the aotumatic formattign modus, you can divide one disk into more than one volume by partitioning it. Keep in mind that all existing data on a volume or disk will be deleted if you format or repartition it! +

+
+

Accessing Data

+

+Now you know how to set up a CryptoBox and how to prepare volumes. So you finally can put some data on your configured volume. Click in the web frontend on "Open this volume" and give the correct passphrase. +

+

+If you want to open or save files on the volumes of the CryptoBox, you just use its available network shares: click on network neighbourhood (or similar - depending on your operating system) and choose the cryptobox computer. Only currently open volumes are visible there. +

+

+In case the cryptobox computer is not visible in your network overview, you may have to search for the hostname cryptobox or its configured IP address. Maybe it can also be necessary to reboot the CryptoBox after you changed its network settings. +

+

+The following screenshots may help you to find the cryptobox in your network on different desktop systems: +

+
  • Gnome: +
+

+website/screenshots/doc-0.3.x/search0.png +

+
+
  • KDE: +
+

+website/screenshots/doc-0.3.x/search1.png +

+
+
  • Windows: +
+

+website/screenshots/doc-0.3.x/search2.png +

+
+

+Do not forget to close the volume again via the web frontend, as soon as you do not need the encrypted files any more. +

+
+

Using your Harddisks without reformatting

+

+In some cases, a disk can be used in the CryptoBox without reformatting it. This depends on the filesystem of your disk. If it is a plain (unencrypted) one and supported by the linux kernel you will not have any problems. Encrypted disks are supported only if they use a cryptsetup-luks format. Other types of disk encryption will not be accessible. +

+

+On the downside you won't be able to store your CryptoBox settings (e.g. volume name, network address) on this disk. Therefore you would need a small config partition, which is being created automatically when you partition a disk. A warning message appears if you are working without a writeable config partition. +

+
+

+Go back to user documentation overview. +

+
+
+ +
+ + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/downlo0.html b/config/chroot_local-includes/_offline/doc/downlo0.html new file mode 100644 index 0000000..5a5c191 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/downlo0.html @@ -0,0 +1,119 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+ +
+

Latest releases

+

CryptoBox-CD: 0.2.1

+

CryptoBox-Server: 0.3.4

+
+ +
+

Planned major releases:

+

CryptoBox-CD:

+
  • v0.3.x 02/15/02007
+

CryptoBox-Server:

+
  • v0.4 06/01/02007
+

Read the development roadmap + for more details.

+
+ +
+

License

+

All code is licensed under the GPL.

+

The documentation, the graphics and this website are licensed under a Creative Commons License.

+
+ +
+ +
+

CryptoBox live-CD

+

Get the latest CryptoBox live-CD image and burn it on CD.

+

CryptoBox live-CD download

+


We would like to thank codecoop.org for + providing the necessary bandwidth.

+

Alternatively you can buy a live-CD at OpenSoft.nl + for 5.95 european bugs. Note: this is an unpaid advertisement link. + So if you ask us kindly, we might send you a CD for a better price. ;)

+
+ +
+

CryptoBox-Server Debian package

+

Use the CryptoBox-Server package in your Debian/Ubuntu Linux distribution.

+

CryptoBox-Server debian package + download

+


Install it with: dpkg -i cryptobox-server.deb

+

We strongly recommend to use the server package of our + (inofficial) debian package repository, which is easier to + maintain. How to do that ist written in the FAQ.

+
+ +
+

CryptoBox-Server source files

+

Users of a non-debian-based Linux distributions are a bit + out of luck. You may try to install the source package, but you + have to adapt some paths manually.

+

cryptobox-server source + archive download

+
+ + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/en_con0.png b/config/chroot_local-includes/_offline/doc/en_con0.png new file mode 100644 index 0000000..e74b416 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/en_con0.png differ diff --git a/config/chroot_local-includes/_offline/doc/en_mount.png b/config/chroot_local-includes/_offline/doc/en_mount.png new file mode 100644 index 0000000..eca7049 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/en_mount.png differ diff --git a/config/chroot_local-includes/_offline/doc/faq.html b/config/chroot_local-includes/_offline/doc/faq.html new file mode 100644 index 0000000..77a067c --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/faq.html @@ -0,0 +1,114 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

Frequently Asked Questions

+

+We answer some common questions her. Add a comment or mail us if you have questions, that might be interesting for others, too. +

+

+

    +
  1. I successfully opened a volume. How can I access the data now?
  2. +
  3. Recently I partitioned my harddisk. Now I can open the volume without a password. Isn't it encrypted any more?
  4. +
  5. How can I restrict access to certain data?
  6. +
  7. There is a user manager available in the preferences section. What is it good for?
  8. +
  9. How do I use the server package from the Debian repository?
  10. +
+ + +

+
+

I successfully opened a volume. How can I access the data now?

+
  • CryptoBox live-CD: browse the network neighborhood for the CryptoBox (in M$ Windows), scan the network (with KDE or Gnome). If you like terminals use smbmount or mount -t smbfs to access the network share. +
  • CryptoBox-Server: you should ask your administrator, which way is the best to access the mounted volume. In case you are the administrator, then you should take a look at the configuration file for the !MountDir setting. Publish this directory via your favourite fileserver (e.g. samba, webdav, nfs, ftp, ...) and tell your users how to reach it. +

Recently I partitioned my harddisk. Now I can open the volume without a password. Isn't it encrypted any more?

+

+The partition manager creates non-encrypted volumes by default. If you want to enable encryption for a volume, then you have to format it. Be aware that this will erase all data of the volume. +

+

How can I restrict access to certain data?

+

+The CryptoBox does not support user and access management for now. Everyone in your local network can access all open volumes for reading and writing. This behavior is based on the assumption, that there are no evil guys in your local network. Please take care for this! +

+

+For the next major release (v0.4) we plan to implement user and access management. +

+

There is a user manager available in the preferences section. What is it good for?

+

+It's aimed for administrative tasks of the CryptoBox. Administrators can disable functions of the CryptoBox for other users (e.g. disabling the shutdown function). This way the webinterface can be customized to the needs of the users. The default admin password is admin, change that immediately! +

+

+Users who just want to open and close volumes do not need an administrative account. +

+

How do I use the server package from the Debian repository?

+

+The CryptoBox server package is not part of the official Debian repository (at least for now). But you can use our systemasufall.org repository for installation. +

+
  1. Add the following to your "/etc/apt/sources.list": +
    deb http://systemausfall.org/toolforge/debian unstable main
    +
  2. Run: +
    apt-get update && apt-get install cryptobox-server
    +
+
+

+Go back to user documentation overview or to the CryptoBox Homepage. +

+
+
+
+ +
+ + + + + + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/header.jpg b/config/chroot_local-includes/_offline/doc/header.jpg new file mode 100644 index 0000000..0921fe4 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/header.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/help_d0.jpg b/config/chroot_local-includes/_offline/doc/help_d0.jpg new file mode 100644 index 0000000..cb6152d Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/help_d0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/help_e0.jpg b/config/chroot_local-includes/_offline/doc/help_e0.jpg new file mode 100644 index 0000000..6226852 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/help_e0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/index.html b/config/chroot_local-includes/_offline/doc/index.html new file mode 100644 index 0000000..565d205 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/index.html @@ -0,0 +1,108 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

What is it about?

+

The CryptoBox project aims to bring data encryption to the masses.

+

Therefore we develop two Free Software packages:

+ +

Take a look at the CryptoBox usage example!
+ It may give you a better understanding of what the CryptoBox does and how it + works.

+
+ +
+ +
+

Demo

+

See the CryptoBox in action.

+
    +
  • user: admin
  • +
  • password: admin
  • +
+
+ +
+

Documentation

+

Browse through the online user + documentation site.

+
+ +
+

Details

+

Read what's under the hood.

+
+ +
+ +
+

Screenshots

+

Everybody wants some screenshots. + Here we go:

+

+
+ + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/main.css b/config/chroot_local-includes/_offline/doc/main.css new file mode 100644 index 0000000..a229917 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/main.css @@ -0,0 +1,230 @@ +body { + margin: 0; + padding: 0; + font-family: Verdana, Arial, sans-serif; + font-size: 80%; + color: #545454; + background-color: #fff; +} + +p { + margin: 0.1em 0 0.1em 0; +} + +h1 { + margin: 0; + padding: 0; + font-size: 200%; + font-weight: normal; + color: #4169E1; +} + +h2 { + margin: 0 0 5px 0; + padding: 0; + background-color: #8bbf75; + color: White; + font-size: 100%; + font-weight: normal; + text-align: left; + /* RFC: there is a font-weight above - which is valid? */ + font-weight: 800; +} + +div { + margin: 0; + padding: 0; + display: block; +} + +tt { + padding: 0.1em 0.6em 0.1em 0.6em; + font-size: 120%; + background: #fffad0; +} + +b { + font-size: 95%; +} + +div.container { + background-color: #FFF; + margin: 0 auto 0 auto; + padding: 0; + width: 740px; +} + +div.container a:link, div.container a:visited { + color: #366b30; +} + +div.navbar a { + text-decoration: none; +} + +div.container a:hover, div.container a:active { + color: #ff8a00; +} + +div#header { + padding: 2em; + margin: 0; + background-image: url(header.jpg); + background-repeat: no-repeat; + background-position: center; + height: 78px; +} + +div.centercontent { + padding: 0.3em 1ex 0.3em 1ex; + margin: 5px 5px 9px 5px; + border: 1px solid #e0e0e0; +} + +div.centercontent h2 { + padding: 0.1em 0 0.1em 0.5em; +} +div.centercontent p { + padding: 0.1em 1.8em 0.5em 0.8em; +} +div.centercontent ul { + padding: 0.1em 1.8em 0.1em 2.8em; +} + +ul { + margin-top: 0; + margin-bottom: 5px; + margin-left: 0; + padding-left: 2em; +} + +div.navbar { + display: block; + font-weight: bold; + margin: 5px 0 5px 0; + padding: 10px 0 10px 0; + border-top: 1px solid #C4C4C4; + border-bottom: 1px solid #C4C4C4; + text-align:center; +} + +div.left { + float: left; + width: 30%; + margin: 0 0 0 5px; + padding: 0; + text-align: center; +} + +div.left h2 { + text-align: left; + color: #366b30; + background-color: #eeeeec; + padding: 0 0 0 0.5em; + margin-bottom: 0.3em; +} + +div.leftcontent { + margin: 0.2em 0.4em 0.5em 0; + padding: 0.3em; + text-align: left; + border: 1px solid #e0e0e0; +} + +div.leftcontent p { + padding: 0.1em 0 0.5em 0.5em; +} + +div.content { + margin: 5px 5px 15px 31.5%; +} + +div.onecolumn { + margin: 5px 5px 9px 5px; +} + +div.content, div.onecolumn { + padding: 0.3em 1ex 0.3em 1ex; + border: 1px solid #e0e0e0; +} + +div.content h2, div.onecolumn h2 { + /* these are 2 pixels higher then those on the left side */ + /* RFC: what does that mean? Do we want this difference or not? [l] */ + padding: 0.1em 0 0.1em 0.5em; + margin: 0.1em 0 0.1em 0; +} + +div.content p, div.onecolumn p { + padding: 0.1em 0.8em 0.5em 0.8em; +} + +div.onecolumn p { + margin-top: 10px; + margin-bottom: 25px; + text-align: center; +} + +.date { + text-align: right; + font-style: italic; + font-size: 0.8em; +} + +div#footer { + margin: 20px 0 5px 0; + padding: 5px 0 5px 0; + border-top: 1px solid #C4C4C4; + border-bottom: 1px solid #C4C4C4; + font-size: 80%; + text-align: center; + clear: both; +} + + +/* FAQ headers */ +div.faq h3 { + margin: 0.5em; + font-size: 0.9em; + color: #8bbf75; +} + + +/* table of content for FAQ */ +ol.toc { + padding-left: 2em; +} + +ol.toc li { + margin-top: 0.5em; + margin-bottom: 0.5em; +} + +ol.toc a { + text-decoration: none; +} + +/* recent changes (rss feed) */ +ul.recent_changes { + padding-left: 0; + list-style-type: none; +} + +ul.recent_changes li { +} + +ul.recent_changes li h3 { + font-size: 0.9em; + margin: 2px; + text-decoration: none; +} + +ul.recent_changes li h3 a { + text-decoration: none; +} + +ul.recent_changes li p.date { + padding: 2px 2px 0 2px; + font-size: 0.8em; +} + diff --git a/config/chroot_local-includes/_offline/doc/mini_s0.jpg b/config/chroot_local-includes/_offline/doc/mini_s0.jpg new file mode 100644 index 0000000..0eb07d6 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/mini_s0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/news.html b/config/chroot_local-includes/_offline/doc/news.html new file mode 100644 index 0000000..ea065c9 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/news.html @@ -0,0 +1,150 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

NEWS: CryptoBox-Server v0.3.4 released

+

19/02/02007

+

This is a bugfix release

+

The following bug was fixed:

+ +
+ +
+

NEWS: CryptoBox-Server v0.3.3 released

+

10/02/02007

+

This release fixes some small bugs:

+ +

Additionally the following features were added:

+ +

The Slovenian and German translations are complete.

+

This release is planned to be the base for the next live-cd, which will be + published within the next week.

+
+ +
+

NEWS: CryptoBox-Server v0.3.2 released

+

08/01/02007

+

This release contains some important bugfixes:

+ +
+ +
+

NEWS: CryptoBox-Server v0.3.1 released

+

20/12/02006

+

This release contains some usability fixes for users of the Internet Explorer, + as well as some additional translations and more convenient default settings.

+
+ +
+

NEWS: CryptoBox-Server v0.3.0 released

+

15/12/02006

+

Here it comes - the earliest x-mas present 02006: the + CryptoBox-Server 0.3.0 package. It is not a live-cd, but a software package + that you can just install on your favourite linux system.

+

Take a look at the screenshots.

+

It was a long ride and this is the first milestone we reached. Be prepared + fo another 1000 miles of code.

+

The live-CD based on this new version will be released in February 02007.

+
+ +
+

NEWS: Python rewrite progress

+

19/08/02006

+

Finally the cryptobox-python-rewrite-process is in progress. + From now on you can follow discussions and participate at the + development mailinglist via gmane.

+
+ +
+

NEWS: Download interception

+

14/04/02006

+

Sorry folks, codecoop.org is temporarily down.

+

UPDATE: It is up and running again. Fetch the latest version here.

+
+ +
+

NEWS: CryptoBox code splitting

+

07/03/02006

+

We are currently splitting the CryptoBox into the + CryptoBox-Server and the Cryptobox-CD. This will let you use + the CryptoBox-Server in your favourite Linux installation.

+

Stay tuned ...

+
+ +
+

NEWS: CryptoBox-CD v0.2.1 released

+

30/10/02005

+

The latest CryptoBox version 0.2.1 is available at + codecoop.org!

+
+ + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/prefer0.jpg b/config/chroot_local-includes/_offline/doc/prefer0.jpg new file mode 100644 index 0000000..588c651 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/prefer0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/prepar0.jpg b/config/chroot_local-includes/_offline/doc/prepar0.jpg new file mode 100644 index 0000000..33c8a04 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/prepar0.jpg differ diff --git a/config/chroot_local-includes/_offline/doc/screen0.html b/config/chroot_local-includes/_offline/doc/screen0.html new file mode 100644 index 0000000..bf472d9 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/screen0.html @@ -0,0 +1,87 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

Versions 0.3.x

+

+ screenshot v0.3: activation of encrypted filesystem
+ activation of encrypted filesystem
+

+

+ screenshot v0.3: configuration
+ configuration
+

+
+ +
+

Versions 0.2.x

+

+ screenshot v0.2: activation of encrypted file system
+ activation of encrypted file system
+

+

+ screenshot v0.2: configuration
+ configuration
+

+
+ + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/search0.png b/config/chroot_local-includes/_offline/doc/search0.png new file mode 100644 index 0000000..36b2b7f Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/search0.png differ diff --git a/config/chroot_local-includes/_offline/doc/search1.png b/config/chroot_local-includes/_offline/doc/search1.png new file mode 100644 index 0000000..8dd8c99 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/search1.png differ diff --git a/config/chroot_local-includes/_offline/doc/search2.png b/config/chroot_local-includes/_offline/doc/search2.png new file mode 100644 index 0000000..256fb80 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/search2.png differ diff --git a/config/chroot_local-includes/_offline/doc/support.html b/config/chroot_local-includes/_offline/doc/support.html new file mode 100644 index 0000000..c66c722 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/support.html @@ -0,0 +1,91 @@ + + + + + CryptoBox + + + + + + + +
+ + + + +
+

Any problems?

+
    +
  1. Please read the user + documentation.
  2. +
  3. Check if the FAQ helps you to solve your problem.
  4. +
  5. Check if it is a known + issue. If so, provide some detailed information + there.
  6. +
  7. Submit a new bug report.
  8. +
+
+ +
+ +
+

Missing your language?

+

The CryptoBox is easily extensible via plugins. It also has + support for multiple languages. You can help us with some + translations.

+
+ +
+ +
+

Further questions

+

If you have more questions or if you want better answers, just send a mail + to info@cryptobox.org. Thanks!

+

And no, we don't sit on any irc channel. There's a life to live. :)

+
+ + + + + +
+ + + + + + + diff --git a/config/chroot_local-includes/_offline/doc/system0.png b/config/chroot_local-includes/_offline/doc/system0.png new file mode 100644 index 0000000..60fbbb9 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/system0.png differ diff --git a/config/chroot_local-includes/_offline/doc/trac.ico b/config/chroot_local-includes/_offline/doc/trac.ico new file mode 100644 index 0000000..3547a13 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/trac.ico differ diff --git a/config/chroot_local-includes/_offline/doc/trac.js b/config/chroot_local-includes/_offline/doc/trac.js new file mode 100644 index 0000000..2e96c75 --- /dev/null +++ b/config/chroot_local-includes/_offline/doc/trac.js @@ -0,0 +1,159 @@ +// Used for dynamically updating the height of a textarea +function resizeTextArea(id, rows) { + var textarea = document.getElementById(id); + if (!textarea || (typeof(textarea.rows) == "undefined")) return; + textarea.rows = rows; +} + +// A better way than for example hardcoding foo.onload +function addEvent(element, type, func){ + if (element.addEventListener) { + element.addEventListener(type, func, false); + return true; + } else if (element.attachEvent) { + return element.attachEvent("on" + type, func); + } + return false; +} + +// Adapted from http://www.kryogenix.org/code/browser/searchhi/ +function searchHighlight() { + if (!document.createElement) return; + + var div = document.getElementById("searchable"); + if (!div) return; + + function getSearchWords(url) { + if (url.indexOf('?') == -1) return []; + var queryString = url.substr(url.indexOf('?') + 1); + var params = queryString.split('&'); + for (var p in params) { + var param = params[p].split('='); + if (param.length < 2) continue; + if (param[0] == 'q' || param[0] == 'p') { // q= for Google, p= for Yahoo + return unescape(param[1].replace(/\+/g, ' ')).split(/\s+/); + } + } + return []; + } + + function highlightWord(node, word, searchwordindex) { + // If this node is a text node and contains the search word, highlight it by + // surrounding it with a span element + if (node.nodeType == 3) { // Node.TEXT_NODE + var pos = node.nodeValue.toLowerCase().indexOf(word.toLowerCase()); + if (pos >= 0 && !/^searchword\d$/.test(node.parentNode.className)) { + var span = document.createElement("span"); + span.className = "searchword" + (searchwordindex % 5); + span.appendChild(document.createTextNode( + node.nodeValue.substr(pos, word.length))); + var newNode = node.splitText(pos); + newNode.nodeValue = newNode.nodeValue.substr(word.length); + node.parentNode.insertBefore(span, newNode); + return true; + } + } else if (!node.nodeName.match(/button|select|textarea/i)) { + // Recurse into child nodes + for (var i = 0; i < node.childNodes.length; i++) { + if (highlightWord(node.childNodes[i], word, searchwordindex)) i++; + } + } + return false; + } + + var words = getSearchWords(document.URL); + if (!words.length) words = getSearchWords(document.referrer); + if (words.length) { + for (var w in words) { + if (words[w].length) highlightWord(div, words[w], w); + } + } +} + +function enableControl(id, enabled) { + if (typeof(enabled) == "undefined") enabled = true; + var control = document.getElementById(id); + if (!control) return; + control.disabled = !enabled; + var labels = document.getElementsByTagName("label"); + for (var i = 0; i < labels.length; i++) { + if (labels[i].htmlFor == id) { + labels[i].className = enabled ? "enabled" : "disabled"; + } + } +} + +function addWikiFormattingToolbar(textarea) { + if ((typeof(document["selection"]) == "undefined") + && (typeof(textarea["setSelectionRange"]) == "undefined")) { + return; + } + + var toolbar = document.createElement("div"); + toolbar.className = "wikitoolbar"; + + function addButton(id, title, fn) { + var a = document.createElement("a"); + a.href = "#"; + a.id = id; + a.title = title; + a.onclick = function() { try { fn() } catch (e) { } return false }; + a.tabIndex = 400; + toolbar.appendChild(a); + } + + function encloseSelection(prefix, suffix) { + textarea.focus(); + var start, end, sel, scrollPos, subst; + if (typeof(document["selection"]) != "undefined") { + sel = document.selection.createRange().text; + } else if (typeof(textarea["setSelectionRange"]) != "undefined") { + start = textarea.selectionStart; + end = textarea.selectionEnd; + scrollPos = textarea.scrollTop; + sel = textarea.value.substring(start, end); + } + if (sel.match(/ $/)) { // exclude ending space char, if any + sel = sel.substring(0, sel.length - 1); + suffix = suffix + " "; + } + subst = prefix + sel + suffix; + if (typeof(document["selection"]) != "undefined") { + var range = document.selection.createRange().text = subst; + textarea.caretPos -= suffix.length; + } else if (typeof(textarea["setSelectionRange"]) != "undefined") { + textarea.value = textarea.value.substring(0, start) + subst + + textarea.value.substring(end); + if (sel) { + textarea.setSelectionRange(start + subst.length, start + subst.length); + } else { + textarea.setSelectionRange(start + prefix.length, start + prefix.length); + } + textarea.scrollTop = scrollPos; + } + } + + addButton("strong", "Bold text: '''Example'''", function() { + encloseSelection("'''", "'''"); + }); + addButton("em", "Italic text: ''Example''", function() { + encloseSelection("''", "''"); + }); + addButton("heading", "Heading: == Example ==", function() { + encloseSelection("\n== ", " ==\n", "Heading"); + }); + addButton("link", "Link: [http://www.example.com/ Example]", function() { + encloseSelection("[", "]"); + }); + addButton("code", "Code block: {{{ example }}}", function() { + encloseSelection("\n{{{\n", "\n}}}\n"); + }); + addButton("hr", "Horizontal rule: ----", function() { + encloseSelection("\n----\n", ""); + }); + + textarea.parentNode.insertBefore(toolbar, textarea); + var br = document.createElement("br"); + br.style.clear = "left"; + textarea.parentNode.insertBefore(br, textarea); +} diff --git a/config/chroot_local-includes/_offline/doc/trac_c0.png b/config/chroot_local-includes/_offline/doc/trac_c0.png new file mode 100644 index 0000000..702eb26 Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/trac_c0.png differ diff --git a/config/chroot_local-includes/_offline/doc/trac_l0.png b/config/chroot_local-includes/_offline/doc/trac_l0.png new file mode 100644 index 0000000..38c038d Binary files /dev/null and b/config/chroot_local-includes/_offline/doc/trac_l0.png differ diff --git a/config/chroot_local-includes/_offline/shellopn.exe b/config/chroot_local-includes/_offline/shellopn.exe new file mode 100644 index 0000000..e7d91bf Binary files /dev/null and b/config/chroot_local-includes/_offline/shellopn.exe differ diff --git a/config/chroot_local-includes/_offline/shellopn.zip b/config/chroot_local-includes/_offline/shellopn.zip new file mode 100644 index 0000000..6ddb3b4 Binary files /dev/null and b/config/chroot_local-includes/_offline/shellopn.zip differ diff --git a/config/chroot_local-includes/autorun.inf b/config/chroot_local-includes/autorun.inf new file mode 100644 index 0000000..d476528 --- /dev/null +++ b/config/chroot_local-includes/autorun.inf @@ -0,0 +1,2 @@ +[autorun] +open=_offline\shellopn.exe _offline\doc\index.html diff --git a/config/chroot_local-includes/etc/cbox-dev.conf b/config/chroot_local-includes/etc/cbox-dev.conf new file mode 100644 index 0000000..0cb115b --- /dev/null +++ b/config/chroot_local-includes/etc/cbox-dev.conf @@ -0,0 +1,54 @@ +# some local settings for cbox-build.sh and validate.sh +# +# previously defined settings: +# - ROOT_DIR +# + + +####################### cbox-build ######################## + +# the build directory (will be ERASED without warning) +BUILD_DIR="$ROOT_DIR/_builddir" + +# the cryptobox development files +CBOX_DEVEL_DIR=$ROOT_DIR/cbox-tree.d + +# template for live-cd +TEMPLATE_DIR=$ROOT_DIR/live-cd-tree.d + +# the iso image +IMAGE_FILE=$BUILD_DIR/cryptobox.iso + +# temporary directory +TMP_DIR=/tmp/$(basename $0)-$$ + +# the virtual harddisk image used for qemu +HD_IMAGE=/tmp/$(basename $0)-testplatte.img + +# mkisofs options (the option "-U" is not clean, but it prevents long +# filenames from getting mapped) +# TODO: this may prevent windows user from reading the documentation +MKISOFS_OPTIONS="-allow-multidot -U -D -iso-level 3 -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 1 -boot-info-table -pad -R" + +# for burning a CD +CDWRITER=0,0,0 + + +####################### validation ######################## + +# language of validation (select web interface language) +VALIDATE_LANGUAGE=en + +# directory of the test-cases +VALIDATE_TEST_CASES_DIR=$ROOT_DIR/validation/test-cases + +# override these settings if the CryptoBox uses a non-default IP +VALIDATE_HOST_IP_DEFAULT=192.168.0.23 +VALIDATE_HOST_IP_CHANGED=192.168.0.24 + +# destination directories for the results +VALIDATE_REPORT_DIR=/tmp/cryptobox-validation-$$ +VALIDATE_REPORT_DIR=$ROOT_DIR/validation/report +VALIDATE_SUMMARY_TEMPLATE_DIR=$ROOT_DIR/validation/templates + + diff --git a/config/chroot_local-includes/etc/dfs-cbox.conf b/config/chroot_local-includes/etc/dfs-cbox.conf new file mode 100644 index 0000000..23bad8b --- /dev/null +++ b/config/chroot_local-includes/etc/dfs-cbox.conf @@ -0,0 +1,236 @@ +# arch-tag: Default configuration file +# Copyright (c) 2004 John Goerzen + +[DEFAULT] +###################################################################### +# Overall settings, set defaults for all archs +###################################################################### + +# Name of generated disc & hostname +# BEWARE: hostname does not work - you have to set the hostname manually at the end of this file +name = CryptoBox + +# Version of generated disc +version = 0.3.4 + +# Person that built it +builder = sense.lab + +# Repositories to mirror. Details about each one are configured below. +dlrepos = stable + +# Repository to build the CD with. Must be in above list. +suite = stable + +# Whether or not to use zftree compression on ISO image +compress = no + +# Files to never compress if the above is yes +# If a dir is given, that dir and everything below is not compressed +dontcompress = /boot + /etc/*boot* + /opt/dfsruntime/initrd.dfs + +# Location of dfsbuild support files +libdir = /usr/lib/dfsbuild + +# Location of docs for CD +docdir = /usr/share/doc/dfsbuild + +# Bootloader to place on CD. Choices are: +# grub-hd GRUB with ElTorito hard disk emulation (not working yet) +# grub-no-emul "raw" ElTorito image +# aboot Alpha SRM bootloader +# yaboot PowerPC bootloader +# (usually set in arch area) +#bootloader = grub-no-emul + + +# Packages to install on live FS, on all archs, besides base system +allpackages = + util-linux + grub + parted + dmsetup + perl + tar + bash + coreutils + module-init-tools + ifupdown + busybox + usbutils + pciutils + discover + hdparm + binutils + debconf + sysutils + stunnel4 + samba + hashalot + python-clearsilver + python-cherrypy + python-configobj + python-central + super + dosfstools + cryptsetup + python-m2crypto + # support for file systems + e2tools + e2fsprogs + xfsprogs + hfsutils + jfsutils + ## ntfs-3g is not in etch + #ntfs-3g + # TODO: remove the following packages for the final version + subversion + strace + ssh + vim + nano + less + lynx + w3m + screen + elinks + + +# select a mirror for the repository (apt-cacher, apt-proxy, no caching) by +# uncommenting the line of your choice +# (1) apt-cacher (default) +mirror = http://127.0.0.1/apt-cacher/ftp.debian.org/debian +# (2) apt-proxy +#mirror = http://127.0.0.1:9999/debian +# (3) no caching proxy for apt +#mirror = http://ftp.debian.org/debian + + +# Files to place on the ramdisk +ramdisk_files = /etc/resolv.conf + /etc/lvm* + /tmp + /var/tmp + /dev + /var/lib/dhcp + /var/lib/samba + /var/log + /var/cache/samba + /var/lock + /var/run + /var/state + /etc/mtab + /root + /etc/network + /var/lib/misc + /var/lib/urandom + #/etc/hotplug/.run + /var/spool/cron + +# Directories to create on live fs +makedirs = + +# Files to delete from live fs +deletefiles = /etc/rcS.d/*discover + /etc/rcS.d/*lvm + /var/log/dpkg.log + /var/log/bootstrap.log + +preparescripts = + ../scripts/prepare_target.sh + +cleanupscripts = + ../scripts/cleanup_target.sh + +###################################################################### +# Arch settings: i386 +###################################################################### + +[i386] +# Name of any kernel images to install directly from your current filesystem +#kernels = /boot/vmlinuz-2.4.27-2-386 + +# Modules to copy from host filesystem +#modules = /lib/modules/2.4.27-2-386 + +# Debs from local fs to unpack on live FS (will not be configured) +unpackdebs = + ../packages/linux-image-2.6.20_cryptobox0.3.3_i386.deb + +# Other packages to install besides the list in DEFAULT +packages = %(allpackages)s + +# Debs from local fs to install on live fs +## fetch newest ntfs-3g from debian backports +installdebs = + ../packages/cryptobox-server.deb + ../packages/ntfs-3g_1%3a1.516-1~bpo.1_i386.deb + +# Bootloader (see options under default) +bootloader = grub-no-emul + +# Extra lines for grub config +grubconfig = timeout 0 + password -md5 this_invalid_hash_protects_grub_config + +##################################################################### +# Repository configuration +###################################################################### + +# Repositories to download +[repo testing] +suite = testing + +[repo amd64] +suite = unstable +# Override default mirror +#mirror = http://debian-amd64.alioth.debian.org/pure64/ +# Override default arch +arch = amd64 + +###################################################################### +# Text to add to existing files +###################################################################### + +[appendfiles] + +/etc/network/interfaces = + auto lo eth0 + iface lo inet loopback + iface eth0 inet static + address 192.168.0.23 + netmask 255.255.255.0 + +# /etc/modules = + +/etc/profile = export TERM=vt100 + +###################################################################### +# Files to create or truncate +###################################################################### + +[createfiles] +/etc/hostname = CryptoBox + +/etc/syslog.conf = *.* /dev/tty8 + *.info /dev/tty7 + +/etc/hosts = 127.0.0.1 localhost + +/etc/kernel-img.conf = do_initrd = Yes + +# exit the samba startup script during install immediately - otherwise +# there would be /proc problems - it will get replaced later via +# live-cd-tree.d/usr/lib/cryptobox-cd/configure-cryptobox.sh +/etc/default/samba = exit + +###################################################################### +# Symlinks to create (from = to format) +###################################################################### + +# this does not work anymore +#[symlinks] +#/etc/mtab = /proc/mounts + diff --git a/config/chroot_local-includes/etc/rc3.d/S99usage_hint b/config/chroot_local-includes/etc/rc3.d/S99usage_hint new file mode 100755 index 0000000..c423759 --- /dev/null +++ b/config/chroot_local-includes/etc/rc3.d/S99usage_hint @@ -0,0 +1,6 @@ +#!/bin/sh +echo -e "\n+----------------------------------------------------------------+" +echo -e "\n The CryptoNAS has started." +echo -e "\n You can access it now via a web browser at: http://192.168.0.23" +echo -e "\n Visit cryptonas.org for help and more information." +echo -e "\n+----------------------------------------------------------------+\n" diff --git a/config/chroot_local-includes/etc/samba/smb.conf b/config/chroot_local-includes/etc/samba/smb.conf new file mode 100644 index 0000000..ed2ea24 --- /dev/null +++ b/config/chroot_local-includes/etc/samba/smb.conf @@ -0,0 +1,35 @@ +[global] + workgroup = workgroup + server string = cryptobox + # 'security' is necessary - otherwise windows clients will ask for a login and fail + security = share + dns proxy = no + log file = /var/log/samba/log.smbd + max log size = 500 + syslog only = yes + syslog = 0 + panic action = /usr/share/samba/panic-action %d + encrypt passwords = true + passdb backend = tdbsam + obey pam restrictions = yes + invalid users = root + passwd program = /usr/bin/passwd %u + passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . + socket options = TCP_NODELAY + guest ok = yes + + # the following lines should help to be visible in the network + # os level - higher than non-PDC (primary domain controller) but lower than PDC + os level = 17 + # announce ourselves to other networks + remote announce = 192.168.0.255 192.168.255.255 172.16.255.255 10.255.255.255 + # don't act as a wins server, but use wins + # if yes, don't set "wins server" + wins support = yes + # we don't want to confuse existing servers + local master = no + domain master = no + preferred master = no + +include = /var/cache/cryptobox-server/settings/misc/samba-include.conf + diff --git a/config/chroot_local-includes/etc/udev/rules.d/z99_local.rules b/config/chroot_local-includes/etc/udev/rules.d/z99_local.rules new file mode 100644 index 0000000..e71d1f6 --- /dev/null +++ b/config/chroot_local-includes/etc/udev/rules.d/z99_local.rules @@ -0,0 +1,3 @@ +# the cryptobox live-cd should not use any device mapper block devices as they +# are created by cryptsetup -> make it non-writeable for the cryptobox user +KERNEL=="dm-*", MODE="0600", OWNER="root", GROUP="root" diff --git a/config/chroot_local-includes/start.html b/config/chroot_local-includes/start.html new file mode 100644 index 0000000..40eec34 --- /dev/null +++ b/config/chroot_local-includes/start.html @@ -0,0 +1,11 @@ + + + + + The CryptoBox + + + Automatic redirect to Documentation ... + + + diff --git a/config/chroot_local-includes/usr/lib/cryptobox-cd/chroot-start.sh b/config/chroot_local-includes/usr/lib/cryptobox-cd/chroot-start.sh new file mode 100755 index 0000000..626672f --- /dev/null +++ b/config/chroot_local-includes/usr/lib/cryptobox-cd/chroot-start.sh @@ -0,0 +1,56 @@ +#!/bin/sh +# +# Copyright (c) 02005-02006 sense.lab +# +# License: This script is distributed under the terms of version 2 +# of the GNU GPL. See the LICENSE file included with the package. +# +# $Id$ +# +# FOR DEVELOPMENT ONLY! +# +# this script is used to prepare a chroot session for testing or configuring +# +# called by: +# - cbox-build.sh +# +# parameter: [commandline] +# +# if "commandline" is empty, "bash" will be used +# + +set -eu + +MNT_SRC=/opt/dfsruntime/runtimerd +MNT_DST=/opt/dfsruntime/runtimemnt +# the directory /tmp/ can not be used, as it is still a broken link, too +TMP_DIR="/tmp-`basename $0`-$$" + + +cp -a "$MNT_SRC/." "$TMP_DIR" +mount -n --bind "$TMP_DIR" "$MNT_DST" + +[ ! -e /dev/null ] && mknod "/dev/null" c 1 3 && chmod 666 "/dev/null" +[ ! -e /dev/urandom ] && mknod "/dev/urandom" c 1 9 && chmod 444 "/dev/urandom" +[ ! -e /dev/console ] && mknod "/dev/console" c 1 5 && chmod 660 "/dev/console" + +# remember, if proc was mounted before (e.g. because of a running chroot) +PROC_WAS_MOUNTED=no +mount -n -t proc proc /proc 2>/dev/null || PROC_WAS_MOUNTED=yes + +# default language setting - prevents dpkg error messages +export LANG=C + +# set default terminal (good if you are running in a screen session) +export TERM=linux + +# execute parameters as commandline +if [ $# -gt 0 ] + then "$@" + else bash + fi + +umount -l -n "$MNT_DST" +[ "$PROC_WAS_MOUNTED" = "no" ] && umount -l -n proc +rm -r "$TMP_DIR" + diff --git a/config/chroot_local-includes/usr/lib/cryptobox-cd/configure-cryptobox.sh b/config/chroot_local-includes/usr/lib/cryptobox-cd/configure-cryptobox.sh new file mode 100755 index 0000000..a08233f --- /dev/null +++ b/config/chroot_local-includes/usr/lib/cryptobox-cd/configure-cryptobox.sh @@ -0,0 +1,179 @@ +#!/bin/sh +# +# Copyright (c) 02005 sense.lab +# +# License: This script is distributed under the terms of version 2 +# of the GNU GPL. See the LICENSE file included with the package. +# +# $Id$ +# +# this script is part of the building process of the cryptobox +# the "normal" action is necessary for every cryptobox (development & release) +# the "secure" action is mandatory for every release CD +# +# called by: +# - cbox-build.sh after copying custom files and before creating the iso image +# + +set -eu + +RUNTIMEDIR=/opt/dfsruntime/runtimerd +TUNDEV=$RUNTIMEDIR/dev/net/tun +ADD_GROUPS="floppy cdrom tape video plugdev" + +REMOVE_PACKAGES="strace + nvi nano vim vim-common vim-tiny + unzip zip aptitude tasksel locate + ssh elinks curl wget netkit-inetd telnet + exim4-daemon-light exim4-config exim4-base + ppp pppconfig pppoe pppoeconf iptables + subversion w3m wget lynx less screen + info iptables man-db manpages + openssh-server openssh-client" + +# remove rc symlinks for these services +SERVICES_OFF="ssh setserial nviboot mountnfs ntpdate" + +function configure_normal() +# the usual stuff - not optimized for security +{ + ##### cryptobox settings ###### + # start during bootup + sed -i 's/^NO_START=.*$/NO_START=0/' /etc/default/cryptobox-server + # listen to port 80 by default + sed -i 's/^PORT=.*$/PORT=80/' /etc/default/cryptobox-server + # use a separate configuration partition + sed -i 's/^UseConfigPartition.*$/UseConfigPartition = 1/' /etc/cryptobox-server/cryptobox.conf + # all plugins are enabled (especially: "encrypted_webinterface") + sed -i 's#^DisabledPlugins.*$#DisabledPlugins = #' /etc/cryptobox-server/cryptobox.conf + # change the selection of devices, that can be used as the crypto harddisk + sed -i 's#^AllowedDevices.*$#AllowedDevices = /dev/#' /etc/cryptobox-server/cryptobox.conf + # add the cryptobox user to some more groups + for new_group in $ADD_GROUPS + do adduser cryptobox "$new_group" + done + + ############ samba ############ + # enable samba startup (disabled before via cbox-build.sh) + echo 'RUN_MODE="daemons"' >/etc/default/samba + # install the samba hook script + cp /usr/share/doc/cryptobox-server/event-scripts/samba /etc/cryptobox-server/events.d/samba + chmod +x /etc/cryptobox-server/events.d/samba + + + ############ webdav ############ + #TODO: add apache2 packages; configure port; add webdav link in web frontend + sed -i 's/^NO_START=.*$/NO_START=0/' /etc/default/apache2 + cp /usr/share/doc/cryptobox-server/event-scripts/apache2_dav /etc/cryptobox-server/events.d/apache2_dav + chmod +x /etc/cryptobox-server/events.d/apache2_dav + + ########### boot up ########### + # turn off creation of "/etc/nologin" (read-only fs) + sed -i '/^DELAYLOGIN=/s/^DELAYLOGIN=.*$/DELAYLOGIN=no/' /etc/default/rcS + # turn off modifying /etc/motd (read-only fs) + sed -i '/^EDITMOTD=/s/^EDITMOTD=.*$/EDITMOTD=no/' /etc/default/rcS + # default runlevel (out of some strange reason, runlevel 2 is not working) + sed -i 's/^id:.*$/id:3:initdefault:/' /etc/inittab + # add tmpfs entry for mount parent + # remove old line, if fstab exists + test -e /etc/fstab && sed -i '#/var/cache/cryptobox-server/mnt#d' /etc/fstab + # add new line + echo "tmpfs /var/cache/cryptobox-server/mnt tmpfs defaults 0 0" >>/etc/fstab + + ######### devices ########## + # create tun device for running under qemu + if [ ! -e "$TUNDEV" ] + then mkdir -p `dirname "$TUNDEV"` + mknod "$TUNDEV" c 10 200 + fi + + ########## sshd ############ + if [ -e "/etc/ssh" ]; then + # allow empty passwords for ssh + # the daemon is NOT started automatically, so you have to start it + # manually in case of need - as the root pw is empty and passwd is ro, you + # have to allow empty passwords for this rare case + sed -i 's/^PermitEmptyPass.*$/PermitEmptyPasswords yes/' /etc/ssh/sshd_config + # turn off PAM for ssh, as it prevents the use of empty passwords (stange behaviour) + sed -i 's/^UsePAM.*$/UsePAM no/' /etc/ssh/sshd_config + # allow input of password + sed -i 's/^PasswordAuthentication.*$/PasswordAuthentication yes/' /etc/ssh/sshd_config + fi + + # remove symlinks for unwanted services + for a in $SERVICES_OFF; do + # echo "Turning off service $a ..." + find /etc/rc?.d/ -type l -name "[SK][0-9][0-9]$a" | while read b + do rm "$b" + done + done + + return 0 +} + + +function configure_secure() +# remove everything that could weaken security +# configure_normal should be called too! +{ + # disable keyboard login + sed -i '/getty/d' /etc/inittab + + # remove unnecessary packages + dpkg --force-all -P $REMOVE_PACKAGES 2>&1 | grep -v "which isn't installed." || true + + # maybe an authorized_keys file was created - but it is not dangerous, + # as the openssh package was removed anyway + [ -d /root/.ssh ] && rm -rf /root/.ssh + + # disable root account + passwd -l root + + ############## clean up ################ + # remove deb-files, that were left by dfsbuild + # remove packages and package lists + # remove locale files + # remove doc files + # remove man pages + # some vim files stay behind? + rm -rf /opt/packages /var/cache/bootstrap /var/cache/apt/ /var/cache/locate + rm -rf /usr/share/man /usr/share/vim /var/lib/apt /var/cache/debconf /var/cache/man + # remove docs except for the cryptobox's + ls /usr/share/doc | while read dname + do test "$dname" == "cryptobox-server" || rm -rf "/usr/share/doc/$dname" + done + # remove all locale files and symlinks except for the cryptobox's + (find /usr/share/locale -type f; find /usr/share/locale -type l) | grep -v "cryptobox-server" | while read fname + do rm "$fname" + done + # remove all empty locale directories + find /usr/share/locale -type d | while read dname + do test -d "$dname" && rmdir --ignore-fail-on-non-empty --parents "$dname" + done + + # change some dir permissions + chmod 660 /var/cache/cryptobox-server/settings/ + + return 0 +} + + +################ main #################### + + +ACTION=help +[ $# -gt 0 ] && ACTION=$1 + +case "$ACTION" in + normal ) + configure_normal + ;; + secure ) + configure_secure + ;; + * ) + echo "Syntax: `basename $0` { normal | secure }" + echo + ;; + esac + diff --git a/config/chroot_local-includes/usr/lib/cryptobox-cd/devel-features.sh b/config/chroot_local-includes/usr/lib/cryptobox-cd/devel-features.sh new file mode 100755 index 0000000..c3dd82c --- /dev/null +++ b/config/chroot_local-includes/usr/lib/cryptobox-cd/devel-features.sh @@ -0,0 +1,83 @@ +#!/bin/sh +# +# Copyright (c) 02005 sense.lab +# +# License: This script is distributed under the terms of version 2 +# of the GNU GPL. See the LICENSE file included with the package. +# +# $Id$ +# +# this script is part of the boot process of a developer's cryptobox +# +# it should really NEVER be found on a release CD +# +# called by: +# - /etc/rc2.d/S99cb-devel-features +# + +set -eu + +# read the default setting file, if it exists +[ -e /etc/default/cryptobox ] && . /etc/default/cryptobox + +# set CONF_FILE to default value, if not configured in /etc/default/cryptobox +CONF_FILE=${CONF_FILE:-/etc/cryptobox/cryptobox.conf} +# parse config file +. "$CONF_FILE" + +MIRROR_DIR=/tmp/mirror +MIRROR_ORIG_DIR=/tmp/mirror.orig +WRITE_DIRS="/usr/share/cryptobox /var/www /usr/lib/cryptobox" + +ACTION="--help" +[ $# -gt 0 ] && ACTION="$1" + +case "$ACTION" in + start ) + # copy cryptobox files to tmpfs + for a in $WRITE_DIRS + do mkdir -p "$MIRROR_DIR/$a" + cp -a "$a/." "$MIRROR_DIR/$a" + mount --bind "$MIRROR_DIR/$a" "$a" + done + $0 set_diff_base + + # cryptobox-server needs to be restarted to reopen its files + invoke-rc.d cryptobox-server restart + + # start ssh daemon + [ -x /etc/init.d/ssh ] && /etc/init.d/ssh start + ;; + set_diff_base ) + # the present content of the tmpfs mirror get copied to + # MIRROR_ORIG_DIR for later diffs + # whenever you merged a diff, you should call this function + [ -e "$MIRROR_ORIG_DIR" ] && rm -rf "$MIRROR_ORIG_DIR" + cp -a "$MIRROR_DIR" "$MIRROR_ORIG_DIR" + ;; + diff ) + cd "`dirname \"$MIRROR_ORIG_DIR\"`" + # diff and remove "binary files differ"-warnings (vi-swap-files) + # ignore generated reports + # ignore cryptobox.pl and index.html, as those are the same as + # /var/www/cryptobox (symbilic links) + # replace the link name (/var/www/cryptobox) by its destination + # UGLY! + diff -ruN --exclude=report --exclude=cryptobox.pl --exclude=index.html "`basename \"$MIRROR_ORIG_DIR\"`" "`basename \"$MIRROR_DIR\"`" | grep -v "^Binary files" | sed 's#/var/www/cryptobox\t#/var/www/cgi-bin/cryptobox.pl\t#' + ;; + stop ) + [ -x /etc/init.d/ssh ] && /etc/init.d/ssh stop + for a in $WRITE_DIRS + do umount "$MIRROR_DIR/$a" + done + rm -rf "$MIRROR_DIR" + ;; + restart ) + $0 stop + $0 start + ;; + * ) + echo "Syntax: `basename $0` { start | stop | restart }" + ;; + esac +