last preparations for v0.3 release

README

@@ -76,7 +76,7 @@ not get compromised.
  a) Start at bootup
 	Set NO_START in /etc/default/cryptobox-server to "0".
 	The CryptoBox webserver will get started by its runlevel control script
-	after during booting.
+	after bootup.
 
  b) Define managed devices
 	You may restrict which blockdevices should be accessible to the CryptoBox.

README.ssl

@@ -28,13 +28,13 @@ There are two ways for setting up a SSL connection:
 
 
 2) CryptoBox behind stunnel
-	You may want to tunnenl the traffic between the cryptobox-server
+	You may want to tunnel the traffic between the cryptobox-server
 	and your browser. "stunnel" is an excellent candidate for this job.
 
 	If you do not have an ssl certificate yet, then you should create
 	one first. On Debian: "apt-get install ssl-cert" and run the following
-	command (replace the <NAMES>; a default CERT_CONF is shipped with the cryptobox-server
+	command (replace the <NAMES>; a default CERT_CONF is shipped with the
-	package):
+	cryptobox-server package):
 
 		make-ssl-cert <CERT_CONF> <CERT_FILE_NAME>
 

changelog

@@ -1,5 +1,5 @@
 Version 0.3 - 02/15/02007
- * completely new interface
+ * new interface
  * manage multiple disks
  * support custom partitioning
  * support plaintext partitions
@@ -7,11 +7,7 @@ Version 0.3 - 02/15/02007
  * allow to set time and date
  * change of encryption passphrase without data losses
  * support for pluggable features
- * new kernel: 2.6.18
+ * seperated cryptobox-server package
- * bugfix: add /dev/hdd to device scan
- * support for usb, scsi and firewire cdrom drive
- * seperated cryptobox-server package available
- * french translation added (thanks to 'rike')
 
 Version 0.2.1 - 10/22/02005
  * fixed a critical bug in the initialisation process

conf-examples/cryptobox.conf

@@ -12,8 +12,8 @@ UseConfigPartition = 0
 DefaultVolumePrefix = "Disk "
 
 # which cipher should cryptsetup-luks use?
-#TODO: uml does not support this module - DefaultCipher = aes-cbc-essiv:sha256
+# if you lack the appropriate kernel modules, then you could try "aes-plain" - but it is less secure
-DefaultCipher = aes-plain
+DefaultCipher = aes-cbc-essiv:sha256
 
 # label of the configuration partition (you should never change this)
 ConfigVolumeLabel = cbox_config

debian/README.Debian

@@ -9,8 +9,8 @@ Set 'NO_START' to "0" if the CryptoBox should start at every bootup.
 Set the port on which the cryptobox-server should listen.
 
 2) Define [Main]->AllowedDevices according to the devices that you want to
-publish via the cryptobox webinterface. Be careful this drives may be
+publish via the cryptobox webinterface. Be careful: the data on these drives
-overwritten by front-end users!
+can be overwritten by front-end users!
 
 3) Choose a list of plugins to disable in [Main]->DisabledPlugins.
 

debian/changelog

@@ -1,3 +1,15 @@
+cryptobox (0.3.0-1) unstable; urgency=low
+
+  * first release of the CryptoBox as a seperate package
+
+ -- Lars Kruse <devel@sumpfralle.de>  Fri, 15 Dec 2006 14:37:07 +0100
+
+cryptobox (0.2.59-1) unstable; urgency=low
+
+  * remove leading white lines to improve standard complicance of html
+
+ -- Lars Kruse <devel@sumpfralle.de>  Thu, 14 Dec 2006 14:19:12 +0100
+
 cryptobox (0.2.58-1) unstable; urgency=low
 
   * fixed small layout bug

src/cryptobox/__init__.py

@@ -10,5 +10,5 @@ __all__ = ['core', 'web', 'plugins', 'tests']
 __revision__ = "$Id$"
 
 
-__version__ = "0.2.58"
+__version__ = "0.3.0"
 

templates/language.hdf

@@ -12,7 +12,7 @@ Text {
 	EnterSamePassword	= Repeat new password
 	RedirectNote		= Click here if your browser does not support automatic redirection.
 	ProjectHomePage		= Website of project
-	ProjectNote		= The CryptoBox is a project by
+	ProjectNote		= The CryptoBox is a project of
 	ContainerName	= Volume's name
 
 }