I'm guessing that this is never going to get implemented. If anyone knows a good alternative that is portable, please message me.
The android client would make CryptSync perfect. I use it now on all my Windows-devices, and adding my phone would just finalize the awesomeness!
Installing 1.3.1 seems to have resolved the problem :-)
Found further info in the Application Log: Faulting application name: CryptSync.exe, version: 1.3.0.337, time stamp: 0x5af2dcbd Faulting module name: CryptSync.exe, version: 1.3.0.337, time stamp: 0x5af2dcbd Exception code: 0xc0000005 Fault offset: 0x000000000014f134 Faulting process ID: 0x646c Faulting application start time: 0x01d450c18f44ea70 Faulting application path: C:\Program Files\CryptSync\CryptSync.exe Faulting module path: C:\Program Files\CryptSync\CryptSync.exe Report ID: 6271adb6-fa83-4e49-bd65-aaa68b4c0563...
Cryptsync is exiting after a few seconds of running in the background
update version check file
Small feature requests
long path names
Updates
Just after midnight, so update the year check.
Originally posted by: n...@bitnology.com I also have recurring syncs but happening with encrypted filenames. In the case of encrypted filenames, cryptsync should be able to look at the filename and realize when it is a conflicted copy because the filename is the encrypted filename plus e.g. "Wally's conflicted copy". In this case the extra text could be simply appended to the decrypted filename? Maybe the option could be called "Preserve conflicted copy"? It would be great if Cryptsync could one-up...
I am a developer (retired) and have given this problem some thought. In case anyone is interested in writing some code, here is a possible solution. This addresses the use case where there is ONE encrypted repository and one or more unencrypted synced copies, which would seem to be the primary use case for "multiple computers": What we need to do is maintain a "system" file in the encrypted area, or rather, one such file in each directory which has had children (files or subdirectories) deleted -...
I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...
I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...
I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...
I aggree with Folding Home Portable app is needed. Creating encrypted files from Admin restricted public device should not be that hard. Installation of program may be an option
I'm considering using an external text file to specify default compression level and extensions that should not be compressed globally. But I have no plan to add such settings per sync pair. That is more involved than what I'm comfortable doing right now.
Thanks for the effort and sharing the version, it's well appreciated! Any plans on implementing a manual option to include certain filetypes (per sync pair)? I'm especially looking at raw image files. These can be either compressed or uncompressed, so a hardcoded option would not work so well for them. Fast compression by default in your new version may already help there, though, I will have to test that.
I've modified the source code to turnoff compression for some already compressed file formats. But it's hard-coded, you cannot choose from UI what to compress and what not to. This "personal version" of mine is now published on GitHub. Installers can be downloaded on the releases page. Note that it also comes with some other personal tweaks that might not be what you want.
I've modified the source code to turnoff compression for some already compressed file formats. This "personal version" of mine is now published on GitHub. Installers can be downloaded on the releases page. It addresses this issue, but also comes with some other personal tweaks that might not be what you want.
I've published my "personal version" on GitHub. Installers can be downloaded on the releases page. It fixes this issue. But also comes with some other personal tweaks that might not be what you want.
Very nasty when syncing two computers.. Will it be fixed soon in the installer versions? Mathias
Thanks for answers! Added a program to my site (it's in Russian), here's the link.
update to vs2017
Sourcecode is right here on the project page where you created this issue. Just two buttons on the right. https://sourceforge.net/p/cryptsync-sk/code/HEAD/tree/ License is GPL, indicated in every source file. translations are not implemented (yet).
license
Turns out this issue is not specific to command line, but all decrypt operations in full scans. File sync on individually detected file changes don't have this issue. I fixed it by changing line 701 in FolderSync.cpp from if (!DecryptFile(origpath, cryptpath, pt.password, it->second, pt.useGPG)) to if (!DecryptFile(origpath, cryptpath, pt.password, cryptit->second, pt.useGPG))
Turns out this issue is not specific to command line, but all decrypt operations when syncing entire folders. File sync on individually detected file changes don't have this issue. I fixed it by changing line 701 in FolderSync.cpp from if (!DecryptFile(origpath, cryptpath, pt.password, it->second, pt.useGPG)) to if (!DecryptFile(origpath, cryptpath, pt.password, cryptit->second, pt.useGPG))
Turns out this issue is not specific to command line, but all decrypt operations when syncing entire folders. File sync on individually detected file changes don't have this issue. I fixed it by changing line 701 in FolderSync.cpp from if (!DecryptFile(origpath, cryptpath, pt.password, **it**->second, pt.useGPG)) to if (!DecryptFile(origpath, cryptpath, pt.password, **cryptit**->second, pt.useGPG))
That's okay Yes, -mx0 works as "copy without compression" when -m0=lzma2 is not present. But when -m0=lzma2 is present, -mx0 effectively becomes -mx1 "-mx0 -m0=lzma2" and "-mx1" produces the exact same output (without -p"password). All I said above is backed up with tests I did, not just from reading documentation
files larger than 100MB still compressed (verified by many tests)
files larger than 100MB still compressed due to 7z -m0=lzma2 flag
Ups, sorry. My fault. I mixed lzma2 with sha2. But still: according to the official docs (which you can find in c:\program files\z-zip\7-zip.chm when you install 7-zip), when passing -m, the '0' means Copy mode (no compression).
files larger than 100MB still compressed (verified by many tests)
With -m0=lzma2 and -mx0, files get compressed with effect of -mx1 Without -p"password", "-mx0 -m0=lzma2" and "-mx1" produces the exact same output. Without -m0=lzma2, -mx0 functions properly without compression. Encryption still works with -p"password" These are verifiable with tests, as I have done. There's no option for encryption algorithm when using -t7z, because 7z format only supports AES
screenshot from 7zip GUI
http://www.7-zip.org/7z.html https://en.wikipedia.org/wiki/7z#Encryption
Surely lzma2 refers to the compression algorithm. It's on by default according to 7z documentation. Also consistent with the many tests I did 7z format only uses AES for encryption, no other choices references: https://sevenzip.osdn.jp/chm/cmdline/switches/method.htm#MethodID https://sevenzip.osdn.jp/chm/cmdline/switches/method.htm#LZMA2 https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Markov_chain_algorithm
lzma2 is not on by default, because that's the encryption algorithm to be used. lzma2 has nothing to do with compression but only with encryption.
files larger than 100MB still compressed due to 7z -m0=lzma2 flag
files larger than 100MB still compressed due to 7z -m0=lzma2 flag
CryptSync is shipped with GnuPG v1.4.9, which uses Cast5 by default (CryptSync doesn't change that). https://security.stackexchange.com/questions/86305/what-is-the-default-cipher-algorithm-for-gnupg The most straightforward way would be to change CryptSync's source code yourself and compile a personal version. (Build instructions are very clear, I tried it before) The relevant source code is in "FolderSync.cpp", line 941 and line 1009
CryptSync is shipped with GnuPG v1.4.9, which uses Cast5 by default (CryptSync doesn't change that). The most straightforward way would be to change CryptSync's source code yourself and compile a personal version. (Build instructions are very clear, I tried it before) The relevant source code is in "FolderSync.cpp", line 941 and line 1009
I wouldn't keep my hope up. CryptSync is written with native Windows code, not on some platform independent library. Porting to other OS would be a lot of work. It's open source free software afterall, incentives not that strong. But if someone donate some big bucks... then we have hope.
Turning off compression wouldn't help. What most responsible for changing your whole file isn't compression, it's encryption. With compression but without encryption, all the data blocks following the changed block would be changed, but blocks that come before stay the same. With encryption, with or without compression, every block in your file would be changed, even if the original file stay exactly the same. Because 7zip uses AES with CBC mode, which uses an initialization vector (IV) that should...
Originally posted by: operati...@gmail.com 7-Zip File Manager created these zombie-long-name files, and 7-Zip File Manager can kill them too. Navigate to the offending path and rename it from within the program. (However, even 7-Zip can't DELETE the files directly.) It also does not work if you have numerous offenders.
You can check the code log at https://sourceforge.net/p/cryptsync-sk/code/log/ Stefan writes a description for every change.
You can check the code log at https://sourceforge.net/p/cryptsync-sk/code/log/ Stefan writes a description for every changes.
command line "/mirrorback" mode does not update "date modified" of source files
Complementing Sync Direction used: "unencrypted to encrypted only" How to recreate:...
Deleted folder on origin not delete folder on destination
Versioning of files
"Stefan's" -> "Stefans"
uploading only changed file parts by turning off 7zip compression
File splitting
Adjust for 2017
Exclude incompressible files (photos, mp3)
This would be a very nice thing to have - either as something built in to the app...
MISSING CHANGELOG
version 1.2.7 is online. now works from the command line as well.
update the version check file
use 'delete' to prevent using default construct...
Fix: meant to assign the value, not compare it.
Searching for chars is faster than searching fo...
constify parameter.
pass std::string directly.
bump version to 1.2.7
When /mirrorback is specified on the command li...
The "on demand" feature is not fully reliable. It can miss some changes if there...
How does interval work?
Hi Stefan! Thanks for adding the option to mirror deletions from encrypted to unencrypted...
Just wanted to bump the portable thread again by noting a few use cases for portable...
any possibility for a future Linux or OSX verion?
have the build script update the version check ...
update the version check file
update 7zip to 16.04
tag the 1.2.6 release
ignore folder with test data
bump version to 1.2.6
Hi Stefan. Would you mind to add an option to let the user decide whether or not...
Hi Stefan. Would you mind to create an option to let the user decide whether or not...
Thx, for the fast reply. You're absolutely right! I thought I simulate one shared...
Rename Problem
That's expected: when you rename an encrypted file, the original filename is still...
Here is the Log
Rename Problem
Thanks for the help. 1) How can I have it NOT ignore files? I don't want to copy...
When syncing dest to source, also delete files ...
Thanks Stefan for the prompt updates, looking forward to giving 1.2.6 a try when...
Thanks Stefan for the prompt updates, looking forward to giving 1.2.5 a try when...
Add info to the help dialog about the %ERRORLEV...
[r323]
Request: Return value / messages for command line usage
* use different return values for different fai...
Only files in Root-Dir are encrypted
Request: Improvement of logging behaviour