Re:Pokemon Go: Reverse Engineering of the Android App
by acq on Monday July 18, 2016 @09:59AM
(#12115049)
Imho, it was more of a "why bother?".
Most of the code is inside Unity, which is harder to access, but they ended up putting more code in the Android part (for the Pokémon Go Plus for example), and probably forgot about it.
They can still obfuscate later releases, but the lack of certificate pinning is going to be harder to fix.
Or perhaps was this a conscious decision, not do to it for some reason?
Most of the code is inside Unity, which is harder to access, but they ended up putting more code in the Android part (for the Pokémon Go Plus for example), and probably forgot about it.
They can still obfuscate later releases, but the lack of certificate pinning is going to be harder to fix.
- the code is not obfuscated, which makes attempts at reverse engineering much easier.
- possible to rebuild a functional project
- dependencies could be better managed
- no hint to future VR or Cardboard versions
- it may be possible to downgrade the minimum requirements (below Android 4.4)
- we can get access to quite a few things: code for location/network/sensors and communication with Pokémon Go Plus
- the requests can be easily intercepted because of the lack of certificate pinning