Deprecated DexFile APIs about free-rasp-flutter

[talsec-app]

Thanks for your submission. We are inspecting this issue internally. We will get back to you with a resolution.

[ShadyZekry]

Thanks for paying attention, @talsec-app.

My main concern is that the callbacks is not being invoked, so I guessed that these warnings had something to do with that.
If you need any specific information about the my app to continue your debugging, I'll be happy to help.

[talsec-app]

Hi @ShadyZekry , the issue will be solved in the upcoming freeRASP release. Thanks for giving your time to help our cause.

[talsec-app]

Hello.
We have just released new version of freeRASP 2.0.0. This version fixes this issue. We recommend you to update to this new version.
Talsec Team

[realTristan]

this is happening to me too, did you find a solution?

[ShadyZekry]

Not yet, @realTristan .
I wanted to deploy my application fast, so I skipped the RASP part from my app.

[talsec-app]

This issue was caused by a deprecated API in one of hook detection checks. It shouldn't impact your app run whatsoever. But it is a bug, and we will provide a patch in the upcoming release.

[talsec-app]

This seems to be a separate issue. How do you test your callbacks? You can find tips in this issue: #3

[yakim333]

Hi @ShadyZekry

My main concern is that the callbacks is not being invoked, so I guessed that these warnings had something to do with that. > If you need any specific information about the my app to continue your debugging, I'll be happy to help.

Just would like to check if issue: #3 suggestions helped you to verify the problem. Please let me know if you can proceed with freeRASP or any other issue is blocking you.

Regards,
Sergiy Yakymchuk
Talsec co-founder

[ShadyZekry]

Sorry I was busy in the last 3 days, @yakim333 @talsec-app

So, I was not following this issue to test the package to be honest. What I have tried to do is trying different changes to the app to test these lines of code which i found on the README:

    // Talsec config
    TalsecConfig config = TalsecConfig(
      androidConfig: AndroidConfig(
        expectedPackageName: dotenv.env["EXPECTED_PACKAGE_NAME"]!,
        expectedSigningCertificateHash: dotenv.env["EXPECTED_SIGNING_HASH"]!,
      ),

      watcherMail: '[email protected]',
    );

    // Callback setup
    TalsecCallback callback = TalsecCallback(
      onDebuggerDetected: () => print("Debugger detected"),

      // For Android
      androidCallback: AndroidCallback(
        onRootDetected: () => print('Root detected'),
        onEmulatorDetected: () => print('Emulator detected'),
        onHookDetected: () => print('Hook detected'),
        onTamperDetected: () => print('Tamper detected'),
        onDeviceBindingDetected: () => print('Device binding detected'),
        onUntrustedInstallationDetected: () => print('Untrusted installation detected'),
      ),
  }

These lines were added to initstate at the start of my app, after adding all the android configurations mentioned in the README ofcourse.

I did try these to test the app over multiple devices:

• Run the app on debugger.
• Run on a rooted device.
• Run on Emulator.
• Change my EXPECTED_PACKAGE_NAME in my .env file.
• Change my EXPECTED_SIGNING_HASH in my .env file.
• Install the app .apk as an untrused installation.

And sadly not a single callback is called, and I keep getting these lines in the logs as I mentioned before.

I/System  (24218): Opening DexFile: /data/app/com.test.project.dev-LGO3HZxe32u2d8rLunK-_A==/base.apk
W/est.project.de(24218): Opening an oat file without a class loader. Are you using the deprecated DexFile APIs?
W/System  (24218): A resource failed to call close.