Activity for WinFire
-
WinFire released /WinFire v3.23.rar
-
-
Andrew modified a comment on discussion General Discussion
v3.21 "Install_WinFire.bat" - Added Auto prompt ELEVATE cmd and Grant Users modify permission on the WinFire folder. Can now extract WinFire to any place, run Install and it 'should' work. "WinFire.bat" - Added a check to see if files are already in the temp list, and not relist if found. . Anyone find any issues or have any suggestions?
-
v3.21 "Install_WinFire.bat" - Added Auto prompt ELEVATE cmd and Grant Users modify permission on the WinFire folder. Can now extract WinFire to any place, run Install and it 'should' work. "WinFire.bat" - Added a check to see if files are already in the temp list, and not relist if found. Anyone find any issues or have any suggestions?
-
v3.21 "Install_WinFire.bat" added Auto prompt ELEVATE cmd and Grant Users modify permission on the WinFire folder. Can now extract WinFire to any place, run Install and it 'should' work. Added a check to see if files are alreay in the temp list, and not relist if found. Anyone find any issues or have any suggestions?
-
v3.21 "Install_WinFire.bat" added Auto prompt ELEVATE cmd and Grant Users modify permission on the WinFire folder. Can now extract WinFire to any place, run Install and it 'should' work. Added a check to see if files are alreay in the temp list, and not relist if found. Anyone find any issues or have any suggestions?
-
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. Actually 'they don't NEED to, they could create the shortcut manually. But then they'd actually have to manually make the vbs too first. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is...
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. Actually 'they don't NEED to, they could create the shortcut manually. But then they'd actually have to manually make the vbs too first. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is...
-
Will be trying Powershell in the near future to overcome the 8191 character limit (not an issue if your blocking a few folders containing millions of files) Edit: I found a basic way to send all arguments (paths) to a text file for the batch to loop through. Instead of a complete rewrite using Poweshell with a cmd shell method for rule creation or some native Poweshell implementation I'm sticking with tried and tested CMD line.
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. Actually 'they don't NEED to, they could create the shortcut manually. But then they'd actually have to manually make the vbs too first. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is...
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. Actually 'they don't NEED to, they could create the shortcut manually. But then they'd actually have to manually make the vbs too first. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is...
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. Actually 'they don't NEED to, they could create the shortcut manually. But then they'd actually have to manually make the vbs too first. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is...
-
Simply going to notify user in Install_Winfire.bat that they need to manually run as admin to add shortcut. It's a one off. There will also be notification about requirement to allow write access to folder permission of WinFire if it's in a folder like Program Files. Not going to force hack anything with that. Only reason WinFire requests elevation in function is to allow rule creation. Need to add a check while writing temp text files to ensure lines (paths) aren't already defined. Mostly if multiple...
-
Forgot to change the version from 3.14 BETA to 3.20. Issue is if you install WinFire into Program Files or other protected folder, the VBS will fail because it does not have the permission to write in that location. Installing to HOMEDRIVE\WinFire works. To allow WinFire to work in Program Files: 1. Right-Click the WinFire folder and select 'Properties' 2. Click the 'Security' tab, scroll downand select 'Users (name\users)', click 'Edit' 3. Tick 'Full control' box under 'Allow' 4. Apply, OK and OK....
-
Forgot to change the version from 3.14 BETA to 3.20. Issue is if you install WinFire into Program Files or other protected folder, the VBS will fail because it does not have the permission to write in that location. Installing to HOMEDRIVE\WinFire works.
-
v3.20 now includes an Install File. Simply extract anywhere and run the install file. The install file dynamically writes a VBS file that is used to write all arguments to text file. The VBS launches WinFire.bat which asks for Elevation. WinFire.bat then uses the text file in for loops to create a dir.txt and file.txt. Those files are used to make the rules :) 8191 limit overcome :)
-
v3.20 now includes an Install File. Simply extract anywhere and run the install file. The install file dynamically writes a VBS file that is used to write all arguments to text file. The VSB launches WinFire.bat which asks for Elevation. WinFire.bat then uses the text file in for loops to create a dir.txt and file.txt. Those files are used to make the rules :) 8191 limit overcome :)
-
-
Will be trying Powershell in the near future to overcome the 8191 character limit (not an issue if your blocking a few folders containing millions of files)
-
Just doing some tests on large set of files. Ran into limitation as 8,191 characters is maximum for CMD can accept on Windows 10. So maybe around 100 to 150 files/folders depending on path and filename lengths. https://support.microsoft.com/en-au/help/830473/command-prompt-cmd-exe-command-line-string-limitation Just fixed the SetLocal situation for checking shortcuts and file count in v3.13
-
-
Just doing some tests on large set of files. Ran into limitation as 8,191 characters is maximum for CMD can accept on Windows 10. So maybe around 100 to 150 files/folders depending on path and filename lengths. Just fixed the SetLocal situation for checking shortcuts and file count in v3.13
-
-
-
-
v3.10 uploaded as RAR file. Needs to be extracted to Program Files manually. And WinFire.bat run manually. When adding it to a self-extracting archieve, Avast was detecting it as "Win32:Evo-gen [Susp]" most likely because of the elevation code and the fact the SFX was set to execute the batch file. So just review it yourself with a text editor and run it if you want. Update: Found that Avast only flagged as evo-gen when SFX was created with an SFX Icon. Found this... https://forum.avast.com/index.php?topic=142243.0...
-
v3.10 uploaded as RAR file. Needs to be extracted to Program Files manually. And WinFire.bat run manually. When adding it to a self-extracting archieve, Avast was detecting it as "Win32:Evo-gen [Susp]" most likely because of the elevation code and the fact the SFX was set to execute the batch file. So just review it yourself with a text editor and run it if you want. Update: Found that Avast only flagged as evo-gen when SFX was created with an SFX Icon. Found this... https://forum.avast.com/index.php?topic=142243.0...
-
-
v3.10 uploaded as RAR file. Needs to be extracted to Program Files manually. And WinFire.bat run manually. When adding it to a self-extracting archieve, Avast was detecting it as "Win32:Evo-gen [Susp]" most likely because of the elevation code and the fact the SFX was set to execute the batch file. So just review it yourself with a text editor and run it if you want.
-
-
WinFire v3.10 will no longer requests to sit within %HOMEDRIVE% (C:\WinFire), and will ask to be installed to Program Files using (%PROGRAMFILES%). Since the CMD exe on a 64bit OS runs as 64bit but can use 32bit commands, it will house correctly within "Program Files" either on a 32bit or 64bit OS. It is possible in the future to install to any directory, but for now it'll be "Program Files/WinFire/"
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch file/s used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch/s file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file...
-
It's important to state something right now. My previous batch file used a cmd line exe utility 'elevate.exe' either 32 or 64bit varients included in "elevate-1.3.0-redist.7z" downloadable from "http://code.kliu.org/misc/elevate/" dated 5-Mar-2011. That utility and my script/s where NOT MALWARE in any form. Yes, elevate.exe could've been used maliciously and I will allow sourceforge.net that credit. Now that I found, edited and provide a direct way for users to elevate the CMD prompt batch file with...
-
-
Winfire v3.10 is almost complete. It's turned into a beast of a CMD line batch script. Elevating with paremeters carried over by from local permission launched CMD. It now displays all files, folders (searches for dll and exe files) and all files directed by shortcut and files found within shortcuts to folders (searches for dll and exe files). It displays them all in a clear format before more possibilities. Default tag for block, clr or del option to clear all existing rules, open file location...
-
Working on verison 3.00. Why jump to v3.00 now? Big change... Will use SendTo shortcut to a single batch file that will allow blocking multiple files or/and files within folders at once (working on FORFILES command to process any hidden files). Dropping WinFire options on the right-click main menu. May add the shortcut to "Windows Defender Firewall with Advanced Security" for files and folders, but it will need to be manually added. Most likely will drop the clear rules options. It is simple enough...
-
Working on verison 3.00. Why jump to v3.00 now? Big change... Will use SendTo shortcut to a single batch file that will allow blocking multiple files or folders at once (but not a mix of files and folders combined). Dropping WinFire options on the right-click main menu. May add the shortcut to "Windows Defender Firewall with Advanced Security" for files and folders, but it will need to be manually added. Most likely will drop the clear rules options. It is simple enough to sort and delete manually...
-
v2.0 dropped elevate utility. Batch files now ask for elevation themselves.
-
-
The so called Malware is "elevate-1.3.0-redist.7z". WinFire needs Admin rights to get the job done. Elevate makes that easy. It will not harm your system. http://code.kliu.org/misc/elevate/ 1.30 of elevate was released in 2011, I've not had a single problem with it. It is not Malware.
-
-
-
1
