I didn't notice different files when I downloaded. I was only offered Pre 3.2.
Hope I didn't do the wrong one.
Sorry for the confusion, I should have noted, the site only presents you with a single version based on your VIN/ESN and a lookup in Ford's database to see which version of Sync you are running/should be running. You guys should be in good shape with what it provided to you.
I'm a software dev, so I poked around and picked up on the two variations. I did so by digging through some of the web service API calls and JSON data that was returned back in the download page (pretty verbose and quite informative - some of Fords sites, like the owner.ford.com even show the buckets/categories they break us each down into - wether we are satisfied, have submitted poor ratings on experiences, recent purchasers, etc - very detailed - anyway....) and the JavaScript that makes the pages function. Using the results along with a little educated guessing on some variations of the provided Amazon AWS-S3 bucket URL(s) where the map files are being served from, provided me the right results. The install PDF was also served from a Ford web service API based on your VIN/ESN and other parameters, and I jiggered with those, again with some educated guessing on the naming convention to get it to send me the accompanying alternate install instructions for the other variation, in PDF format.
The license key that you are presented with is a tar'd/gzipped folder containing a plain text "License.txt" file with the product SKU number associated with the update, and the Version.der file is basically a code signing cert - an X.509 certificate in the binary DER format, that contains an RSA public key (Using Ford's In-Vehicle Security groups SyncGen3, self signed CA), and is signed with the private portion of their 2048 bit RSA key, a small payload (containing the Ford Part # for the map data, the length of the License.txt (14 bytes) and the ESN you submitted and a hash (sha256 format) of the License.txt file. The other portions of the map data are also tar'g/gzipped and contain similar Version.der files for essentially signing the contents of the archives, the files in each, and a hash of each file to make sure they haven't been tampered/modified. You can validate the files with standard openssl libs.
Couple additional notes:
While you may be able to download the other map variation(s), they have a different Ford Product #, and thus the license file which wraps your ESN, will be tied to a different product number. I realized this after looking through the file structure after I finished downloading, my previous post while was while I was still waiting for things to finish downloading and didn't realize how things were bound to the license yet. This also means, you can't browse around for screenshots where folks may have exposed their VIN and ESN, as you may be able to use them to get another set of files, but they won't validate on your car with different values. I won't go into how to possibly generate an additional valid license file from the Ford web service API based on your own VIN/ESN but for a different product variation…
FWIW, anyone who downloads the files can easily deduce these things from what you are provided, and what comes through directly from the website during your transactions - you just have to know what to look for
I just thought I'd share the extra detail here, as these forums are a great source of information. I've got a ELM327 OBD2 adapter coming this weekend, so I can do a little FORScan tinkering. Finally going to disable that stupid double-honk and do some other tweaking.
