signtool/Applocker issue with SmartAssembly 8.1

AowAow Posts: 2 New member
in SmartAssembly

Windows Forms based EXEs are not affected by this issue. Only Consoles and Services,

Adding secpol.msc Applocker Publisher rule open EXE to get certificate and Product name is blank and version is incorrect.

No SmartAssembly 
Build .NET Console application x 64 RELEASE
Sign the EXE using Signtool.exe
Open EXE in Publisher browser Applocker to get certificate
Product name and version correct.,

SmartAssembly Post Build
Build .NET Console application x 64 RELEASE
- Smart Assembly (SA) ->new EXE
Sign the SA EXE using Signtool.exe
Open SA + Signed EXE in Applocker to get certificate
Product name and version not set.

How to resolve? Thanks

Tagged:
· Share on Twitter

Answers

  • Peter_LawsPeter_Laws Posts: 214 Silver 2
    I'm sorry to read you hit this issue Aow,

    The missing product name and version attributes, do you know where these values are derived from for signtool please?
    Kind regards
    Peter Laws | Redgate Software
    Have you visited our Help Center?
    · Share on Twitter
  • AowAow Posts: 2 New member
    Hi Peter,

    The values are derived from  .AssemblyInfo.cs  not signtool.

    [assembly: AssemblyTitle("Our .NET Component")]
    [assembly: AssemblyDescription("our .NET Component")]
    [assembly: AssemblyConfiguration("")]
    [assembly: AssemblyCompany("We Limited")]
    [assembly: AssemblyProduct("Our Socket Test")]
    [assembly: AssemblyCopyright("(c) 2007-2023 Us Limited")]
    [assembly: AssemblyTrademark("")]
    [assembly: AssemblyCulture("")]
    [assembly: AssemblyVersion("4.8.23.7")]

    Forms APP:         All picked up
    Console APP:     Version and product missing.


    You can only see the error after importing into Applocker..   The right click file properties are okay

    I can upload a console app that has this issue if helpful.

    thanks Adrian 
    . 

    · Share on Twitter
  • Peter_LawsPeter_Laws Posts: 214 Silver 2

    I can see an old issue where is there's a merged dependency that has an assembly version attribute set, but the main doesn't, it may overwrite. I appreciate the value substitution isn't quite the same as you described.

    Otherwise is the setup applicable please?

    Kind regards
    Peter Laws | Redgate Software
    Have you visited our Help Center?
    · Share on Twitter
Sign In or Register to comment.