Qubes 3.2 after patching

[rob_66]

Hello.

So, I received Xen packages, version 4.6.6-36, via dom0 --enablerepo=qubes-dom0-security-testing.

I changed 1) the (xscreensaver) password and 2) LUKS passphrase.

Now the questions:

Can I start with 3) disk reencrypting (reinstalling Qubes 3.2., restoring from
backup) and 4) generating new secrets (PGP, passwords …) now – or do I have to wait until Xen
4.6.6-36 has landed in the stable repository?

Or do I start 1)–4) of Qubes' »Suggested actions after patching« anew after Xen
4.6.6-36 has landed in stable repository?

And how do I know when 4.6.6-36 has landed there? (I'm always updating Qubes via dom0 with
--enablerepo=qubes-dom0-security-testing enabled and never faced problems with that.)

Please excuse my confusion.

Thanks, r.

[awokd]

On Tue, January 30, 2018 4:54 pm, rob_66 wrote:
> Hello.
>
>
> So, I received Xen packages, version 4.6.6-36, via dom0
> --enablerepo=qubes-dom0-security-testing.
>
>
> I changed 1) the (xscreensaver) password and 2) LUKS passphrase.
>
>
> Now the questions:
>
>
> Can I start with 3) disk reencrypting (reinstalling Qubes 3.2., restoring
> from backup) and 4) generating new secrets (PGP, passwords …) now – or do
> I have to wait until Xen
> 4.6.6-36 has landed in the stable repository?

I think you could start this now.

> Or do I start 1)–4) of Qubes' »Suggested actions after patching« anew
> after Xen 4.6.6-36 has landed in stable repository?
>
>
> And how do I know when 4.6.6-36 has landed there? (I'm always updating
> Qubes via dom0 with
> --enablerepo=qubes-dom0-security-testing enabled and never faced problems
> with that.)

To the best of my knowledge, if you've already installed a package from
the testing repository, it won't get re-installed again once it moves to
stable.