Alexander Neumann

Hm, then restic should be able to detect the symlinks then. Strange. What's the difference between a "junction" and "symlink"? restic uses the following code to decide if something [is...

I'm closing this issue, we cannot do anything here but guess.

Ah, I actually like the idea. We even have an abstraction layer now (`fs.FS`) which could be used to implement a `tar` file system maybe.

Just a comment from the sidelines: if the symlink target field is just an arbitrary sequence of bytes (not necessarily UTF-8, it'll be whatever the OS and/or the filesystem is...

I don't think it's a major problem, but we should not print the stats for files/dirs when reading from stdin.

Interesting, thanks for the hint! It also feels to me that the `stats` command does much more work than necessary in this case, that could be improved.

Uh, that's indeed a corner case we don't handle yet, I classify this as a bug. On backup, we needed a way to make saving `d:\` and `e:\` possible without...

> Am I right? Not quite: You can do that with restic, even with this limitation. You only need to make sure that the backup is made by changing the...

As far as I understand the docs you linked all bits (not only the lowest 9 bits) are part of the public API of the Go standard library, so I...

That's hardly possible just by using asymmetric crypto. The point here is that old backup contents (not necessarily metadata) should not be available to an attacker who has broken into...