Reply to Thread

Post a reply to the thread: Suspicious.Cloud again..

Your Message

Click here to log in

What's the name of our main installation product (in uppercase letters), directly followed by the current year?

 

You may choose an icon for your message from this list

Additional Options

  • Will turn www.example.com into [URL]http://www.example.com[/URL].

Topic Review (Newest First)

  • 02-26-2014, 05:22 AM
    linder

    Re: Suspicious.Cloud again..

    You are very welcome.

    By the way, we have accepted all the standard (default) Symantec installation settings. We did not change a single recommended option. We did not add any Exception (and no files are quarantined; we created and compiled 50 test .sb8 projects).

    Friedrich
  • 02-26-2014, 05:11 AM
    ThoKluge001

    Re: Suspicious.Cloud again..

    Many thanks for your effort.

    I have exactly the same Symantec Version. Correct.

    I will play around and try to find out what might be different on my side.

    I'm getting back to you about my results.

    Thanks a lot.
  • 02-26-2014, 04:15 AM
    linder

    Re: Suspicious.Cloud again..

    Here are the installed Symantec versions (see screenshot).

    Friedrich
  • 02-26-2014, 03:47 AM
    linder

    Re: Suspicious.Cloud again..

    And that's from your original Hybrid installer type demo project (dated: 2/20/2014).

    Friedrich
  • 02-26-2014, 03:38 AM
    linder

    Re: Suspicious.Cloud again..

    Thomas,

    See attached screenshot. Symantec Endpoint Protection Version 12.1.4013.4013 (64-bit) installed on a clean Windows 7 Ultimate (x64) machine. After that, we installed SetupBuilder 8.1. Then we created a "dummy" standard project with code-sign option (.pfx) and compiled it. No problem at all (no false-positive when installing SetupBuilder nor when compiling a project). Latest Symantec updates and definitions applied.

    Friedrich
  • 02-26-2014, 01:50 AM
    ThoKluge001

    Re: Suspicious.Cloud again..

    I'm using the pfx file and have switched to the Microsoft SignTool.exe from the SDK 7.0.
    But it seems the SignTool can not be called, cause before Symantec is removing the temp files.
  • 02-26-2014, 01:15 AM
    linder

    Re: Suspicious.Cloud again..

    Thomas,

    To code-sign files with a .PFX, you have to switch to Microsoft SignTool.exe.

    http://www.lindersoft.com/forums/showthread.php?p=75360

    Friedrich
  • 02-26-2014, 12:53 AM
    linder

    Re: Suspicious.Cloud again..

    Thomas,

    I think you are using a code-signing certificate in form of .PFX, but you forgot to switch to Microsoft SignTool.exe. You are still using SignCode.exe.

    Friedrich
  • 02-26-2014, 12:43 AM
    ThoKluge001

    Re: Suspicious.Cloud again..

    Hi,

    tryed to add a digital signature to the setup and getting following problem.

    Do you have any idea what to do?
  • 02-25-2014, 08:53 AM
    ThoKluge001

    Re: Suspicious.Cloud again..

    Hi,
    trying to code sign the Setup.

    Getting following error from SetupBuilder
    and from Symantec.

    Any idear what I can do here?
This thread has more than 10 replies. Click here to review the whole thread.

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •