Status: Fixed
A minor change caused SSL to be disabled for FTP, TahoeLAFS and WEBDAV unless the option was set to "--use-ssl=true".
git-svn-id: https://duplicati.googlecode.com/svn/trunk@726 59da171f-624f-0410-aa54-27559c288bec
Now also stores the filename+size of signature/content files to ensure that the parsed filenames match the expected ones.
The filesize and filenames are used to verify that the remote file is complete, without downloading it.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@716 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I have now added a module called http-options which can be used to
configure http options, notably the 100-Expect.
I am unsure if it will break existing installations if I disable
it by default, so it is still enabled but can be disabled by the
switch --disable-expect100-continue.
You can set this option in the GUI under "Advanced options".
git-svn-id: https://duplicati.googlecode.com/svn/trunk@713 59da171f-624f-0410-aa54-27559c288bec
This commit includes an option to create an unencrypted verification file.
There is now a check to see if all volumes mentioned in the manifest exists,
before performing backup/restore operations.
This check is also performed on cleanup.
There is now a check that prevents auto-cleanup from removing more than
2 orphan files.
If a delete-older-than or delete-all-but-n-full is interrupted, the leftover
files will not be auto-deleted but must be deleted with the cleanup command,
which allows the user to see what files are delete.
Update issue #360
Status: Fixed
There is now a complete verification chain, where the manifest hashes are verified backwards.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@711 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I found and fixed the issue, I was using an int instead of a long for the filesize,
which caused it to truncate.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@683 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
That is an incorrect warning, the priority is applied despite the warning.
I have fixed the code so the warning does not appear anymore.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@675 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I have now removed the code required to activate the deprecated AES crypt encryption, but kept the code required to decode it,
git-svn-id: https://duplicati.googlecode.com/svn/trunk@670 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
It was supposed to write an error message like:
When listing the folder <foldername> the file <filename> was listed, but the server now reports that the file is not found.
This can be because the file is deleted or unavailable, but it can also be because the file extension .aes is blocked by the web server. IIS blocks unknown extensions by default.
Error message: 404 - File not found
Unfortunately the error message was incorrectly formated so you got a highly misleading message instead.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@658 59da171f-624f-0410-aa54-27559c288bec
Changed the non-streaming file-backend interface to use sytem copy calls rather than
manual stream copy.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@654 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
There were some issues with namespaces and signing of the files,
which caused the translations to not load.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@649 59da171f-624f-0410-aa54-27559c288bec
Update issue #323
Status: Fixed
I see the problem, in SSHUI.cs line 107, the keyfile option is always set, even if it is empty.
I have added checks to detect the empty string in the UI and the backend itself.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@639 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
There is now a Tahoe-LAFS backend option.
It is quite new, so obviously it is fairly untested in real life.
It passes all unittests, and is largely based on the WEBDAV backend which as seen some action.
I will put up a preview build with Tahoe-LAFS support soon.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@623 59da171f-624f-0410-aa54-27559c288bec
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
Status: Fixed
I found the error in the USN handling code.
The problem was that the filename was compared case insensitive, when doing USN file listing.
This caused all my tests to pass (as the folders have the correct case).
I managed to type it with the incorrect case in a test setup and found the error.
I will put up a new preview soon with the fix.
I would recommend that you use that version instead and delete the usn-policy setting from the backup.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@605 59da171f-624f-0410-aa54-27559c288bec
