I really have no reason to put a password on my file. I would like anyone with access to the files to be able to recover the data, not necessarily just me, hence data theft isnt really of my concern.
When initializing a repository it literally says “Repository password is required”.
Do I have any options at all? I also dont really want to encrypt my files to begin with for that matter 
Would prefer not to.
While Im well here, what file compression algorithm would you guys recommend as of to date?
Saw that pgzip is recommended as a good choice in the docs for both speed & compression rate, is this still the case?
Unprotected repositories were available ~2 years ago or so, but it had some little-tested code paths with problematic properties (no integrity checks), so it was removed.
It may come back at some point, but we need to figure out the integrity story.
Name your repository “Password is 1234” and make the password 1234.
zstd seems to be the best bang for your buck on compression, from what I find.
Try using Kopia’s built in compression benchmarking tool and choose whichever one you like best.
In many of my tests, s2-default comes out as fastest on multicore machines, though with slightly less than optimal compression ratio. You will have to find a representative set of data and run the benchmarks in order to see what fits your usecase best, but given that most machines today that are 10 years old or younger have multiple cores, the parallelizable ones are of course recommended. This will be nicely shown when you do run the compression benchmarks, some of the compressors scale almost linearly with the number of cores in your machine.
pgzip can eat tons of ram, so make sure you check that column too on the benchmarks.
This is really dumb.
The data is going encrypted over SSL, to a cloud store which is itself optionally encrypted. It’s ridiculous that you insist on encrypting it a third time. And then you make the encryption password unrecoverable, so a forgotten password means you lose all your data forever.
How hard can it be to not encrypt something?
Which doesn’t guarantee the use of strong ciphers… & it’s TLS. SSL is insecure, obsolete for that reason.
Key word: optionally. Who’s running the endpoint, specifically?
Encrypted in transit != encrypted at rest.
That sounds like a skill issue.
It’s about as hard as updating your password manager.
Here, this might be far more your speed:
#Learn2E2EE
The key word is not “optionally”. The key word is insist, as in:
Let the user decide whether they want a third type of encryption. With an unrecoverable password (seriously?). I don’t require any encryption except over transport.
You sound like an arrogant condescending troll. And if you think that people should be forced to remember ever more passwords for everything they do (whether they want to or not) then you are sorely out of touch with the mindset of the general population, who practically to a man are saying “enough already”.
Frankly, Kopia is already not for the “general population” as is. Kopia operates in a highly complex environment and I’d expect anyone using it not only to use encryption at rest everywhere possible, but actually demand it.
And not to break out a war over this, but please be aware that Kopia will likely never support that, so no need to dig up this long beaten-to-death horse.
Oh boy; someone has painful comprehension issues. Let’s try it your way: there’s no guarantee the endpoint insists on encrypting the data at rest, son.
Oh, my apologies: you come ITT both so hot & empty headed when you don’t even understand the fundamentals of E2EE & its relation to this software but, of course, I’m the “arrogant asshole.” Silly me.
It must be such a cross to bear when everyone else is at fault while its never you, amirite?
Here you go:
You have a difficult life ahead of you if you don’t get your head out of your ass, boy.
