Notices


Reply
Thread Tools
Posts: 19 | Thanked: 16 times | Joined on Sep 2010
#11
The problem is only OVI repository I tried to comment

deb https://downloads.maemo.nokia.com/fremantle1.2/ovi/ ./

in /etc/apt/sources.list.d/hildon-application-manager.list and the problem disappear.
I tried to verify the signature of 3 Release file.

Code:
# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg  --verify Release.gpg_apps   Release_apps
gpg: Signature made mer  2 feb 2011 12:42:31 CET using DSA key ID 13FA4ED6
gpg: Good signature from "Nokia repository signing key 4v1"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1CC1 A2A2 B8CE 8F25 8F89  6B42 07C0 DFF7 13FA 4ED6

# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg  --verify Release.gpg_mr0  Release_mr0
gpg: Signature made lun 25 ott 2010 11:42:40 CEST using DSA key ID 13FA4ED6
gpg: Good signature from "Nokia repository signing key 4v1"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1CC1 A2A2 B8CE 8F25 8F89  6B42 07C0 DFF7 13FA 4ED6
but ovi Release file I have

Code:
# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg  --verify Release.gpg_ovi    Release_ovi
gpg: Signature made mar 19 lug 2011 00:05:36 CEST using RSA key ID 60A655EF
gpg: Can't check signature: public key not found
Nokia forget to release the public key 60A655EF.
In my apt-key list i have these keys:
Code:
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub   1024D/C8009E74 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 1v1
sub   2048g/C1B723AA 2007-10-05 [expires: 2012-10-03]

pub   1024D/7C4B240D 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 1v2
sub   2048g/0580E9EB 2007-10-05 [expires: 2012-10-03]

pub   1024D/32009917 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 2v1
sub   2048g/1F2E958F 2007-10-05 [expires: 2012-10-03]

pub   1024D/E1448911 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 2v2
sub   2048g/EE0B0D1A 2007-10-05 [expires: 2012-10-03]

pub   1024D/413DA5CA 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 3v1
sub   2048g/4D5BEEF4 2007-10-05 [expires: 2012-10-03]

pub   1024D/EC9627ED 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 3v2
sub   2048g/0E39BF83 2007-10-05 [expires: 2012-10-03]

pub   1024D/13FA4ED6 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 4v1
sub   2048g/8B1115B2 2007-10-05 [expires: 2012-10-03]

pub   1024D/4C36F0B6 2007-10-05 [expires: 2012-10-03]
uid                  Nokia repository signing key 4v2
sub   2048g/3CF7720A 2007-10-05 [expires: 2012-10-03]

pub   2048R/616730BD 2009-07-27
uid                  maemo.org Extras repositories (Fremantle Extras) <repositories@maemo.org>

pub   1024D/4510B055 2009-03-18
uid                  MaemoSW Admin <admin@maemo.research.nokia.com>
sub   2048g/F18168D7 2009-03-18

pub   1024D/FF445C24 2009-03-16
uid                  Mozilla Release Engineering <release@mozilla.com>
Sorry for the paranoid.
 
Posts: 270 | Thanked: 45 times | Joined on May 2010 @ UK
#12
Sorry for being a noob could you please explain in detail how to get rid of this problem please!
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#13
Originally Posted by romiiio View Post
Sorry for being a noob could you please explain in detail how to get rid of this problem please!
Find someone at Nokia and ask them to release the public key (though if it's not certified in any way then it's no more secure really - it probably ought to be certified with one the old keys), or just ignore the warning as it doesn't actually stop anything from working.
 
Posts: 5 | Thanked: 0 times | Joined on Jul 2010 @ Bogor - Indonesia
#14
YEAH...I Have this problem too...
 
Posts: 154 | Thanked: 13 times | Joined on Jan 2011
#15
oke, disable all repos. refresh ham, enable all repos, refresh. It worked for me!
 
Posts: 5 | Thanked: 0 times | Joined on Jul 2010 @ Bogor - Indonesia
#16
Originally Posted by Bramji View Post
oke, disable all repos. refresh ham, enable all repos, refresh. It worked for me!
yes its work when I use from HAM, but when I update from xTrm I steal get error.
 
Banned | Posts: 695 | Thanked: 308 times | Joined on Apr 2011 @ originally pakistan ,now in china
#17
as far as i know this issue has been raised in past in 2010 and now here it comes again in 2011,i wonder when it gets over ?this public key issue .
cant update right through x-terminal.it has been almost a month or so ,dev's isnt there any method been evolved to handle this ?
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#18
Originally Posted by prankster View Post
as far as i know this issue has been raised in past in 2010 and now here it comes again in 2011,i wonder when it gets over ?this public key issue .
cant update right through x-terminal.it has been almost a month or so ,dev's isnt there any method been evolved to handle this ?
The public key issue has absolutely zero effect on whether or not you can update anything. That's why it's a WARNING, not an ERROR.
 

The Following User Says Thank You to Rob1n For This Useful Post:
Posts: 32 | Thanked: 9 times | Joined on Feb 2011
#19
i have disable this repository and now update work ok, but will that be reapired or not !?
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#20
Originally Posted by sehrz View Post
i have disable this repository and now update work ok, but will that be reapired or not !?
I doubt it will be fixed, no, but as it doesn't actually prevent anything from working then there's no major issue.
 
Reply


 
Forum Jump


All times are GMT. The time now is 13:52.