macchiaz-o

Well-Known Member
First Name
Jonathan
Joined
Nov 25, 2019
Threads
168
Messages
8,157
Reaction score
15,299
Location
🔑 ]not/A/gr8'Place.2.store-mEyePassword[ 👀
Vehicles
MY21 J1 Premium RWD SR
Country flag
Also, the APIs are documented at developer.ford.com.
I've requested access to developer.ford.com/fordconnect a bunch of times. Never got any response. I do have a developer.ford.com account but the other APIs, AppLink and OpenXC, don't seem useful to me right now.
Sponsored

 

AEtherScythe

Well-Known Member
First Name
Leon
Joined
Oct 11, 2020
Threads
19
Messages
241
Reaction score
570
Location
Michigan
Vehicles
Ford Mustang Mach-E, Ford Escape Hybrid
Occupation
Sr. IT/Product Architect; Enterprise and Cloud Manageability Engineering
Country flag
Doesn't this suggest that if you were to sign into my company's WiFi, someone in IT at the company could see, in plain text, the traffic between your phone and @Ford Team's servers?
Apples and oranges. You're raising an Area 51 level conspiracy theory level of nonsense against what happened totally between ME on MY device, and something happening at an enterprise level. Your company shouldn't be doing what they're doing.

There's nothing wrong with what I am doing with me and my data on my device. Please just stop.
 

mikeho

Well-Known Member
First Name
Mike
Joined
Jun 25, 2020
Threads
10
Messages
158
Reaction score
134
Location
San Jose, CA
Vehicles
Mustang Mach-E
Country flag
@AEtherScythe no... @macchiaz-o is not spouting a conspiracy theory. When TLS initiates a handshake with the server, the server is supposed to respond with a certificate. That certificate should be checked to ensure that it is legitimate and secure. The fact that your VPN/proxy can intercept the calls to Ford's servers suggests that when the handshake occurs, the client (FordPass app) is not verifying that the certificate and public key that it is receiving is the correct one. In addition, that means that the symmetric key used for communication is also compromised.

In a public/private key pair encryption scheme, only the private key is capable of decrypting a transmission, which includes the URL and the content body (if it is a POST), and it is never transmitted or shared. Ford's servers would never send that over. But once that part is compromised, then the proxy also has a copy of the symmetric key used for communication, which it can used to decrypt any message now sent during this session.

So that means that the following is happening:
1. The app is making a request to the server over TCP to establish a secure connection.
2. Your proxy is intercepting this message and spoofing a similar message to Ford's servers.
3. When a response is received by Ford, your proxy can unpack the message and repackage it to send to the app.
4. The app accepts the response and assumes that the secure channel is established.
5. For every message now sent over SSL, the proxy can decrypt the message to show you and re-encrypt the message so that the server will accept it.

See
https://www.cloudflare.com/learning/ssl/how-does-ssl-work/
https://stackoverflow.com/questions/14907581/ssl-and-man-in-the-middle-misunderstanding https://stackoverflow.com/questions/499591/are-https-urls-encrypted
https://security.stackexchange.com/...lf-signed-certificate-while-private-keys-is-g

This means that the client is not authenticating the origin server properly.
 

ChasingCoral

Well-Known Member
First Name
Mark
Joined
Feb 3, 2020
Threads
376
Messages
12,403
Reaction score
24,517
Location
Maryland
Vehicles
GB E4X FE, Leaf, Tacoma, F-150 Lightning ordered
Occupation
Retired oceanographer
Country flag
I had the issue where when your charging and do a remote start when you get in the car and go. I won’t start. Today I was at the dealer and they did the software update to multiple controllers in the car. They then put it on a charger. About 20 minutes later I did a remote start and when I got in to drive it started right up. They also checked the 12V battery and it checked out as healthy. So now I guess we will see if they get the charging issue with the 12V resolved.
Sounds like the 21B02 issue. When was yours built?
 

ChasingCoral

Well-Known Member
First Name
Mark
Joined
Feb 3, 2020
Threads
376
Messages
12,403
Reaction score
24,517
Location
Maryland
Vehicles
GB E4X FE, Leaf, Tacoma, F-150 Lightning ordered
Occupation
Retired oceanographer
Country flag
For starters, the FordPass app isn't showing all the charging events nor the "conditioning" nor the 12V battery charging events (which personally I have never seen)...

Looking back at the data from my ChargePoint charger (not the FordPass app), it does seem as if the car calls for more LVB charging the colder it is outside. It isn't strictly on a six hour interval, especially since the temperatures have inched well above freezing during the day these past few days. I don't see the "conditioning" messages as frequently now that it's warmer out, nor does my ChargePoint charger show the vehicle taking power on regular intervals. It does seem as though the car calls for LVB charging power only as needed.

If you want to monitor LVB charge patterns, yourself, I can tell you how I'm doing it...

I am using a for-pay app call "HTTP Catcher" with the SSL decrypt in-app purchase. When enabled it turns on a VPN which the FordPass app must go through. The FordPass app thinks it's negotiating SSL with the Ford endpoints but in reality the HTTP Catcher is doing the negotiation and repeating same with the Ford endpoints. That allows the HTTP Catcher to intercept the communications in the middle.

Under this arrangement, you can then view the the REST calls and responses In the HTTP Catcher. The API of interest is of the following form:

https://usapi.cv.ford.com/api/vehicles/v4/{vin}/status?lrdt=01-01-1970%2000:00:00

That is the one that will have the battery statuses like the one I pasted above.
Cool. Black magic!
 


Shayne

Well-Known Member
Joined
Aug 9, 2020
Threads
18
Messages
3,340
Reaction score
2,487
Location
Northern Ontario Canada
Vehicles
2021 MME4x Prem
Occupation
Retired
Country flag
AFAIK, an it's AT&T modem and so in Canada it'll be a roaming arrangement. They could have different arrangements in different countries, especially Europe, but anyway it won't matter if generally there are plenty of carriers in the area, you need to know THE carrier and whether they have good coverage where you are. :-/

In my experience the FordPass app does a better job of getting the charge location address correct.

What I saw today is that if I delete my home location from the car, then add it again, it initially just shows at a lat/long location, and then the car does a lookup to approximate the address. The car is using a different search than the FordPass app, so because I am on a corner and my garage is on the side street the car gets the address on the side street, which is not my actual address. The FordPass app gets my actual address. The addresses do not agree, but with the car backed out of the garage and open air view of the sky, it seems at least the lat/long coords are correct, and how it is displayed is largely cosmetic, AFAICT; the lat/long is what matters most.

If you're trying to get this to work and you're ignoring the FordPass app as an avenue for setting and verifying the charge settings, that's probably part of the problem. It should of course "just work" but it isn't working for you and if I understand you correctly you're trying to do it all from the car and not FordPass and that's a difference. I ultimately got it working, but from the FordPass app.

Whether or not the car is running is a factor even when changing the settings from the FordPass app. Today, I noticed that when changing the settings from the car it wanted to call the deleted and re-added location "Default" and I couldn't get it to rename to "Home" until I shut the car off. If the car was running and I tried to change the name via FordPass it would appear to save as "Home" but quickly reverted to "Default" and in the car it said "Default" all along.

So there is definitely a tug-of-war between Sync and the FordPass there, with FordPass ultimately "winning" after a few tries, once the car was shut off.

One reason I favor using the FordPass app for setting the charge schedule (other than it ultimately does work FOR ME), is that from the app I can request "recommended" settings based on my energy provider and it gets the time-of-day rates correct automatically (half the cost from 11p - 9a weekdays, anytime on weekends vs. 2x the cost any other time). I can of course manually make those schedules in the car, but I want Ford to know my energy provider so they can cross-reference the costs based on time of day with my provider.

But as I said trying to do all of this strictly from the car is unreliable for me and it seems, same is true for you. HTH. Good luck! =D
It works off coordinates and the address is for users info only I think.

First time I did set it up in the app and it did not work now I sit at the terminal where the OS is the car and have taken Fordpass out of the equation as it should have nothing to do with it? Doing it strictly in the car take the little app out of the equation does it not?

Maybe I am confused but what does AT&T have to do with sync running/maintaining the vehicle. The vehicle knows it is home once it knows that does it keep checking during the charging session? I thought it was more like an OS (named sync) running the car and has no need for outside info. A PC will run windows and function correctly and I never need to plug a cat6 into it. If Sync the OS running the car knows it is home at the beginning then either sync and/or the car is not running correct (dysfunctional PC bad ram, buggy windows OS) unless you think it looses it location and thinks it has move while charging. Right now Fordpass has no previous/saved charging locations but the car does. Tried that and it does not work. I can uninstall Fordpass and it will not work. Fordpass should have no logical bearing on why the charging schedule is set, says it will do it and then resets to default (immediate 100%) and does not.
 

ChasingCoral

Well-Known Member
First Name
Mark
Joined
Feb 3, 2020
Threads
376
Messages
12,403
Reaction score
24,517
Location
Maryland
Vehicles
GB E4X FE, Leaf, Tacoma, F-150 Lightning ordered
Occupation
Retired oceanographer
Country flag

Shayne

Well-Known Member
Joined
Aug 9, 2020
Threads
18
Messages
3,340
Reaction score
2,487
Location
Northern Ontario Canada
Vehicles
2021 MME4x Prem
Occupation
Retired
Country flag
Great news CC hope take two goes better. I love driving it make the destination less important.

I have installed phone as a key on two phones twice to set the Schule up via fob. This was my original problem prior to the the 12V crashing at not a good time -27C (-17F). Not sure how more low level than that I can get. I did do the vol arrow and reset sync for the first time last night did not help in that combination. First I set it up in the app didn't work. So deleted it from saved locations thinking it would still be in previous (with warning messages about deleting it from there) but it is not. I did @JamieGeek suggestion and went and charged elsewhere (DCFC tested and it worked but @ 30KW at a free one) came back and home repopulated into previous locations. Right now deleting it may still incurs moving it 90 Km. Who wants to volunteer to delete one of there saved charging schedules and see if it copies it back to previous or it is just gone ;).

Came back 46% 200 km yesterday. Got this message.
Ford Mustang Mach-E Deep Sleep Mode - 12v battery drained dead [update: Mach-E jump started] Screenshot 2021-02-27 at 8.28.04 AM - Copy

Think it knows it is at charging schedule home? Fordpass has not updated since I unplugged it 10 hours ago at 63% before I went to bed. It is hard to test a charging schedule when the vehicle is charged to 100%. All good just need the charging schedule to work. The vehicle runs great. I always learn things the hard way but understand them at the end. If I set phone as a key and link it to a profile for the third time I should have it down pat.
 

ChasingCoral

Well-Known Member
First Name
Mark
Joined
Feb 3, 2020
Threads
376
Messages
12,403
Reaction score
24,517
Location
Maryland
Vehicles
GB E4X FE, Leaf, Tacoma, F-150 Lightning ordered
Occupation
Retired oceanographer
Country flag
So, rear motor and software?

Going on a trip this weekend right?
All the latest software and a new primary drive unit. Leave for Florida tomorrow.
 

Illinibird

Well-Known Member
First Name
Mike
Joined
Oct 13, 2020
Threads
40
Messages
1,563
Reaction score
1,445
Location
Frankfort Illinois
Vehicles
2015 Acura MDX Adv; 2016 Titanium Fusion Hybrid
Occupation
retired Endodontist (root canal specialist) and Clinical Assistant Professor
Country flag

Shayne

Well-Known Member
Joined
Aug 9, 2020
Threads
18
Messages
3,340
Reaction score
2,487
Location
Northern Ontario Canada
Vehicles
2021 MME4x Prem
Occupation
Retired
Country flag
You’re a brave man Charlie Brown!
Why this new tech is fun and relaxing to drive. Mark does not sound like a run from Florida to Maryland is a bad thing. He will definitively get a chance to break it in and test it.
All the latest software and a new primary drive unit. Leave for Florida tomorrow.
We want stories.
 

dbsb3233

Well-Known Member
First Name
TimCO
Joined
Dec 30, 2019
Threads
54
Messages
9,298
Reaction score
10,812
Location
Colorado, USA
Vehicles
2021 Mustang Mach-E FE, 2023 Bronco Sport OB
Occupation
Retired
Country flag
Why this new tech is fun and relaxing to drive. Mark does not sound like a run from Florida to Maryland is a bad thing. He will definitively get a chance to break it in and test it.
A test for sure. Hopefully a successful one.

Trial by fire.
 

AEtherScythe

Well-Known Member
First Name
Leon
Joined
Oct 11, 2020
Threads
19
Messages
241
Reaction score
570
Location
Michigan
Vehicles
Ford Mustang Mach-E, Ford Escape Hybrid
Occupation
Sr. IT/Product Architect; Enterprise and Cloud Manageability Engineering
Country flag
@AEtherScythe no... @macchiaz-o is not spouting a conspiracy theory.
...

This means that the client is not authenticating the origin server properly.
That isn't how HTTP Catcher works. The fact that it's a VPN on the same device as the app allows it to see both sides of the key exchange and replay them, same same re: client and server. There's nothing anyone can do to stop this and there's no way it can be used to exploit it against anyone else's data. It only works on-device by the user of the FordPass app looking strictly at their own data.
Sponsored

 
 




Top