-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still not so clean. #55
Comments
thanks for the updates dude |
fortunately Avast is one of the biggest jokes of the AV industry, so nobody should take much of what they have to say about anything with a lick of seriousness. back in the day they would leave the previous years major release without definition updates which allowed for entire Windows XP worm botnets to spread. You can't actually do Export redirection the way that VxKex does in a AV happy manner unless you EV sign your libraries. |
You misspelled Norton. Avast is actually the premier AV program, hence why it's recommended by pretty much every tech bro and technician.
This has already been disproven. I would know, i had (and still have) an XP system. Avast quite competently defends against botnet infection.
I'm not sure what EV signing is but it sound like the problem in question is already known. Hopefully we can expect said signatures in the next update to VxKex. |
In no reality is Avast a premier av program.
Nowhere has this been disproven, you just asserted your recent experience as if it was how Avast would do things 20 years ago, and in fact there is evidence 6 years ago they were still doing this BS
EV signing costs thousands, not happening. |
Except this one. Because it is, but you keep believing what makes you feel better, if less safer. Just don't do it here.
I love how you immediately do what you accuse me of. It's been disproven by not only myself but many people in the industry. Maybe spend some time researching things instead of believing everything your told, yeah? Now please stop posting here as this is derailing the issue.
If this were true, then many programs simply would not exist. There are many programs created by people who don't have thousands of dollars that Avast, and the dozens of others that have a problem with VxKex, have no problem with, from itch games to UI editors to my personal favorite Win7 taskbar tweaker (i guarantee you the creator of that program didn't have thousands of dollars to spend). So again, please let me and i486 work in peace, thank you. |
lol, your answer is just not serious. This page has no value... do you call these comments, official tests? What you show has no correlation at all with the capacity for avast to detect something suspect in this project. maybe something more reliable is needed for you |
Keeping VxKex av-clean will takes a lot of time, efforts and moneys. At least an OV certificate is necessary, because virus use same technology of VxKex used, publisher release it need to validate himself, or else user will be warned. |
There is no such thing as a "premier" antivirus program, since they can all be bypassed with a few lines of code. |
premier /prĭ-mîr′, -myîr′, prē′mîr/
Avast is the most effective AV available on the market thus it is the premier AV program. BTW you do know that every single post you people make that tries in vain to condemn Avast only makes i486 look more suspicious, right? I don't know why your simping this hard unless you know there is something in the code that shouldn't be there and your trying to derail any conversation that might reveal it. Either way this issue is about VxKex's safety and adherence to standardized safety guidelines, so if your post is not about that then i recommend that you and everyone else stop posting here, this is not a social networking platform. |
i486 is not the author, this is a hard work for him. You should ask vxiiduu to do, but I think he will reject, just like he left here silently before. |
The author left? Then who is maintaining the program? |
So, you are the people who never see the release note. |
I'm among them yes. What happened? |
After presenting Avast with the information provided by i486 in #41 (comment) they have gone ahead and changed the status of the program to PUP (potentially unwanted program) and recommend that if i486 would like the status of the program to be changed to clean that i486 insure that the program matches the Avast Threat Labs - Clean guidelines. and request another analysis.
The text was updated successfully, but these errors were encountered: