Regarding the "Alternate Patching Method" using normal apt update: Its
possible the template was attacked via updates even before the bug was
announced, or sometime between the Debian announcement and now. The
"check InRelease" only helps if the attack occurs only during the next
update and not before. Otherwise, the user has no way of knowing if
their template has been compromised before doing this special update
procedure.
Replacing the template as described in "Patching" section provides much
more certainty.
Chris
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/a3df6d0a-e193-1c59-a553-e0367e936567%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
