https://github.com/zebradevs/a13_ba_ssm

Exercising Boot Aware features and SSM
https://github.com/zebradevs/a13_ba_ssm

Last synced: about 1 year ago
JSON representation

Exercising Boot Aware features and SSM

• Host: GitHub
• URL: https://github.com/zebradevs/a13_ba_ssm
• Owner: ZebraDevs
• License: mit
• Created: 2023-04-03T22:16:42.000Z (about 3 years ago)
• Default Branch: master
• Last Pushed: 2023-04-03T22:24:46.000Z (about 3 years ago)
• Last Synced: 2025-02-10T08:51:23.206Z (over 1 year ago)
• Language: Java
• Size: 5.03 MB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# A13_DIRECTBOOT_MODE

## com.ndzl.targetelevator

TESTING

- A BOOT-AWARE APP WITH FBE FILESYSTEM IN A13

- DATAWEDGE INTENT DELIVER TO BACKGROUND AND FOREGROUND SERVICE 

## PURPOSE OF THIS APP IS SHOWING WHAT SCREEN LOCK MODE IS TRIGGERING THE CREDENTIAL ENCRYPTED STORAGE PROTECTION.

SCREEN LOCK MODES ARE

![image](https://user-images.githubusercontent.com/11386676/222977690-7414560a-5eca-484d-a048-0542781671a1.png)

ON A TC58 BSP 13-08-07 IT TURNS OUT THAT

- WITH **NONE, SWIPE, PATTERN** A BOOT-AWARE APP IS ABLE TO ACCESS BOTH THE DPS (DEVICE PROTECTED STORAGE) AND THE CES (CREDENTIAL ENCRYPTED STORAGE) BEFORE THE FIRST UNLOCK AFTER REBOOT

- WITH **PIN AND PASSWORD** A BOOT-AWARE APP *IS* ABLE TO ACCESS DPS WHILE IT *CANNOT* ACCESS CES BEFORE THE FIRST UNLOCK AFTER REBOOT

Here is a screenshot from the app. Where you spot an exception under the DPS section, that is failed attempt to access CES after boot. It was logged under DPS since that context is always available.

![image](https://user-images.githubusercontent.com/11386676/222977925-ca15cd47-b55b-41db-a0e7-2e550eb67dc4.png)

A11 ASKING THE USER ABOUT THE SECURE START-UP SETUP, it was not mandatory yet

No such option is available on A13. Secure start-up is always enabled with PIN or Password screen lock

![image](https://user-images.githubusercontent.com/11386676/223754949-4c1727da-fc80-4f2e-a74b-33d1a043cb0b.png)

## DATAWEDGE AND INTENTS DELIVERY

- IN A13 NO METHOD WORKS BUT BROADCAST DELIVERY

- IN A13 BOTH STARTSERVICE AND STARTFOREGROUNDSERVICE FAIL WITH MESSAGE "Unable to start service Intent { act=com.ndzl.DW cat=[android.intent.category.DEFAULT] cmp=com.ndzl.targetelevator/.DW_FGS (has extras) } U=0: not found"

- IN A11 ALL THREE METHODS WORK