Closed rasa closed 2 years ago
This seems like it would add a lot of complication. What would happen if there are multiple archives in the repository?
This seems like it would add a lot of complication. What would happen if there are multiple archives in the repository?
Good point. Yadm would need to be smart enough to remove an old archive when a new archive is created. It might be too complicated, but if there's interest, I could explore creating a draft PR for discussion.
Another solution could be to add yadm save-config
and yadm restore-config
commands. Something akin to:
yadm config -l >~/.config/yadm/settings.conf
yadm add ~/.config/yadm/settings.conf
and
IFS=$'\n' read -d '' -r -a lines <~/.config/yadm/settings.conf
for line in "${lines[@]}"; do
yadm config "${line%=*}" "${line##*=}"
done
Edit: and maybe a yadm show-config
as well:
cat ~/.config/yadm/settings.conf
or
read -d '' -r settings <~/.config/yadm/settings.conf
printf '%s\n' "${settings}"
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Is your feature request related to a problem?
yadm has to be configured the same on every decrypting system to match the settings on the encrypting system.
Describe the solution you'd like
Yadm uses the suffix of the archive to automatically decrypt the archive. Here are some examples:
(or aes256)
(or aes256_old)
(or aes192)
(or aes192_old)
We could also solve this by creating a file with the config settings, called say
~/.local/share/yadm/archive.conf
, but parsing it could prove problematic, so using the file extension seems cleaner. But this would allow full backward compatibility.