View Single Post
Old 06-24-2012, 04:32 AM   #399
kirokko
Member
kirokko began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Mar 2012
Device: Kindle 4
Sorry for double post, I just want that all this should be clear.

This is the MD5 hash for all kernels which I found:
Code:
99c31fa3ad2618e577194a912f139550  diags_kernel_forensic.img
3566d91f123e609b6a1aa8e679d65bfc  diags_kernel_hostar.img
2e880fdfd48c3d460151c5051ca8161b  main_kernel_forensic.img
f8ee194c84bbc824537b469265785691  main_kernel_hostar.img
2e880fdfd48c3d460151c5051ca8161b  main_kernel_mediafire.img
As you can see, main kernel form forensic server and from mediafire are the same. The main kernel from hostar differ from main kernel form forensic.

Also I attach info using file utility. This is for main kernel from forensic:
Code:
main_kernel_forensic.img: u-boot legacy uImage, Linux-2.6.31-rt11-lab126, Linux/ARM, OS Kernel Image (Not compressed), 4760896 bytes, Fri Sep 23 11:34:55 2011, Load Address: 0x70008000, Entry Point: 0x70008000, Header CRC: 0xEE89786D, Data CRC: 0x04F95A54
And this is for main kernel by hostar:
Code:
main_kernel_hostar.img: u-boot legacy uImage, Linux-2.6.31-rt11-lab126, Linux/ARM, OS Kernel Image (Not compressed), 4760896 bytes, Sat Sep  3 12:46:54 2011, Load Address: 0x70008000, Entry Point: 0x70008000, Header CRC: 0x3E5D2E75, Data CRC: 0x8C67E408
We can see that Header CRC and Data CRC differ.

And info about diags kernel. As you can see, MD5 also differ.
This info for diags kernel from mediafire (there is no such kernel on forensic server):
Code:
diags_kernel_forensic.img: u-boot legacy uImage, Linux-2.6.31-rt11-lab126, Linux/ARM, OS Kernel Image (Not compressed), 5122432 bytes, Sat Sep  3 09:01:08 2011, Load Address: 0x70008000, Entry Point: 0x70008000, Header CRC: 0x2A4A2E2C, Data CRC: 0xAB6660C5
And info for diags kernel by hostar:
Code:
diags_kernel_hostar.img: u-boot legacy uImage, Linux-2.6.31-rt11-lab126, Linux/ARM, OS Kernel Image (Not compressed), 5122432 bytes, Sat Sep  3 09:01:08 2011, Load Address: 0x70008000, Entry Point: 0x70008000, Header CRC: 0x2A4A2E2C, Data CRC: 0xAB6660C5
As we can see, Header CRC and Data CRC are the same.

Summarize all, the reason is wrong main kernel from forensic and mediafire. I think it would be useful to correct all links.
kirokko is offline   Reply With Quote