ArrowOS Topics!Hello everyone, its been a long time since i took a break. okay, maybe this time i want to talk about the future of this project, seeing that some device communities like this project, so i want to discuss something, and none other than... device integrity.
You must have known that next year Google will change the integrity mechanism, especially on devices running on Android 13 and above, and it will be more complicated and complex in the future, but... before that happens, i think about it considering that this project is intended for long-term use, so if the integrity of this project is not right, how can that goal be achieved.. right?
thats why i thought of giving users an option for a while before Google changes its integrity mechanism completely next year, please select the option below for the integrity system:
Option 1: stuck in MEET_DEVICE integrity but using the AOSP keybox where the bootloader is locked by spoof and it is needed by several applications. this is a safe path considering that the justification that will be done is only in the fingerprint section later. This path produces less than optimal results but is more durable than Option 2.
Option 2: MEET_STRONG integrity and using a keybox that has been leaked to the public. in my opinion, this is a vulnerable path considering that Google always patrols keyboxes and fingerprints, this path does produce good results but does not last long.
Vote via the poll below this message later, while i brew tea/coffee to see your criticism and suggestions before i return xD.
signed,
@iverzasterix
