New iPod "Classic" Compatibility
Moderator: Gurus
-
guest
See Article on iPodMinusiTunes.jiri wrote:I don't have either of these new generation iPods for testing (and won't have for at least a week). ...
Thanks,
Jiri
-
Guest
-
Santiago
If I had known that I woulda waited...I'd never really used iTunes before now and man, does it blow chunks or what?! It just does....well...nothing!Spazz wrote:Apple locked third party vendors from the ipod. Something about itunes and DB MD5 hashes not matching up. I actually just put an article in the news section about it. Sad day.
-
Guest
Welcome to the clubmetalewd wrote:If I had known that I woulda waited...I'd never really used iTunes before now and man, does it blow chunks or what?! It just does....well...nothing!Spazz wrote:Apple locked third party vendors from the ipod. Something about itunes and DB MD5 hashes not matching up. I actually just put an article in the news section about it. Sad day.
-
Michael Vogel
- Posts: 54
- Joined: Mon Jan 29, 2007 4:31 am
Found a table of the database header...
http://ipodminusitunes.blogspot.com/200 ... s-off.html
Maybe this can help...
Michael
Code: Select all
MHBD header:0x00 4 mhbd0x04 4 header size = 0xBC (changed)0x08 4 filesize0x0C 4 unknown = 10x10 4 version number = 0x19 (changed)0x14 4 child count = 0x05 (changed)0x18 8 itunes databaseid0x20 2 unknown = 20x22 2 unknown = 0x0263 (changed, 0x0000 before)0x24 8 ipod identification? (changed)0x2C 4 zero padding0x30 2 unknown = 10x32 20 unknown, changing completely from itdb to itdb0x46 2 language, seen: de, en0x48 8 library persistent id0x50 4 unknown, seen: 1, 50x54 4 unknown, seen: 0x08, 0x0D, 0x1D, 0x4D, 0x8D0x58 20 unknown some similarities between versions0x6C 4 timezone offset in seconds. +2*60*60 -> 0x00001C20, -4*60*60 = 0xFFFFC7C0 (really?)0x70 76 zero padding 0x00000000Maybe this can help...
Michael
-
TwiztidSinz
- Posts: 146
- Joined: Tue Sep 11, 2007 10:47 am
- Contact:
Knowing what the data is doesn't really help as much as we'd all like.
To allow other programs outside of iTunes to write to the database properly they'd need to crack the SHA-1 hash
See how much changing 1 letter effects the whole of the hash?
I have a feeling that this will be 'fixed' soon enough though.
is the just the location of the lock, not the key that unlocks it.0x32 20 unknown, changing completely from itdb to itdb
0x58 20 unknown some similarities between versions
0x32 is most likely a SHA1 hash, and 0x58 also could be.
To allow other programs outside of iTunes to write to the database properly they'd need to crack the SHA-1 hash
Code: Select all
SHA1("The quick brown fox jumps over the lazy dog")
= 2fd4e1c6 7a2d28fc ed849ee1 bb76e739 1b93eb12
SHA1("The quick brown fox jumps over the lazy cog")
= de9f2c7f d25e1b3a fad3e85a 0bd17d9b 100db4b3I have a feeling that this will be 'fixed' soon enough though.
