AM Debug v2.7.0 Run#1318
Revert "TB Optimize importing backups by eliminating the need for cache"
This reverts commit 5e97823b
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Revert "TB Optimize importing backups by eliminating the need for cache"
This reverts commit 5e97823b
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
App Manager | DEBUG pinned «Note that import-export functionality is by no means perfect as there were limitations on how tests could be performed. This is specially true for TB backups (some backups may fail). So, test the feature very carefully and don’t delete your existing OAB or…»
AM Debug v2.7.0 Run#1319
TB Optimize importing backups by eliminating the need for cache
This time TarArchiveEntry is not directly used.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
TB Optimize importing backups by eliminating the need for cache
This time TarArchiveEntry is not directly used.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1320
Refactor Add backward compatibility for ADB over TCP
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Add backward compatibility for ADB over TCP
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.6.2 Run#1321
Refactor Add backward compatibility for ADB over TCP
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Add backward compatibility for ADB over TCP
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1322
Backup Fix relative path issue
Java File API often fails to handle the relative files properly. As a result,
some backups have the wrong relative paths. To solve the issue, a custom
method is used with a number of tests.
The issue appears to be present only in v2.6.1. However, no backward
compatibility has been provided with this patch.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Backup Fix relative path issue
Java File API often fails to handle the relative files properly. As a result,
some backups have the wrong relative paths. To solve the issue, a custom
method is used with a number of tests.
The issue appears to be present only in v2.6.1. However, no backward
compatibility has been provided with this patch.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1323
Refactor Fix returning the wrong manifest if the APK has multiple manifests
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix returning the wrong manifest if the APK has multiple manifests
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.6.2 Run#1324
Refactor Fix returning the wrong manifest if the APK has multiple manifests
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Refactor Fix returning the wrong manifest if the APK has multiple manifests
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1325
Merge remote-tracking branch 'weblate/master'
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Merge remote-tracking branch 'weblate/master'
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1326
Init cipher with a PRNG
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Init cipher with a PRNG
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
AM Debug v2.7.0 Run#1327
KeyStore Encrypt data using Cipher itself instead of using CipherOutputStream
Android KeyStore in older Android versions did not reset IV correctly.
As a result, when close was called on CipherOutputStream, it threw an
IllegalStateException saying that "IV has already been used. Reusing IV in
encryption mode violates security best practices." which was not correct.
This patch attempts to fix the issue by avoiding the use of CipherOutputStream
altogether.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
KeyStore Encrypt data using Cipher itself instead of using CipherOutputStream
Android KeyStore in older Android versions did not reset IV correctly.
As a result, when close was called on CipherOutputStream, it threw an
IllegalStateException saying that "IV has already been used. Reusing IV in
encryption mode violates security best practices." which was not correct.
This patch attempts to fix the issue by avoiding the use of CipherOutputStream
altogether.
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>