Author Topic: Latest update and Proxomitron  (Read 9492 times)

0 Members and 1 Guest are viewing this topic.

Offline Umath

  • Sr. Member
  • ****
  • Posts: 204
Re: Latest update and Proxomitron
« Reply #15 on: January 30, 2006, 01:41:47 PM »
How about letting Web Shield ignore local communication (On-Access Protection Control>Web Shield>Basic>check "Ignore local communication") and monitor Proxomitron?  Of course, this is not a conclusive solution but may work.

About the Off Topic, I thought it is spelled Blanca in English...though the setting is Venice, Cassio's mistress had this name, for example.  There are some local variations in Europe but basically, the name sounds feminine to me while the illustration is quite contrary... ;D

Offline BlankaM

  • Newbie
  • *
  • Posts: 12
Re: Latest update and Proxomitron
« Reply #16 on: January 30, 2006, 05:26:04 PM »
I tried the suggestion above but I'm still getting the warning... :(

Offline Umath

  • Sr. Member
  • ****
  • Posts: 204
Re: Latest update and Proxomitron
« Reply #17 on: January 31, 2006, 01:04:53 AM »
I tried the suggestion above but I'm still getting the warning... :(

Did you close Web Shield and restart it after the changes?    This ritual may seem to be stupid but needed.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11803
    • AVAST Software
Re: Latest update and Proxomitron
« Reply #18 on: January 31, 2006, 09:56:46 AM »
BlankaM, you still get the warning with 0605-1 VPS?

Offline Nokia3510

  • Newbie
  • *
  • Posts: 2
Re: Latest update and Proxomitron
« Reply #19 on: January 31, 2006, 11:41:11 AM »
Igor, I can confirm that the problem regarding 0605-0 VPS and Proxomitron was solved in 0605-1 VPS. I could'n t understand, though, why this false alarm appeared randomly. Out of 5 identically PC's, only one had this annoying problem.

On the other hand, could you explain to me please the logic in numbering the VPS versions ? Other AV products release their updates in a dd/mm/yyyy form. Thanks in advance :)

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11803
    • AVAST Software
Re: Latest update and Proxomitron
« Reply #20 on: January 31, 2006, 11:55:27 AM »
Generally, it's YYWW-N, where N is the number of VPS within the week.

Offline BlankaM

  • Newbie
  • *
  • Posts: 12
Re: Latest update and Proxomitron
« Reply #21 on: January 31, 2006, 09:03:59 PM »
My apologies guys for not posting here sooner,

yes it's sorted now and doesn't appear! :D Thanks a lot!

Offline Umath

  • Sr. Member
  • ****
  • Posts: 204
Re: Latest update and Proxomitron
« Reply #22 on: February 01, 2006, 02:55:11 AM »
No news may be good news but a confirmation is always nice.

I cannot understand, though.  Why did it happen only with IE/Proxomitron combination and was it persistent even when Web Shield was supposed to be checking before Proxomitron?

Offline dr_j

  • Newbie
  • *
  • Posts: 15
Re: Latest update and Proxomitron
« Reply #23 on: February 01, 2006, 03:05:44 AM »
I can reply too, that it is now gone (the false positives). On that note, this appeared on every one of the machines I use that have Proxomitron installed..... so there was no randomness at all in my case.

j

Offline Scott Gilmore

  • Newbie
  • *
  • Posts: 2
Re: Latest update and Proxomitron
« Reply #24 on: February 01, 2006, 05:24:02 AM »
BlankaM, you still get the warning with 0605-1 VPS?
You guys are fast. Problem solved.

Thanks,
Scott Gilmore

Offline BjMarowitz

  • Newbie
  • *
  • Posts: 2
Re: Latest update and Proxomitron
« Reply #25 on: February 01, 2006, 12:34:42 PM »
Problem resolved for me as well.

As to the randomness, I have a home machine that isn't used regularly -- it was running Firefox 1.0.4 -- and there was no problem.

Firefox 1.5 on my company machine had the issue, as well as another test machine with Firefox 1.0.6.

Doesn't seem to matter whether it was Avast Home or Pro.

Thanks for the quick fix!

Offline Nokia3510

  • Newbie
  • *
  • Posts: 2
Re: Latest update and Proxomitron
« Reply #26 on: February 01, 2006, 02:30:29 PM »
I have an answer for the apparently randomness of the problem. It depends of the Proxomitron's Version. The June release worked fine. Older releases had this problem. Check your Proxo's Help-About guys :)