You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this was for a joke, I can accept it. Below are the issues the function defined in main.py line 1091 character 0 is non-required and is non-safe. Please note that these are predicted errors from a thorough examination of the code.
In my expectations, the following code will and should not work, as trying to delete all files recursively will cause a crash of the command execution process, as it will overhaul in terms of memory.
Trying to delete System32, a protected folder, recursively, will decline in access to bulk deletion. Deleting a protected operating-system folder through only administrator permissions, will fail. Although going around this problem and creating an elevated NT AUTHORITY\SYSTEM process using a third-party Python toolkit will allow some files to delete, is just unsecure.
This function is not-needed. It is not certain how much damage this function/command may perform with only admin perms.
The same is for the function bsod. I can guarantee that the bsod function//command will and should work as expected, however it is simply not-required. Who will ever run a BSOD? What did you expect? A more "traditional way" to reboot? No.
The text was updated successfully, but these errors were encountered:
If this was for a joke, I can accept it. Below are the issues the function defined in
main.py
line 1091 character 0 is non-required and is non-safe. Please note that these are predicted errors from a thorough examination of the code.System32
, a protected folder, recursively, will decline in access to bulk deletion. Deleting a protected operating-system folder through only administrator permissions, will fail. Although going around this problem and creating an elevatedNT AUTHORITY\SYSTEM
process using a third-party Python toolkit will allow some files to delete, is just unsecure.bsod
. I can guarantee that thebsod
function//command will and should work as expected, however it is simply not-required. Who will ever run a BSOD? What did you expect? A more "traditional way" to reboot? No.The text was updated successfully, but these errors were encountered: