How to fix a BADSIG with SOUP? Partial update happening?

[bug...@gmail.com]

Hi,

I posting about 2 potential issues:
1. A signature problem for the Ubuntu extra archive
2. A partial upgrade of my SO system may be occuring because of that
---

1. A signature problem for the Ubuntu extra archive

I have recently changed network provider and I noticed my Ubuntu based VM have problems updating with an error related to the integrity/signature of the update list:
Checking for updates...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://gb.archive.ubuntu.com trusty Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key <ftpm...@ubuntu.com>

If I go through a VPN then that's OK (makes you wonder if the Netowrk Provider is using a proxy for Ubuntu updates), but that's not a long term solution for me.

Searching on what could be the cause and solution besides a VPN, I found an article suggesting we should run the following if we encounter the "BAGSIG" error.
I understand we have to be careful when updating SO and "Soup" is recommended over apt-get update.

Can I safely run the following set of commands? or is there some kind of "soup-clean"
https://itsfoss.com/solve-badsig-error-quick-tip/

sudo apt-get clean
cd /var/lib/apt
sudo mv lists oldlist
sudo mkdir -p lists/partial
sudo apt-get clean
(sudo apt-get update) replace that with soup

---
2. A partial upgrade of my SO system may be occurring because of the above error

Although I am getting an update error, it looks like SOUP is still being able to retrieve some update files (looking at different source lists probably?)
Does that mean my system is only getting partially updated? and thus this could lead to some stability issue?
I would hope that dependancies check would prevent that, but it is not ideal.

I guess my question is:
I am running the risk of getting an unstable system? and should cancel any updates if there are any BADSIG signature error?

Below is a snapshot of my last SOUP output:

Checking for kernels that can be removed...
No kernels are eligible for removal

Checking for updates...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://gb.archive.ubuntu.com trusty Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key <ftpm...@ubuntu.com>

W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/trusty/Release

W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
securityonion-pfring-module is already the newest version.
The following packages were automatically installed and are no longer required:
libllvm3.6 linux-headers-3.19.0-65 linux-headers-3.19.0-78
linux-headers-4.4.0-57
0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
libllvm3.6 linux-headers-3.19.0-65 linux-headers-3.19.0-78
linux-headers-4.4.0-57
The following NEW packages will be installed:
geoip-bin libgeoip-dev libjson-c-dev
The following packages will be upgraded:
libgnutls-openssl27 libgnutls26 libgudev-1.0-0 libpam-systemd libssl-dev
libssl-doc libssl1.0.0 libsystemd-daemon0 libsystemd-login0 libudev1 libxpm4
openssl securityonion-ndpi systemd-services udev xplico
16 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,130 kB of archives.
After this operation, 2,052 kB of additional disk space will be used.
Get:1 http://gb.archive.ubuntu.
[...]
Install goes through and reboot happens

Thanks,
B.

[Wes]

B,

I have not noticed this, however, I will perform some testing and see if I can duplicate the issue.

Thanks,
Wes

[bug...@gmail.com]

Thanks Wes,
I thought the issue was due to my network provider or a corrupt update repository list (hence the question about how safe it was to follow the steps I saw in another linux forum), but if you can reproduce the problem then perfect!

Please let me know if there is anything else I should be doing to help troubleshooting the problem.

Thanks,
B.

[Wes]

B,

I've not been able to duplicate this -- you may want to clean up your /var/lib/apt/lists and re-run apt-get update.

Thanks,
Wes

[bug...@gmail.com]

Thanks for trying Wes, I will do just that.
B.