Skip to content
This repository has been archived by the owner on Jan 18, 2025. It is now read-only.

Commit

Permalink
blu
Browse files Browse the repository at this point in the history
  • Loading branch information
s0urce-c0de authored Dec 9, 2024
1 parent fe9e424 commit 676f63c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ Admins may want to prevent user enrollment to better control their devices. This
By navigating to **Devices > Chrome > Settings > Users & browsers** and then looking for the **Enrollment permissions** tab, admins can set the polcy to **Do not allow users in this organization to enroll new or re-enroll existing devices** to disable user enrollment.

> [!WARNING]
> **THIS HAS ONLY BEEN PARTIALLY TESTED:** It may be possible on unenrolled Chromebooks with developer mode enabled to run `vpdi RW_VPD -s check_enrollment=1` in VT2 to bypass policy and re-enroll. An exploit kit named Rigtoolsv2 also claims to have functionality called `Riienrollment`, which can also bypass enrollment policy set in the admin console.
> **THIS HAS ONLY BEEN PARTIALLY TESTED:** It may be possible on unenrolled Chromebooks with developer mode enabled to run `vpd -i RW_VPD -s check_enrollment=1` in VT2 to bypass policy and re-enroll. An exploit kit named Rigtoolsv2 also claims to have functionality called `Riienrollment`, which can also bypass enrollment policy set in the admin console.
## sh1mmer
sh1mmer is an exploit that takes advantage of how factory shims are verified for the device. By only checking the kernel signature, it was possible to modify the normal shim image to allow users to manipulate the device.
Expand Down

0 comments on commit 676f63c

Please sign in to comment.