Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide instructions for how to use this for “production” (practical) use #50

Open
DemiMarie opened this issue Feb 4, 2018 · 1 comment

Comments

@DemiMarie
Copy link

I would like to use this to backup my personal laptop. How can I do that?

@v6ak
Copy link
Owner

v6ak commented Apr 17, 2018

Sorry for the delay. The project has a bit hibernated. I want to make it live again, because I need to adapt it to R4 changes.

Well, currently, I expect you that you move the content of the repo directly to dom0 and then use it from dom0. It does not assume much about AppVMs, except that both proxy and DVM has duplicity installed. (Hmm, and there is some undocumented reliance on its version…)

I understand this might be not enough friendly. I am not sure how to make it both friendly and Qubes way. Do you have some idea?

  • Maybe I should write something about signature checking.
  • Maybe there should be some deterministic (reproducible) procedure that creates some (tar?) archive that has to be unpacked in dom0. Maybe I should also publish such archives together with signatures.
  • Finally, backups should contain some notes about pubkeys and/or commit id, authenticated by backup password. Verification procedure should be also documented.

What do you think about those ideas? Would it make it more friendly and secure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants