Closed asmeurer closed 1 year ago
Yeah, it's because that path is within the sandbox secretive has access to.
Nothing that would prevent you from symlinking it though, if you were so inclined.
If Secretive can write to ~/.ssh/config during the setup shouldn't it also be able to write a symlink there?
This is actually a little bit of sleight of hand on Secretive's part - we're given write access to that specific file if you explicitly select it from the file dialog - but we can't access ~/.ssh in general
It's a little confusing that the public key is buried in ~/Library somewhere. Is there a reason it isn't included in ~/.ssh/, at least as a symlink?