Commit Graph
7 Commits
Author SHA1 Message Date
rstach@gmail.com 3bf5a74a76 Set max port to 65535
git-svn-id: https://duplicati.googlecode.com/svn/branches/1.3.1@1131 59da171f-624f-0410-aa54-27559c288bec
2012-02-12 10:27:45 +00:00
hugh@hugheaves.com bc00bf1fbe Backed out changes accidentally commited to trunk
git-svn-id: https://duplicati.googlecode.com/svn/trunk@759 59da171f-624f-0410-aa54-27559c288bec
2011-04-27 20:42:14 +00:00
hugh@hugheaves.com 2f8f0be0f1 git-svn-id: https://duplicati.googlecode.com/svn/trunk@758 59da171f-624f-0410-aa54-27559c288bec 2011-04-27 20:24:44 +00:00
kenneth.skovhede@gmail.com 1057424b0d Update issue #153
I have now added preliminary support for keyfiles under SSH.
For the time being it only supports OpenSSH private key files, and only unencrypted or tripple-DES encrypted ones.
This is a limitation of the SharpSSH library, which is based on an old JSCH implementation with this limitation.

git-svn-id: https://duplicati.googlecode.com/svn/trunk@622 59da171f-624f-0410-aa54-27559c288bec
2010-12-07 21:13:51 +00:00
kenneth.skovhede@gmail.com effdba0558 Update issue #134
Status: Fixed

I have now implemented a password protection control.
You can now only view passwords when you enter them.
After this, you may reset the passwords, by entering a
new one, but you cannot read the existing passwords.

To protect against people reading the database,
which contains the passwords in clear text, the
database is now encrypted by using the standard 
SQLite encryption method. This is different
than what I proposed, but is a much stronger
protection than merely scrambling the passwords,
and also protects all information (servername, etc).

It works by setting an environment variable
called DUPLICATI_DB_KEY. When no password
is set, Duplicati will use the key "Duplicati_Key_42",
ensuring that all databases are encrypted by default.

Using a pre-defined publicly known key is obviously
not a strong protection, but it protects from casual
users attempting to browse the database, and it also
protects from string scanners that scan a harddisk
for possible passwords.

On the first startup, Duplicati will encrypt the database,
using the mentioned key. You may want to delete any backup
databases that are placed in the same folder as the database.

Should you wish to decrypt the database, you can start 
Duplicati.exe with the commandline option "--unencrypted-database".
This will use the current key to decrypt the database, and save it
without encryption.

Should you wish to change the database password, simply decrypt the
database, then change the password via the environment variable,
and start Duplicati.exe as normal.

The SQLite documentation for the feature is here:
http://www.hwaci.com/sw/sqlite/see.html

Unfortunately, it does not seem as if any
of the free SQLite tools supports this.

The SQLite library found on Ubuntu
does not support encryption, so I have disabled 
this feature by default on Linux.

If a user has a special compiled version
of SQLite, they may use the environment
variables as mentioned above.

I will write this information into a wiki
page as soon asap.

git-svn-id: https://duplicati.googlecode.com/svn/trunk@498 59da171f-624f-0410-aa54-27559c288bec
2010-09-07 21:39:22 +00:00
kenneth.skovhede@gmail.com 1f87e01fc7 Fixed issue #129.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@337 59da171f-624f-0410-aa54-27559c288bec
2010-01-17 20:21:08 +00:00
kenneth.skovhede@gmail.com 293311b68f All backends are now ported, needs a lot of testing before it can go into trunk
git-svn-id: https://duplicati.googlecode.com/svn/branches/Issue77@286 59da171f-624f-0410-aa54-27559c288bec
2009-09-20 20:58:49 +00:00