It seems that the "Client-DAAP-Validation" hash has changed in this new
version. I haven't been able to figure out what changed yet but I'm trying to
figure it out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The music sharing in iTunes 7.0 has actually changed. Although slight, it’s impact is effective. I’ll explain why it hasn’t impacted Tangerine however.
iTunes sharing works on the client-server model. One side, sends a connect request & if it checks out the other side responds with data (music etc). If you both connect to each other’s iTunes, you will be both a client, and a server in the other direction.
The Client-DAAP-Validation header is the primary way an iTunes server checks to see if the current client attempt looks like legitimate Apple software.
In previous versions it was a combination of MD5 hashes of static text, along with the dynamic DAAP request and an ID.
Analysing packet samples shows the Client-DAAP-Validation header used to connect to an iTunes 7.0 host has changed. This is being worked on, and hopefully a new open specification will be out soon.
Tangerine is unaffected, as it is only the server component, and the iTunes client curiously still does not make any substantial checks to see if a validation-esque string is returned correctly from the DAAP server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1560231
This is true, and they are mostlikely aware of this.
Hopefully they can work this out easily.
Logged In: NO
Yes please. Keep it coming
Logged In: YES
user_id=430868
It seems that the "Client-DAAP-Validation" hash has changed in this new
version. I haven't been able to figure out what changed yet but I'm trying to
figure it out.
Logged In: NO
any news on this yet?
Logged In: NO
Does this to me too, developers seem to have disappeared of
the radar. Their standard e-mail bounces back.
Logged In: NO
The music sharing in iTunes 7.0 has actually changed. Although slight, it’s impact is effective. I’ll explain why it hasn’t impacted Tangerine however.
iTunes sharing works on the client-server model. One side, sends a connect request & if it checks out the other side responds with data (music etc). If you both connect to each other’s iTunes, you will be both a client, and a server in the other direction.
The Client-DAAP-Validation header is the primary way an iTunes server checks to see if the current client attempt looks like legitimate Apple software.
In previous versions it was a combination of MD5 hashes of static text, along with the dynamic DAAP request and an ID.
Analysing packet samples shows the Client-DAAP-Validation header used to connect to an iTunes 7.0 host has changed. This is being worked on, and hopefully a new open specification will be out soon.
Tangerine is unaffected, as it is only the server component, and the iTunes client curiously still does not make any substantial checks to see if a validation-esque string is returned correctly from the DAAP server.