Possible conflict between Secunia PSI and avast?

I’ve been using Secunia’s online scanner for a while, just as a double-check in case I’ve missed something in Updates here. Yesterday I downloaded their PSI since it has a much larger database of apps than the online version.

When trying to install it (while online), I got an error message indicating it couldn’t access my user-name, asked me to verify I could connect with their https address (which I did fine) and try again.

The second line of that error message indicated the problem could be from using a proxy, and they regret the product can’t yet handle proxies.

I set Comodo (I disabled the Defense+ ages ago as more nuisance than help) to treat it as a trusted application, still no luck.

Anyone else run into this yet? Any wild chance this is one of the extremely rare cases where avast’s “transparent proxy” isn’t transparent enough?

Admittedly this brand-new version is tagged RC1, which to me means it’s “almost but not quite” and still technically a beta. So maybe there’ll be further bug fixes shortly, if that’s the problem.

Mike, I don’t think avast WebShield has nothing to do with PSI… PSI proxy settings should be left blank. WebShield is just a local proxy, not one for connection. There is a PSI new version and you can try it.

Thanks, Tech. What I was playing with was supposedly their latest, 0901-A – I know there’s a -B just been released, but it looks like that “merely” added German-language support and interface.

If it wasn’t clear from my first post, the PSI never did finish installing, so I was never able to open it and get at setup options or anything else.

But did it never work? Couldn’t you finish the installation?

Hi again Tech,

I tried re-installing after looking at your last reply, and guess my memory of the problem wasn’t quite accurate. This time (and presumably the first time) it did install OK (no desktop icon, but that was easy enough to fix). After starting it, however, I got the message “Unable to retrieve your user ID from Secunia”, along with the suggestions noted in my original post.

Tried something new this time … I found that if I set IE as default browser, it would start and run fine. :stuck_out_tongue: :stuck_out_tongue: So I’ll probably trash it again and go back to the online version … seems like every other developer who needs to use IE’s engine can do so without having to change the default browser.

OK, one more update … it looks like the problems are more with sloppy documentation than with PSI itself.

Once I’d used IE (as default) to “register” my profile, and got their confirming activation-email (and used the activation link), it finally seemed to happily accept Firefox as default browser on subsequent runs. Helluva way to run a railroad, as they used to say – especially since there’s no mention of all this in the instructions.

And I was pleasantly surprised at what’s in the bigger database – even one of my gaming-site things, PokerStars. Plus if I switched to expert mode, my obscure but free DVD player turned out to need an update.


Glad to know you got it sorted out, Mike. :slight_smile: