syncrypt clone error about client

[lordi]

Thanks for the report. This happens because you haven't uploaded the encrypted vaultkey for yourself. We need to implement it yet.

You can try to do:

syncrypt keys --upload

on the second machine, and

syncrypt add-user your@email

and on the first machine.

[jotech]

okay this makes sense, thanks!

But syncrypt keys --upload failed on the second machine with error syncrypt.exceptions.VaultNotInitialized
Nonetheless on the first machine, I could see the fingerprint of the second via syncrypt add-user mail and I could grant access.
Afterwards syncrypt clone worked on the second machine, perfect!

I am right to assume that the fingerprint of a new machine is attached to the account after using syncrypt login the first time and that I have to provide access to the new machine again with add-user?

[lordi]

Yes, you're right. syncrypt login already uploads the public key (with fingerprint), so syncrypt keys --upload is not needed.

Good to know that add-user on oneself works. But it is only a matter of key transmission. You as a user already have access to your own vault, but its simply the fact that the vaultkey was missing.

I think in addition to add-user we should provide a second command that will simply upload the vaultkey for another machine of yours. Like add-machine or so.

[jotech]

I agree something like add-machine would be more obvious.
Thanks for the support.