Eu tenho construído uma nova instância do Ubuntu usando o Cubic para criar um ISO personalizado. Isso funcionou bem no passado, mas por algum motivo depois de ter sido carregado no ambiente chroot, não consigo atualizar o apt devido a vários erros de assinaturas inválidas.
root@mine:/etc/apt# apt update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
At least one invalid signature was encountered.
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Err:2 http://archive.ubuntu.com/ubuntu xenial InRelease
At least one invalid signature was encountered.
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
At least one invalid signature was encountered.
Fetched 204 kB in 18s (10.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: At least one invalid signature was encountered.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu xenial InRelease: At least one invalid signature was encountered.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: At least one invalid signature was encountered.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease
At least one invalid signature was encountered.
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease At least one invalid signature was encountered.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease At least one invalid signature was encountered.
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@mine:/etc/apt# apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
At least one invalid signature was encountered.
Err:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
At least one invalid signature was encountered.
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Err:3 http://security.ubuntu.com/ubuntu xenial-security InRelease
At least one invalid signature was encountered.
Fetched 204 kB in 17s (11.4 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu xenial InRelease: At least one invalid signature was encountered.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: At least one invalid signature was encountered.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: At least one invalid signature was encountered.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease At least one invalid signature was encountered.
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease At least one invalid signature was encountered.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease At least one invalid signature was encountered.
W: Some index files failed to download. They have been ignored, or old ones used instead.
Eu tentei uma série de métodos para consertar isso, eu suspeito que é por causa de algo sendo feito por cúbicos ao formar o sistema squashfs que está quebrando o chaveiro do GPG.
A lista do apt-key mostra:
root@mine:/etc/apt# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <[email protected]>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <[email protected]>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <[email protected]>
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <[email protected]>
E a atualização do apt-key mostra:
root@mine:/etc/apt# apt-key update
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <[email protected]>" not changed
gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key <[email protected]>" not changed
gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>" not changed
gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) <[email protected]>" not changed
gpg: Total number processed: 4
gpg: unchanged: 4
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
gpg: WARNING: unsafe ownership on homedir '/tmp/tmp.VI7PlJB3k0'
root@mine:/etc/apt#
Alguma idéia de como corrigir isso? Eu tentei executar o apt clean sem nenhuma mudança, junto com a importação de um arquivo de trabalho conhecido sources.list e até mesmo trusted.gpg. As permissões em /etc/apt/sources.list.d/ e /etc/apt/trusted.gpg.d/ são legíveis em todo o mundo, de modo que o apt deve ser capaz de ler as chaves.
Esta é uma compilação limpa, o ISO usado pelo Cubic foi testado em uma VM sem problemas, então parece ser um problema cúbico, mas não tenho certeza do que o Cubic poderia ter feito para causar isso ou como tentar. consertá-lo em chroot eu mesmo.
Qualquer sugestão / conselho seria muito apreciada.
Maxy