You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using Objection to bypass SSL Pinning and test some smart home devices and their apps.
While testing apps from vendors such as IKEA, I noticed that they communicate with a local API initiated by the ZigBee Hub, rather than an internet API. However, Objection only bypasses SSL Pinning for requests to the internet, and not for communication between the app and the hub, which is also SSL encrypted and on port 8443.
I am looking for a solution to bypass SSL Pinning for this communication. Any suggestions would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently using Objection to bypass SSL Pinning and test some smart home devices and their apps.
While testing apps from vendors such as IKEA, I noticed that they communicate with a local API initiated by the ZigBee Hub, rather than an internet API. However, Objection only bypasses SSL Pinning for requests to the internet, and not for communication between the app and the hub, which is also SSL encrypted and on port 8443.
I am looking for a solution to bypass SSL Pinning for this communication. Any suggestions would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions