- May 29, 2018
- 2,728
@danb have you removed nag screen from free version of voodooshield? Last time i tried it i did not get it at all, if so why?
Hello Danb ,sorry for the mixup ,I have the free version .Thks for the help .Hi, just to make sure, are you clicking the Save & Close button at the bottom right after making changes to settings?
If that is not the issue, please send your C:\ProgramData\VoodooShield\DeveloperLog.log to support at voodooshield.com.
Also, I am aware of the other bug you are talking about, it should be a simple fix, thank you!
Well, the Friday nag screen did not increase sales on Friday, and actually sales on Friday are much lower than every other day of the week, hehehe. It was just upsetting people, so I removed it. The prompt that you see when you click on VoodooShield Settings pretty much has to stay because it lets the user know why the settings are greyed out.@danb have you removed nag screen from free version of voodooshield? Last time i tried it i did not get it at all, if so why?
That makes sense... hopefully we can do a giveaway soon and everyone will have a license again.Hello Danb ,sorry for the mixup ,I have the free version .Thks for the help .
Thank you Andy! VS actually uses a string metric known as Levenshtein Distance to compare command lines. So I am guessing that after you manually allowed the first command line, VS auto allowed the modified command line because the Levenshtein Distance was within spec.Maybe there is no need to change the info from the previous post. Using the space before dot somehow bypassed the command-line checking. Running the file "ping .png" is not blocked by command-line alert like in the case of "ping.png":
View attachment 243971
So you can simply include this trick in your command-line blocking.
How did you contact me about IDM? Please let me know so I can see where that issue stands.I'm glad you made that remark about getting on the same page regarding issues surrounding V.S but what you're asking of him is just, but what about the issues i ask you about where V.S blocks internet download manager when where a download has completed with I.D.M and i proceed to open download folders with i.d.m v.s blocks it, you never fixed or replied to me about it. Next v.s also blocks windows defender related stuff and windows related stuff which is important to the operating system i find this crippling for new people and time consuming for advance users.
IT just isn't right and I love this software.
How did you contact me about IDM? Please let me know so I can see where that issue stands.
In default settings, VS should not block anything related to Windows or Windows Updates. I run VS with default settings on 3 different Windows 10 computers and monitor the blocks very closely and have not experienced this issue for a very a long time. If you are having an odd Windows block, it is probably due to a custom setting, such as Custom Folders configuration, or a rule, or some odd combination. Since there are millions + of possible combinations for settings, it is not possible for me to test them all.
Well, I tried all 3 ways (full path, with space (in same folder), without space (in same folder)) and I got 3 command line blocks, so it seems to be working correctly for me. Here are the files I used to test (the full path one is the same as the one with the space... I just moved it to the C drive).@danb,
It is not a big deal for VoodooShield, because only the command-line checking is bypassed, and the executable is still blocked. Only an inexperienced user can be fooled by allowing the alert. So, there is a trick:
If you will use the full path to ping .PNG (like c:\z\ping. png) then this will be blocked correctly as a command-line.
- Create the shortcut and use the command-line below (remember about the space before the dot):
cmd /c "ping .PNG"- Rename the EXE file to ping .PNG
- Put the shortcut and the ping .PNG into the same folder and run the shortcut.
If I use ping .txt instead of ping .png, then it is also blocked as command-line.
It seems that the extension .png is somewhat special because I tried several extensions (.txt, .abc, .jpg, etc.) and all were blocked by command-line.
Oh, I remember now, thank you. In our conversation, I said "If you are not running the 5.64 beta, please let me know how it does with IDM... there is a chance that it is fixed in this version."
If our conversation did not continue beyond that, then I assumed the issue was fixed. These download managers are difficult to get just right (and truly secure at the same time)... for a lot of reasons.
Do you run VS with any setting that is not default?
I will have to look at the entire conversation to know for sure. But just keep in mind that if an app runs executables from AppData (or some other favorite malware hiding spot), and has a barrage of random command lines, is not signed, and has 20 other attributes that are indistinguishable from malware, then that app is simply not going to work with VS without blocks, and the reason why is because there is no possible way to get it to work safely with VS, without creating a vulnerability in VS. Download managers are the only "legitimate" apps that I have seen pull stuff like this. If it is possible for me to get them to work with VS, then I bend over backwards trying to do so, unless it means we have to create a vulnerability to get it to work.I ran it in autopilot first for 3 months then always on. Next i have long updated since and still get random blocks and no the conversation didn't end there, that was the beginning.
I will have to look at the entire conversation to know for sure. But just keep in mind that if an app runs executables from AppData (or some other favorite malware hiding spot), and has a barrage of random command lines, is not signed, and has 20 other attributes that are indistinguishable from malware, then that app is simply not going to work with VS without blocks, and the reason why is because there is no possible way to get it to work safely with VS, without creating a vulnerability in VS. Download managers are the only "legitimate" apps that I have seen pull stuff like this. If it is possible for me to get them to work with VS, then I bend over backwards trying to do so, unless it means we have to create a vulnerability to get it to work.
Have you tried to create a rule?