liso
Member of DD Central
Posts: 389
Likes: 394
|
Post by liso on Nov 28, 2017 18:34:58 GMT
I have AVG CloudCare, Windows 8.1 IE and no problems logging in. Could it be that the problem is with the free versions of AVG/Avast only?
|
|
rxdav
Member of DD Central
Posts: 354
Likes: 349
|
Post by rxdav on Nov 28, 2017 18:42:33 GMT
liso,
AVG Internet Security is a paid for product. I can log on if I use the quarantine facility - but each page I access thereafter also requires the same quarantine treatment to progress. A local fix involves me creating an exception - not a risk I'm prepared to take.
As I said previously - I have no problems with any other site - only Collateral (discovered today when seeking to look at the new loan - but I haven't logged on for a few days).
|
|
amphoria
Member of DD Central
Posts: 156
Likes: 124
|
Post by amphoria on Nov 28, 2017 21:25:16 GMT
amphoria,
I currently use full AVG Internet Security (on Windows 7 Pro) and have used AVG for many years now - with so few issues over those years I am content it is a superb product. I can say without equivocation that I have never had a 'false positive' with any other legitimate site - ever. Furthermore, I am simply not prepared to create an exception and put my system at potential risk - I simply shouldn't have to do this under any circumstances.
I will wait out this loan until a fix in in place and if a fix is not found I will exit the platform (permanently if necessary) - I have too much at potential risk to do otherwise. No other platform I use has ever given me such issues - so I am content it is totally in the realm of Collateral and/or their software developers to get this resolved - and quickly. In that case I suggest that you push AVG/Avast to fix the problem with their software. It is detecting a virus that does not exist. The 3 false positives found during PC Pro's testing means that they are pretty rare with Avast/AVG. F-Secure had 38 false positives by comparison. Thus it is not surprising that you have not come across any others.
|
|
|
Post by isecguy on Nov 29, 2017 9:34:32 GMT
Afternoon, Again, we have been on the Avast website and reported this as a false positive and explained what we did with regards scanning the server and the clean results etc. Hopefully they will fix this and get back to us ASAP. This is a local computer issue and as zendog just posted, you will have to add the Collateral web address as an exception in the AVG Web Shield settings. Many thanks, Gordon This is REALLY BAD advice from Collateral! Granted, in this particular instance it certainly looks like a "false positive", however adding a permanent exclusion/exception to your antivirus software for Collateral's website is NOT RECOMMENDED! ...the simple reason being that if Collateral's website was ever to be hacked/infected by malware in the future, your anti-virus software would ignore it! So please don't add exclusion/exception to your antivirus software for Collateral's website - the onus should be on Collateral to not only report the false positive to the AV vendor, but also to identify and re-code the specific parts of their website/scripts that are triggering false-positives in anti-virus software in the first place. It's also worth mentioning that Collateral's assertions that they have "scanned their servers" offers little protection. Just because malware isn't running on a server itself doesn't mean that the same server isn't capable of at the same time delivering malware directly to an end-users browser. For example, if a server is hacked and a web page modified to deliver malware - a malware scan of the server will scan the server itself for malware - and not necessarily the web pages it delivers (especially if web pages are dynamically generated). Again, I would just clarify; I'm not for one minute saying that Collateral's servers have been compromised, nor am I saying that this particular instance is anything more than just a harmless "false positive".... but what I am saying is that adding a permanent exclusion/exception to your antivirus software for a given website leaves you more vulnerable, and a website assuring you that they've scanned their servers offers little protection against infected client-side web pages.
|
|
dh1
Member of DD Central
Posts: 373
Likes: 383
|
Post by dh1 on Nov 29, 2017 14:05:21 GMT
Very well said, isecguy. People can now make their own calls about how to handle this damaging incident; an AV exception may be the only way forward at this precise moment but I'm going to remove mine just as quickly as I can. Many of you will have noted that my initial post (top of the thread) was carefully worded to avoid jerking knees; you got factual information with a hint or two about what I was doing. The following posts were intelligent and helpful, especially where they indicated which software was moaning and which wasn't, thus providing Gordon with a great picture of what was actually happening in the real world.
|
|
rxdav
Member of DD Central
Posts: 354
Likes: 349
|
Post by rxdav on Nov 29, 2017 18:25:38 GMT
Logged on again this morning and the issue was persisting - however, just tried again and it now seems resolved.
Can only concur that it was dreadful advice to create an exception. Notwithstanding that this situation should never have arisen in the first place (are software updates/upgrades not fully tested off-line using proprietary products before being released live?) - the advice to create an exception should simply never have been offered.
|
|
|
Post by Collateral Rep on Nov 29, 2017 19:33:49 GMT
Evening rxdav, If the issue has been resolved for you, I suspect Avast have looked into our submission of the URL in question and found that there was no issue. Gordon
|
|
msenanna
Member of DD Central
Posts: 73
Likes: 41
|
Post by msenanna on Nov 29, 2017 20:46:57 GMT
Evening rxdav , If the issue has been resolved for you, I suspect Avast have looked into our submission of the URL in question and found that there was no issue. Gordon Issue also resolved for me thankfully. Just have 48 updates to trawl through
|
|
|
Post by Collateral Rep on Nov 30, 2017 7:58:54 GMT
Morning,
Reply from Avast.
******
Hello,
Thank you for contacting Avast.
Our virus specialists have been working on this problem and it has now been resolved. The provided website isn't detected by Avast anymore.
We are sorry for the inconvenience. If you have any further questions, don't hesitate to contact me again.
Best Regards, Prokop The Avast Support Team
******
As previously mentioned we did our server scans and looked into the URL in question and found we had no issues, but unfortunately when it's a third party that we have no influence over, we have to just wait.
Gordon
|
|
dh1
Member of DD Central
Posts: 373
Likes: 383
|
Post by dh1 on Nov 30, 2017 8:37:14 GMT
Yep - Avast have fixed this. Exception removed!
Hopefully their wording is wrong and what they mean is that there is no current problem with the website rather than the software is just ignoring it.
I am reassured that Avast have responded quickly - possibly prompted by the liability they may incur by incorrectly "blocking" a transactional commercial site.
|
|
guff
Posts: 730
Likes: 707
|
Post by guff on Nov 30, 2017 15:29:33 GMT
I am reassured that Avast have responded quickly - possibly prompted by the liability they may incur by incorrectly "blocking" a transactional commercial site. In my experience, it is fairly typical of their response time to reporting false positives. I got the same e-mail as Collateral Rep this morning as I had also reported it a couple of days ago.
|
|