gilbertchen

I agree this is a security flaw. Duplicacy should call the KeyChain API directly instead of relying on 'security' to access the passwords. On Windows it is even less secure...

It should be done by the end of next week at the latest.

Duplicacy uses my fork of github.com/tmc/keyring to access KeyChain on macOS. There is another form that has already implemented direct KeyChain access: https://github.com/SpiderOak/keyring/blob/master/keyring_darwin_arm64.go However, XCode is required to compile that...

I just checked in https://github.com/gilbertchen/keyring/commit/8855f5632086e51468cd7ce91056f8da69687ef6. Now if you want to build Duplicacy from source on macOS it will use the direct keychain access by default. However, you need to have...

This issue has been mentioned on **Duplicacy Forum**. There might be relevant details there: https://forum.duplicacy.com/t/build-duplicacy-from-source/1091/1

Duplicacy uses the [two-step fossil collection](https://github.com/gilbertchen/duplicacy/blob/master/DESIGN.md#two-step-fossil-collection) algorithm. In the first step it only renames unreferenced chunks into fossils and doesn't reclaim any space. Only in the second step when it...

My claim that the B2 version setting doesn't matter is wrong. The `Keep all versions of the file` setting is recommended. See #362 for details.

This issue has been mentioned on **Duplicacy Forum**. There might be relevant details there: https://forum.duplicacy.com/t/backblaze-b2-bucket-size-does-not-match-storage-size/6836/3

This issue has been mentioned on **Duplicacy Forum**. There might be relevant details there: https://forum.duplicacy.com/t/backblaze-b2-bucket-size-does-not-match-storage-size/6836/5

Thanks for pointing out that. I've corrected the link.