Support #11279
[SCP ID :##5574##] : Looping during device pairing
| Status: | Closed - End of life cycle | Start date: | October 23, 2020 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | October 30, 2020 | |
| Assignee: |  Nurul Athira Abdul Rahim | % Done: | 100% | |
| Category: | Technical | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:-
Issue found in Android version 4.4 where cust unable to do device pairing even after set passcode.
History
#1
Updated by Nurul Athira Abdul Rahim almost 4 years ago
- Assignee changed from Nurul Athira Abdul Rahim to Darren Gee Teik Aun
#2
Updated by Nurul Athira Abdul Rahim almost 4 years ago
- upon investigation, this bug only happens on android 4.4 devices
- however due to the latest security standard from our latest pentest by deloitte, we will
update our encryption method to RSA/ECB/OAEPPadding which requires android 6.0
- also, starting Novmber 2, 2020 (https://support.google.com/googleplay/android-developer/answer/113469#targetsdk),
Google Play Store require a targetted version of Android 10,
and to support that, our codebase must update all android dependency to androidx libraries which greatly affect
all Android version below Android 5.0
- For the above reasons, Penril recommends for the next play store deployment, the minimum
support should be Android 6.0 and above
#3
Updated by Norhaidah Md Dasuki almost 4 years ago
- Category set to Bug
#4
Updated by Nurul Athira Abdul Rahim almost 4 years ago
Request meeting with JTM and Pentester. Waiting meeting date from Rahmat Aris.
#5
Updated by Nurul Athira Abdul Rahim almost 4 years ago
From pentest result, they suggest :
Update the Android application to disable support for Android versions below 8.0 to ensure that the devices running the application can be updated with security patches against known vulnerabilities.
Need confirmation from BSN about this issue.
#6
Updated by Norhaidah Md Dasuki almost 4 years ago
- Due date set to October 30, 2020
- Category changed from Bug to Technical
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- Start date changed from September 30, 2020 to October 23, 2020
#7
Updated by Nurul Athira Abdul Rahim almost 4 years ago
Hi Darren,
As discussed with BSN, they agreed to go with minimum ver 6.0.
You can start the development.
#8
Updated by Darren Gee Teik Aun almost 4 years ago
- Assignee changed from Darren Gee Teik Aun to Nurul Athira Abdul Rahim
- % Done changed from 0 to 90
implemented on force update/android 10 and pentest build (v1.6.4 and v1.6.5)
v1.6.4 SIT SIT https://drive.google.com/file/d/1R5Sn_kWj9yupHwcKSOMUOoD4rd6uJNGm/view?usp=sharing (pentest)
v1.6.5 SIT https://drive.google.com/file/d/1792TkwhEwFHm06XkwRuEaKeDkFR4vBPk/view?usp=sharing (force-update)
#9
Updated by Darren Gee Teik Aun almost 4 years ago
- Status changed from Development / Work In Progress to Internal Testing
#10
Updated by Nurul Athira Abdul Rahim almost 4 years ago
- File Looping during device pairing_6.0_11279.docx added
- Status changed from Internal Testing to System Integration Test
- % Done changed from 90 to 100
Tested and passed on emulator and physical phone. Refer attachment.
#11
Updated by Nurul Athira Abdul Rahim almost 4 years ago
- Status changed from System Integration Test to Pending Prod Deployment
- Assignee changed from Nurul Athira Abdul Rahim to Darren Gee Teik Aun
Hi Darren, please prepare for pre production deployment. Target to deploy on 21/12/20.
Thank you.
#12
Updated by Nurul Athira Abdul Rahim over 3 years ago
- Status changed from Pending Prod Deployment to Closed - End of life cycle
- Assignee changed from Darren Gee Teik Aun to Nurul Athira Abdul Rahim
Deployed to production on 23/12/20
Migration ID0027