Open kapouer opened 5 days ago
Looking into this. It appears that the key might have expired although I remember setting it up for 2 years.
@kapouer Are you seeing this error when you run apt update
?
Yes
Le ven. 29 nov. 2024, 09:59, Anoop M D @.***> a écrit :
Looking into this. It appears that the key might have expired although I remember setting it up for 2 years.
@kapouer https://github.com/kapouer Are you seeing this error when you run apt update ?
— Reply to this email directly, view it on GitHub https://github.com/usebruno/bruno/issues/3569#issuecomment-2507359249, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABACTWALLSBFTDUEPH2P432DAUHDAVCNFSM6AAAAABSWPKJ6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGM2TSMRUHE . You are receiving this because you were mentioned.Message ID: @.***>
with both keys (56333 and 9FA) i just get a
Warning: http://debian.usebruno.com/dists/bruno/InRelease: The key(s) in the keyring /etc/apt/keyrings/bruno.gpg are ignored as the file has an unsupported filetype.
used
gpg --no-default-keyring --keyring /etc/apt/keyrings/bruno.gpg --keyserver keyserver.ubuntu.com --recv-keys $KEY
I have checked the following:
Describe the bug
Err:12 http://debian.usebruno.com bruno InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 56333D3B745C1FEC
But the README gives 9FA6017ECABE0266.
While this might be some mishandling of the key (typically the belief that one needs a new key when it expires - it doesn't), it might also be sign of a compromised distribution channel !
.bru file to reproduce the bug
No response
Screenshots/Live demo link
http://debian.usebruno.com/