By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2592 - GPG key mismatch
Summary: GPG key mismatch
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: debian (show other bugs)
Version: R14.1.x [Trinity]
Hardware: amd64 Linux
: P5 blocker
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2016-02-13 07:21 CST by Salvo 'LtWorf' Tomaselli
Modified: 2016-02-13 16:03 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Salvo 'LtWorf' Tomaselli 2016-02-13 07:21:18 CST 
After doing aptitude update I get this error

W: Errore GPG: http://mirror.xcer.cz/trinity-sb stretch InRelease: Le seguenti firme non sono state verificate perché la chiave pubblica non è disponibile: NO_PUBKEY 608F5293A04BE668


But the website instructs to add this key
 apt-key adv --keyserver keyserver.quickbuild.pearsoncomputing.net --recv-keys F5CFC95C


Which does not match.

Were you hacked?
Comment 1 Slávek Banko 2016-02-13 07:42:47 CST 
No, it's not a hacking problem :)

You've used apt source 'Preliminary stable builds' but the gpg key for 'Official release'. Preliminary stable builds is a separate apt source signed by another key - see wiki page:

https://wiki.trinitydesktop.org/Preliminary_Stable_Builds

Please verify that with the corresponding GPG key is signature okay, and then you can close this bug report.
Comment 2 Salvo 'LtWorf' Tomaselli 2016-02-13 16:03:45 CST 
You are correct.

Sorry for the noise.