Scott Leggett
Scott Leggett
I think generating keys on the card is the correct approach. Then you just need to encrypt everything with _two_ subkeys - an emergency disaster-recovery key stored on disk with...
One downside is that it directly conflicts with other use cases like https://github.com/restic/restic/issues/2564, where the user _wants_ the symlink name in the snapshot. Your `readlink` solution seems reasonable.
printing file stats at all doesn't really make sense when using `--stdin`. maybe restic shouldn't print file stats at all in that case? So instead of: ``` repository af7ba211 opened...
Does this do what you're after? ``` find /path/to/urbackup/client/symlink_to_current/ -maxdepth 1 -print0 | xargs -0 restic backup ```
> it dereferences/follows the symlink `find` shouldn't do that with the trailing `/`.. could you try the command?
You can use `restic snapshots -c` to get a single line per snapshot.
On the notification side, could specific Slack integration just be deprecated in favour of webhooks (which slack supports)?
Could this use-case be solved by the setting touch policy to "cache for 15 seconds"?
Since #54 was closed without merging it made `yubikey-agent` unusable for me. I now use https://github.com/smlx/piv-agent instead, you might be interested in trying that.
Wouldn't #44 essentially solve this? `launchd` also supports socket activation. Here's the `launchd` config and associated socket activation code I use in `piv-agent`. It's only lightly tested on macOS since...