Alexander Neumann

argh, wrong button, sorry.

Dokan is not the same as FUSE, it's a compatibility layer around libfuse (which we do not use), I've explained it here: https://github.com/restic/restic/issues/361#issuecomment-192162082

Having a second way to access the contents of the repo in a way similar to a file system becomes more important as the source code for osxfuse is [not...

I agree that this could be better. Restic at the moment is rather dumb concerning file sizes: It won't detect advanced things like deduplicating file systems, and also not (yet)...

Thanks for the idea, unfortunately it's not so easy: We support a few authentication methods for S3, see https://github.com/restic/restic/blob/0279fd72123adc52686156332ed7c00a3a07d6e9/internal/backend/s3/s3.go#L43-L64 And the error message already contains what's wrong: ``` Fatal: unable...

Ah, thanks for the explanation.

I agree in general that "no credentials available" should be a different error than "wrong credentials". We need to consider more cases though, "user did not supply credentials" does not...

You're right, the error message isn't great. I'd like to look into how the Upspin project [handles errors](https://commandcenter.blogspot.de/2017/12/error-handling-in-upspin.html), but that will require larger refactorings within restic.

This is connected to #1306

Huh, that's odd! thanks for the report! Can you please paste the output of: ``` restic cat snapshot 45105405 restic cat snapshot 0b34ebf3 restic cat snapshot e898266a ``` I'd like...