Jump to content

AstroSkipper

Member
  • Posts

    4,587
  • Joined

  • Days Won

    545
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by AstroSkipper

  1. Here is the answer: Batch files themselves are less problematic than compiled executables from batch files, especially with hidden windows.
  2. Anyway, all Windows XP compatible AV engines on VirusTotal do not generate false positive reports anymore! And, nearly all established and well-known AV scanners, too! Except Kaspersky, but I never trusted this company in the past, and will never trust it again in terms of security for good and well-known reasons.
  3. Good question! I am the creator, and I really don't know why! But it can be taken as a good test for insensitivity to the "space bug".
  4. And here is an example of reducing false positives by AV scanners. It's the file Configure PopMenu.exe: Old results uploaded by @Dave-H: Now my new results after all measures: 19 false positive messages have been reduced to a value of 10.
  5. Hello to all again! The work is almost done. I tested deeply my program package, and what can I say? It's working perfectly without any issues as far as I can see. False positive reports by the etablished and well-known AV scanners have been reduced. I am thrilled! Currently, I am updating the documentation in regards to the changelog. And, there were a lot of changes! And now, a special information to my core beta testers, @Dave-H, @mina7601, and @NotHereToPlayGames! When my package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 has been released, download it and, please, remove the old installation completely! Do all from scratch! Due to the changes, a simple replacing of files is neither good nor recommended. It could lead to error messages. Too much changes have been done! Furthermore, Microsoft .NET Framework 4.0 is now needed to run my program package. And now the most important thing! I think the release of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 will be tomorrow. Cheers, AstroSkipper
  6. I do hope so, too! Unfortunately, it's a lot of work. Changing code leads to the need of changing other code, and so on. I modified and cleaned up nearly all self-created programs. And I found bugs which apparently did not occur during the beta test.
  7. Hello to all! Although my program package eventually passed the beta test, I still had to make significant changes due to false positives of several AV scanners: All unnecessarily embedded files have been removed from my self-created executables. Changes in calling up other programs. In all my affected programs, protection against code injection has been improved. This leads to preventing of future "space bugs", too! Different issues which could have been noticed only in very rare cases, have been fixed. All unnecessary code has been removed. New bugs I additionally found have been fixed. Autostart entries of PopMenu and the new Min2Tray, automatically added to the registry by my configuration program, have been fixed in regards to the "space bug". All message windows of my programs have been resized and adjusted for a better visibility. All my self-created program files have been recompiled by using a different compiler. All these measures have led to a reduction in the number of false positives reported by AV scanners. Now I am testing deeply my program package from scratch. Cheers, AstroSkipper
  8. Hello @George King! That was the very first action I did! I removed unnecessarily embedded files from all self-created programs. But anyway, thanks for the hint!
  9. I totally agree! All files self-compiled from batch sources are considered to be intrinsically vulnerable by AV scanners. Of course! But these files aren't more or less liked by AV scanners than my other ones. Hope dies last!
  10. Using a different compiler I could reduce the false positives of OpenLANSet.exe from 19 to 15. No false positives from Avast and Malwarebytes anymore!
  11. A few code changes, and the results are different! Unfortunately, opening and closing of the IE Proxy Settings easily is a wanted function. If I left it out, these two programs would be senseless.
  12. Ok, thanks for your opinion! I'll try to reduce these false positives as much as I can. Important for me are only established, well-known AV scanners, the big players in this business.
  13. Sorry, you're righr! Confgure PopMenu.exe, of course! Too much proxy in my head! I already know these results, and that wasn't the problem, either. I am interested in your opinion about these results.
  14. Thanks again for your tests and observations! Now you may understand what I mean. It's very strange and gets stranger if I modify code or use another compiler. A little change of a code snippet, and my Avast doesn't trigger a warning, and so on. I hate that! Please, try to scan StartProxy.exe, Confgure PopMenu.exe and SetupMin2Tray.exe on VirusTotal! What do you think about the results?
  15. I forgot to mention that I referred to compilers which convert batch files to executables. I believe that the real problem lies in code snippets that are often used by script kiddies or hobby hackers. If this code appears in clean programs, then some AV scanners generate these false positives. Any further ideas? And, after some tests using different compilers, it also seems to depend on the compiler itself. Converted files by a frequently used compiler trigger more false positives than those by a less used one. That was kind of to be expected and makes sense!
  16. Thanks for your observation! It's all a bit strange. You said Malwarebytes premium didn't trigger any warnings for you, but the Malwarebytes online scanner on VirusTotal does! Check, for example, the file StartProxy.exe, and you'll see what I mean!
  17. I forgot to mention that I referred to compilers which convert batch files to executables. I believe that the real problem lies in code snippets that are often used by script kiddies or hobby hackers. If this code appears in clean programs, then some AV scanners generate these false positives. Any further ideas?
  18. Just a short feedback! I tried different compilers, but with moderate success. Some of my compiled program files are repeatedly classified as malware by various AV scanners, although they are absolutely clean, of course. I tried several variations of my programs' source codes. I am a little perplexed at the moment. Presumably, these false positives are caused by the misuse of these compilers by script kiddies or other hobby hackers. Actually, I would like to reduce these false positives from the established AV scanners. Any advice or tip is welcome! Cheers, AstroSkipper
  19. Not really, but it is simply the truth! And, as you know, I really mean what I write.
  20. @mina7601! I hope you feel better already or soon! Enjoy your life and do beautiful things that bring you joy. There are two worlds, the virtual and the real. If I had to choose, I would always choose the latter. And don't forget, you are needed in both worlds! But real life is only possible in the real world! Cheers, AstroSkipper
  21. Up-voting implies the agreement with the content of a post. Liking just means you like this post and its content. Neither of these possibilities applied in your case.
  22. Right! Or, even worse, one might think that I like the fact that you're not doing so well right now. And that would be completely absurd, of course!
  23. Did you really try the version Firemin Portable 6.3.1.5105? I don't think so. It works like a charme on Windows Professional XP 32bit SP3 (fully POSReady updated). I didn't mean the installer version. If the portable version doesn't run in your system, then your partition is faulty or something is missing, unfortunately. BTW: When I state facts, I definitely mean what I wrote. And that literally! I assume you meant "That version doesn't work in my system", otherwise your statement would be definitely wrong And, just to clarify it! There are several programs whose installer version doesn't run under Windows XP 32bit, but its portable vesion does, and vice versa! Cheers, AstroSkipper
  24. @mina7601! Same here! I would have "liked" or "up-voted" your post to show that I care about you, but one can't, and one shouldn't give a ike or an up-vote to this, either. That would be strange and misleading! Today's young generation, newfangledly called digital natives, have grown up with smartphones, tablets and computers. A healthy doubt about this development is essential and desirable. I only use social media when I need them for communication. But, the communication in this forum also has to be reflected, and you must not lose yourself here. It's not the real life, and a lot of information here, and everywhere else, is deceptive, poorly researched, often inappropriate, or even misleading! Anyway, wish you all the best, switch off sometimes or more, enjoy your life, you are still young! There is a lot to experience outside! Greetings from Germany, AstroSkipper
  25. Did you really try the version Firemin Portable 6.3.1.5105? I don't think so. It works like a charme on Windows Professional XP 32bit SP3 (fully POSReady updated). I didn't mean the installer version. If the portable version doesn't run in your system, then your partition is faulty or something is missing, unfortunately. BTW: When I state facts, I definitely mean what I wrote. And that literally! I assume you meant actually "That version doesn't work in my system", otherwise your original statement would be definitely wrong.
×
×
  • Create New...