I have followed the Installation guide from website Whonix/wiki/SecBrowser/Qubes and failed to install secbrowser in a qubes templatevm. However, I’ve successfully installed it in an AppVM - but that’s of little use as the Appvm is non-persistent.
Steps 1 to 8. All successful
Step 9 i.e. sudo apt update produces errors:(edited to remove disallowed links)
“user@debian-10-clone:~$ sudo apt-get update
Get:3 … buster InRelease [37.5 kB]
Get:4 … buster InRelease [2,500 B]
Hit:1 …/debian buster InRelease
Err:3 deb… buster InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY CB8D50BB77BB3C48
Hit:2 …org/debian-security buster/updates InRelease
Reading package lists… Done
W: GPG error…org buster InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY CB8D50BB77BB3C48
E: The repository … buster InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.”
It would appear that the unavailable key CB8D50BB77BB3C48, is a subkey of the primary key 916B8D99C38EAF5E8ADC7A2A8D66066A2EEACCDA downloaded earlier.
Have successfully installed the secbrowser package to a StandaloneVM and to an ApppVM but that’s not reaaly ideal for me.
Has anyone a clue how to rectify.