Compare commits
| SHA1 | |
|---|---|
|
65e71fd42e |
|
|
0630d8d025 |
2 changed files with 3 additions and 3 deletions
|
|
@ -23,7 +23,7 @@
|
|||
- More information about checksum measure :
|
||||
<details>
|
||||
|
||||
- Since v6.5.15+, the checksum is more strict, see [this explain](/docs/checksum_newapp.md) for more details.
|
||||
- Since v6.5.15+, the checksum is more strict, see [this explain](docs/checksum_newapp.md) for more details.
|
||||
|
||||
- The checksum measure (which throws GW934 as response) is known enabled from the server-side (v6.4.64 works since days 0, but return with GW934 error after 11 days), it requires client (MBCP/MBBank) app to sent the SHA256 hash of 3 app libraries `libapp.so` | `libmbshield.so` | `libclosestmadagascar.so` and all of 5 dex files (classes1->5.dex) to the server for comparing hash, and if it doesn't match, the server will prevent the app from logging in with GW934 error : `Re-install app to continue using app.`
|
||||
- The other function (eg: DigitalOTP) that works without logging in still works.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
in first day of v6.5.15+ released, there is no such checksum, it still the same as before, only until 4 days since release, there is toggle in backend that enable the check, remain unaffected for older base
|
||||
|
||||
same as v6.4.63+, in first day nothing happens, no checksum, but after 9 days, checksum appears.
|
||||
same as v6.4.63+, in first day nothing happens, no checksum, but after 11 days, checksum appears.
|
||||
|
||||
if one of these is modified (even one bit) will trigger checksum fail that refuse to accept login from
|
||||
|
||||
|
|
@ -40,4 +40,4 @@ mb.apk/assets/media_init_data
|
|||
mb.apk/assets/flutter_assets/assets/fonts/*
|
||||
mb.apk/assets/flutter_assets/fonts/*
|
||||
mb.apk/assets/flutter_assets/FontManifest.json
|
||||
```
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in a new issue