aawsome
aawsome
@kkettinger Thanks for opening this issue! Which rustic version are you using? From the logs, I see you are using windows, is this correct? Could be a duplicate of #1302...
After the discussion in #3198 I vote against adding this feature in restic but instead support an easy way to use a suitable external tool.
This doesn't help with restic, but I'd like to advertise [rustic](https://github.com/rustic-rs/rustic) which implements this feature. In fact, rustic uses the `ignore` crate to provide the same functionality as ripgrep (which...
Thanks @kapitainsky for opening this issue. This is actually already known and there is https://github.com/rustic-rs/rustic_core/pull/224 on the run.. It just misses some general discussion of us maintainers how to handle...
Thanks @steveh for the bug report! This is something we are working on (but may need a bit of time..)
The parameters in the key you use are invalid in https://datatracker.ietf.org/doc/html/rfc7914#section-2. However, as discussed in https://github.com/golang/go/issues/33703 they seem to be still valid and the RFC is too strict only by...
I reported to the Rust scrypt library, maybe they'll relax this check, then old keys will also work with rustic.
Hi @gyscos! Thanks for opening this issue! I just implemented this feature, see #1474.
I just realized there is a second feature request which is still open...
The failing test is due to missing tests...