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
Status: Fixed
It turns out that it was an invalid error message.
Actually it should request that the user enter a destination folder.
I also changed the summary page to not show the inserted temporary folders.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@657 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
Turns out it was a more generic problem than I first assumed.
The problem was that there are two similar controls on the page (the duration editors),
and their internal controls are named the same, so it applied the setting from the top control to the lower,
and the top control was set to "each day".
The other problem "system is slow" is also fixed, although I'm unsure why it happened in the first place.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@630 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
Hmm.. If I do that, I get an english language page.
I have removed the "lc=DK" from the URL, which seems to be the language indicator.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@612 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
