lars
0c129de015
changed the log level of some messages added early "not writeable" warnings to "volume_format_fs" and "partition" plugins disable "encrypted_webinterface" by default (for cryptobox-server) |
||
---|---|---|
.. | ||
patches | ||
changelog | ||
compat | ||
control | ||
copyright | ||
cryptobox-server.default | ||
cryptobox-server.dirs | ||
cryptobox-server.docs | ||
cryptobox-server.examples | ||
cryptobox-server.init | ||
cryptobox-server.lintian | ||
cryptobox-server.logrotate | ||
cryptobox-server.manpages | ||
cryptobox-server.postinst | ||
cryptobox-server.postrm | ||
cryptobox-server.preinst | ||
cryptobox-server.prerm | ||
pycompat | ||
README.Debian | ||
rules |
CryptoBox for Debian - installation notes The main configuration file of the CryptoBox webserver is: /etc/cryptobox-server/cryptobox.conf All settings named [Foo]->Bar are defined in this file. 1) Configure startup and network settings in /etc/default/cryptobox-server. 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: the data on these drives can be overwritten by front-end users! 3) Choose a list of plugins to disable in [Main]->DisabledPlugins. 4) Use the username 'admin' and the password 'admin' to access protected parts of the CryptoBox. Please change the password soon in the 'user_manager'. You can use the 'plugin_manager' to define which parts of the CryptoBox should be restricted to administrative access. 5) Read /usr/share/doc/cryptobox-server/event-scripts/README for information about event handlers. They can be used to integrate fileservers (samba, apache2-dav, nfs, ...) into the CryptoBox. Detailed information about integration with samba and apach2-dav can be found in README.samba and README.davfs. 6) A line was automatically added to /etc/super.tab. This is necessary to gain root privileges for certain actions. Please inspect /usr/sbin/CryptoBoxRootActions carefully to make sure, that your system can not get compromised by this.