Announcement

Collapse
No announcement yet.

NSIS 2.17 vs Symantec = Trojan.Zlob (here we go again)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NSIS 2.17 vs Symantec = Trojan.Zlob (here we go again)

    Yeah, it seems symantec updated it's virus definitions again and all uninstallation files recognize like Trojan.Zlob. And now i even can't download and run nsis installation package.
    Checked using:
    Norton Antivirus 2006.
    Symantec Antivirus 10.0 Corporate Edition.
    Developers, please do something with that idiots in symantec
    Nsis is a Great job, btw

  • #2
    Well, so you know is a false positive...don't need to be alarm.

    Have a nice day

    * PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with MATE.
    * Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with MATE.

    Comment


    • #3
      /ot
      >> Developers, please do something with that idiots in symantec

      rough words - forum, ban these (...) Symantec consumers.

      Symatec products always suck - and they suck ev'time a bit more.

      I never had a postive false with NOD, but i see lots with Symantec, McAfee, KAV, and some more.

      and one more - symantec has a deal with microsoft that some nice tweaking and modifier tools where treaten as virus/trojans/aso.
      Greets, Brummelchen

      Comment


      • #4
        well I am sure it is a false positive... but people using my installer are reporting Trojan.Zlob found with Norton Antivirus. I can't have that, can anyone do anything about this? or tell me what needs to be done to avoid it?

        Comment


        • #5
          • Make sure they're using the latest definitions, because this has, as far as I know, already been fixed.
          • If it hasn't been fixed, report this to Symantec and give them my e-mail for more details ([email protected]).
          • Rebuild your installer with another version, such as the newly released 2.18.
          NSIS FAQ | NSIS Home Page | Donate $
          "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

          Comment


          • #6
            Thank you, I'll follow steps 1 and 3 for now.

            Comment


            • #7
              >> such as the newly released 2.18

              And again i miss the News for that...
              Greets, Brummelchen

              Comment


              • #8
                Kichik,

                I can second intelworker's issue. SAV 10 corporate with 7/1/06 v8 defs, which are latest as of right now (10:00 AM EST). I'll email Symantec, and give them your info, as I've got over multiple packages deployed to 70,000 users that can't be updated on the fly. ;-)

                Thanks for the help.

                Mike

                Comment


                • #9
                  Updated the false positives page.

                  -Stu

                  Comment


                  • #10
                    I think there should be a sticky about false positives

                    * PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with MATE.
                    * Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with MATE.

                    Comment


                    • #11
                      Good idea. I'll see what I can do.

                      Edit: I'll let Kichik create an announcement post as he knows best

                      -Stu

                      Comment


                      • #12
                        Does 2.18 cause the same problem ?

                        Comment


                        • #13
                          I had quite a few of my installs wiped out by this latest problem with Symantec.

                          So far, however, rebuilding them in NSIS version 2.18 seems to have worked. (Using a different compression algorithm may also work, although I've found nothing concrete to support this claim.)

                          Comment


                          • #14
                            Does 2.18 cause the same problem ?
                            I just installed 2.18 to get around this problem. Didn't work.

                            Comment


                            • #15
                              I have installed 2.18 and no problems at all.

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎