Active Topics

 


Reply
Thread Tools
free's Avatar
Posts: 739 | Thanked: 159 times | Joined on Sep 2007 @ Germany - Munich
#1
While making little audit of the n800, it stopped at a very early stage because stored checksums of some core applications are wrong.

Example of wrong ones:

#debsums -s dpkg
debsums: checksum mismatch dpkg file /usr/bin/dpkg
debsums: checksum mismatch dpkg file /usr/bin/dpkg-deb
debsums: checksum mismatch dpkg file /usr/bin/dpkg-query
debsums: checksum mismatch dpkg file /usr/bin/dpkg-split
debsums: checksum mismatch dpkg file /usr/lib/dpkg/enoent
#debsums -s lsof
debsums: checksum mismatch lsof file /usr/bin/lsof


Still most of them are correct:
#debsums -s busybox
#

Anybody has any idea how this happened?
Are we all owned by a trojaned firmware or it's just that they made a late modification (like they forgot stripping binaries) and did not recalculate the md5sums?
Prelinking is not installed on my system
Hum..

Running a full checksum audit is very scaring, some other core packages have their md5 invalid.
 
Posts: 79 | Thanked: 21 times | Joined on Sep 2007
#2
Stupid questions: Are you running this on the tablet? Where did you get debsums from?
 
free's Avatar
Posts: 739 | Thanked: 159 times | Joined on Sep 2007 @ Germany - Munich
#3
There's no stupid question! I didn't mention it.

I've packaged it, i'll put it on my repository in a minute.
It's the exact version from debian testing, easy to rebuild.

If you or anybody else can check on your own tablet, I would have a confirmation that it's not my image (reflashed a month ago and afaik I din't update dpkg or lsof)

Thanks
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#4
I'll try it out (Reflashed yday for the 11th time...) but i have been doing a lot of upgrading.

I wonder how the debian arm release would come out.
 
Posts: 251 | Thanked: 22 times | Joined on Dec 2007 @ Houston, Texas
#5
Related problem?

While running the Application Manager and asking it to Refresh Applications, it tends to hang up on downloading at about 850K and I end up having to cancel after about 20 minutes.

A check of the Log file showed that many of the repositories are failing checksums.

So....I delete all catalogs and then go to gronmayer and download a fresh set (excluding those that I know to be problems--it looks like there are some duplicates in the list at that site).

This appears to fix the problem, but it seems to happen every few days.

It's tedious to have to individually delete 40+ catalogs/repositories and then restore them.
 
free's Avatar
Posts: 739 | Thanked: 159 times | Joined on Sep 2007 @ Germany - Munich
#6
Should be there. Either go to http://debfarm.free.fr/pool for link (remove the stupid add with flashblocker) or directly from app manager with my repo.
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#7
debsums -s dpkg

debsums: can't open dpkg file /usr/share/doc/dpkg/changelog.gz (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/AUTHORS (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/THANKS (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/pseudo-tags (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/copyright (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/changelog.Debian.gz (No such file or directory)
debsums: checksum mismatch dpkg file /usr/bin/dpkg
debsums: checksum mismatch dpkg file /usr/bin/dpkg-deb
debsums: checksum mismatch dpkg file /usr/bin/dpkg-querydebsums: checksum mismatch dpkg file /usr/bin/dpkg-splitdebsums: checksum mismatch dpkg file /usr/lib/dpkg/enoent
 
free's Avatar
Posts: 739 | Thanked: 159 times | Joined on Sep 2007 @ Germany - Munich
#8
It's now working. So I've put rkhunter on my repository. THis is a direct port, no customization for the tablet (only removed cat -v not known by busybox). I'll create a specific version.
rkhunter -c --nomow --pkgmgr DPKG
Nice output!
 
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#9
Originally Posted by free View Post
Anybody has any idea how this happened?
Are we all owned by a trojaned firmware or it's just that they made a late modification (like they forgot stripping binaries) and did not recalculate the md5sums?
Prelinking is not installed on my system
It can be prelinking too. I think it was mentioned in mailing list by someone @ nokia.com that they do prelink stuff in final firmware. So most probably it is like
1. build all debs from source
2. install everything into rootfs
3. prelink it all together
4. make jffs2 image
__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
 
Posts: 3,841 | Thanked: 1,079 times | Joined on Nov 2006
#10
Originally Posted by qwerty12 View Post
debsums -s dpkg

debsums: can't open dpkg file /usr/share/doc/dpkg/changelog.gz (No such file or directory)
debsums: can't open dpkg file /usr/share/doc/dpkg/AUTHORS (No such file or directory)
..
If anyone is wondering - those missing files are OK, the NITs automatically remove files from /usr/share/doc if they get installed (unlike on a desktop).
__________________
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
 
Reply


 
Forum Jump


All times are GMT. The time now is 16:27.