Remove Selinux Prop spoofing

[DanGLES3]

I'd suggest either removing this line of code or have it set the property to 1 (which shouldn't be problematic as it's present on some stock ROMs) so it doesn't alarm detection systems and doesn't cause property deletion detection

[osm0sis]

Resolved in upstream PIFork scripts with a user option:
osm0sis@cd32f0c

For more context:
osm0sis#19

[Fede2782]

This should be applied in any case as it breaks Samsung Selinux information. The property should not exist on non-One UI while it has to be 1 when in One UI.

[osm0sis]

Back in the MagiskHide days topjohnwu found that it was also set to 0 on some stock ROMs with SELinux enforcing. So both 0 or 1 could mean SELinux was enabled in the build, depending on the ROM, which is why he just chose to delete it.

Some further context and debate throughout this USNF PR thread: kdrag0n/safetynet-fix#166 (comment)

[b0l5]

I can't pass attestation, so I must remove this file: ro.build.selinux?

[ScottRFrost]

I can't pass attestation, so I must remove this file: ro.build.selinux?

Where is the file located?

[b0l5]

I can't pass attestation, so I must remove this file: ro.build.selinux?

Where is the file located?

I don't know.

[OpM3TA]

I can't pass attestation, so I must remove this file: ro.build.selinux?

Where is the file located?

I don't know.

It's not a file lol it's a build property