Manu
Manu
Thanks for checking. Can you provide a minimal failing example using Borg CLI? Then we can open an issue with Borg itself upstream.
I meant the steps to reproduce and verify the issue. Not just the extract command. E.g. I'm not fully sure where the xattr comes from. I just know files downloaded...
Just tried this with Borg by itself and I was unable to reproduce the issue: ``` 10771 touch test.txt 10772 xattr -w com.apple.ResourceFork mytestrf test.txt 10774 borg create test-repo::xattr test.txt...
You're right. Happens here too. Next thing I need to point out though is that this is more related to Borg than Vorta. So should be reported there. If it...
I'm fine with removing this line. Didn't notice any issues for normal use cases. Showing a warning mit more details and giving the option to continue would be the best...
PR added to just remove this for now until we can show a full message with the host key failure details.
Will try. Thing is that SSH runs within Borg, so we need to pull up those messages into Vorta first. Let’s see.
Actually I had `StrictHostKeyChecking` turned off in my SSH configs too. That's why everything kept working. With this option removed there will be a prompt by Borg and adding the...
I think we should keep `StrictHostKeyChecking=no` for the `borg init` and `borg info` operations, which are used to add a new repo, but remove them from everything else. That way...
Since adding a new hostkey is not really what we want to avoid. What we really want to avoid is continuing after this. When a known key changed: ![Screen Shot...