I got a report of a user seeing the same signature on our website. I've got a second submission in the queue to cover that one as well.
They've got a testing license that I should be able to download and use to reduce when I have a second. On 2009-12-09, at 11:29 AM, Joel Webber <j...@google.com> wrote: > Were you able to get any information on the signature (assuming it's > signature-based) from Avira? Their page on the subject is, uh, less > than useful. > > On Wed, Dec 9, 2009 at 1:09 PM, Matt Mastracci > <matt...@mastracci.com> wrote: > We've just had reports of people seeing this while installing our > chrome extension. I'm not near a Windows VM right now, but I can see > if it's easy to reproduce when I get back: > > http://getsatisfaction.com/dotspots/topics/dotspots_plugin_for_chrome_installer_problems > > There's a lot of embedded CSS in the script, as well as HTML snippets. > It's the same virus report as Daniel earlier: "HTML/Crypted.Gen". > > Matt. > > On 30-Nov-09, at 9:20 AM, Joel Webber wrote: > > > If you can find out what was triggering this from Avira, I'd really > > like to see it. This is probably the third-ish time we've seen a > > report like this, and it would be really helpful to understand what > > kind of virus snippets they're looking for. If there's something we > > can do in our code gen to avoid the problem in the future, it would > > probably be worth it. > > > > On Mon, Nov 30, 2009 at 10:19 AM, Thomas Broyer <t.bro...@gmail.com> > > wrote: > > > > On Nov 30, 3:43 pm, BobV <b...@google.com> wrote: > > > On Sat, Nov 28, 2009 at 10:54 AM, Ray Ryan <rj...@google.com> > wrote: > > > > Does one app make heavier use of CssResource than the other? A > > bell is > > > > ringing about mhtml security concerns. Or did we back out our > > mhtml use? > > > > > > I disabled MHTML support in r6839 (trunk) and r6840 (2.0) > because it > > > has too many browser/OS gotchas to be reliable for the 2.0 > release. > > > > And it couldn't have been MHTML in our case, as we're serving the > app > > with HTTPS, which is sniffed in MhtmlClientBundleGenerator to fall > > back to a "one file/request per resource" (otherwise, the "mhtml:" > > pseudo-protocol causes a "mixed content" warning in IE). > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
