Results for "Author: braden"
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :) Also, please be aware that this code will ONLY work on Win98 or Win98SE.
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :)
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :) Also, please be aware that this code will ONLY work on Win98 or Win98SE.
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :) Also, please be aware that this code will ONLY work on Win98 or Win98SE.
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :) Also, please be aware that this code will ONLY work on Win98 or Win98SE.
Updated! Denies access to any specified folder. It will close ALL objects that contain the name of folder to secure, and it's parent object, if it's scanning aggressively. I've seen other code attempting to do the same thing here but nothing that is as aggressive as this is. Fully commented! UPDATED! Fix security holes when editing the registry. When the engine is running, If the controller did not initiate the changes to the password or folder name, then the engine will ignore them and fix the registry entries. This defeats the so called "secure folder nuker" posted here on PSC. Only known way to defeat it (with engine running and scanning aggressively) is to rename the folder in a DOS box. If anyone knows how to stop this, or finds other security holes, PLEASE LET ME KNOW!!! :) Also, please be aware that this code will ONLY work on Win98 or Win98SE.