ok, strace then? ;-)

Probably because they use self signed certificates

A fix is on it's way to CSSU, please test: http://talk.maemo.org/showpost.php?p...&postcount=222

Those of you that have changed their certificates, make sure to revert to "stock" state, otherwise installation may fail/be incomplete, the files in /etc are treated by apt/dpkg as config files and are not auto overwritten on a new package version installed.

@peterleinchen - followup to http://talk.maemo.org/showpost.php?p...&postcount=225

Not sure what you mean by "stock" but if it is PR1.3.1 I guess it makes sense to install everything *certman* , there are a couple of certificate fixes in CSSU not present in PR1.3.1.

Not to say I strongly recommend to install CSSU, be it -stabe, -testing or -thumb

Thanks, just wanted to be sure you did not code anything into a lib or similar.
I checked packages and yeah they seem to be installable to non-CSSU devices (I know I know).

Furthermore I have seen you exchanged the certs, so content of one into the other file (seen by sha1sum). It is a bit late now, but I began to play with order also and I found that the c_rehash is the one to "blame" (not that I am good in reading/understanding perl)
It fetches all pem/crt from directory, but not in any order. That is the reason why the link 7651b327.0 points to the newer cert, while 7651b327.1 should do so. (That is also reason why f3a27298eeb81b82801c4db69a3027990a2f72e2-1.pem works, as the symlink *.1 points to newer cert.

I checked it by just re-symlinking *.0 to older and *.1 to newer cert. And it worked.

--EDIT
Checked once more. And it is really weird/confusing/erroneous !
Now I added certs again. First old one, then new one (as before). And guess what? It worked without changing anything! When checking the symlinks they showed to the correct locations *.0 to *-1.pem (without manually re-symlinking).
Conclusio? IDK. Seems like it could work on some devices and on some not. Just regarding the order of $flist...

--editedit
Okay, now I am confused. Strike above.
It seems after 'c_rehash /etc/certs/common-ca' everything is fine.
I removed, inserted (in different orders) and more. But it is working always.
So easiest is to
make a backup of 00d85*.pem and 00d85*-1.pem
remove 0085*, cmcli -c common-ca -r 00d85*
remove 7651*.*, rm 7651*
reinsert 00d85* (and 00d85*-1) in exactly this order
cmcli -c common-ca -a backup_of_00d85*.pem
cmcli -c common-ca -a backup_of_00d85*-1.pem
this should be enough.
If it is not working for you, then do a
c_rehash /etc/certs/common-ca
If still not working, then start all over, but readd in reversed order (first 00d85*-1.pem and then 00d85*.pem)

Or just use fmg's patch (before messing around!).


I know I know, and the next device -be it a N900 from drawer or Neo900- will have for sure. But this device is so nicely running and customized, I just do not want to "spoil" it.

My GPS is not working for about a month. I use supl.google.com and tried a few others.
Ran this command to reset cache :
gconftool --recursive-unset /system/nokia/location

Reflash done(emmc+rootfs), still no help. It's keep on searching and never locks in. Please let me know how to fix this. Could this be a possible hardware issue?
Thanks

If you read the thread carefully you will see that there is a patch in cssu-devel to fix this issue

AGPS makes acquiring a fix much faster than just using the gps receiver and doing a sky search. Without agps you will eventually get a fix. sO, if your n900 does not get a fix AT ALL (leave it for 20\30 mins using something besides Nokia Maps) then your device has a hw fault.

(Edit: thanks pichlo for the heads up. Never use Nokia Maps so who would know.....)

The problem is that the built-in Nokia Maps application times out after just 10 minutes - even though the time it takes to receive the full almanac under ideal conditions with no retries is 12.5 minutes - which means it will never acquire a lock without help.

This has been discussed countless times, just do a search. Nokia was aware of that and they marked it as "won't fix" ("10 minutes ought to be enough for everybody!").

Get a third-party GPS application such as Location Test discussed in this thread to help Nokia Maps with the lock. It will not make it any faster - for that you need the patch that sixwheeledbeast mentioned - but it will not time out and hence get the lock eventually without the supl server assistance.

Thanks a lot sixwheeledbeast, handaxe and pichlo. I read about that fix(I think maemo-security-certman ??), but i believe it's a fix with CSSU. I don't use CSSU for some reasons. I would like to know whether it's possible to use that fix without CSSU installed. I don't use Nokia maps, i'm happy using the Marble maps which was so convenient for me.
Thank you