Posts 1 - 10 of 19
First | Prev. | 1 2 | Next | Last
|
|
OliverM
Guest
|
I have ticked the option sign output, loader and manifest. Everything works like expected except that the adxloader.dll.manifest is not getting signed. Nevertheless the build log says
MyAddin -> Sign MyAddin.dll... Success
MyAddin -> Sign adxloader.dll.manifest... Success
MyAddin -> Sign adxloader.dll... Success
MyAddin -> Sign adxloader64.dll... Success
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
Any idea why signing the manifest does not work? |
|
Posted 19 Feb, 2018 09:25:12
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18787
Joined: 2006-05-11
|
Hello Oliver,
Is it possible that you look in a wrong location or such? If not, please send us a project reproducing this issue.
Andrei Smolin
Add-in Express Team Leader |
|
Posted 19 Feb, 2018 10:08:30
|
|
Top
|
|
OliverM
Guest
|
Hi Andrei,
I can reproduce the issue with a blank test add-in. Everything is getting signed except the manifest.
I would like to send you the test project but that would not help much as I unfortunately can not send you
my personal code signing certificate and the private key to use it.
The certificate I am using is issued by https://www.ascertia.com/, it is a standard code signing certificate. I have tested it and it has been recognized as valid during all tests.
I also tried to sign the manifest manually using signtool.exe but ended up with
SignTool Error: This file format cannot be signed because it is not recognized. |
|
Posted 20 Feb, 2018 03:55:20
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18787
Joined: 2006-05-11
|
Hello Oliver,
Does a test certificate works for you?
Andrei Smolin
Add-in Express Team Leader |
|
Posted 20 Feb, 2018 04:15:56
|
|
Top
|
|
OliverM
Guest
|
Nope, does not work either. Add-in is signed, adxloader and adxloader64 is signed but manifest is not (Created a new add-in for this test).
In general the way the dialog works is not transparent to me. It seems that the first setting used to sign the loader libs can not be changed anymore. I tried the following:
- Checked the signing option together with SHA1.
- Result: loader libs and add-in lib signed with SHA1.
- Changed setting to SHA256.
- Result: loader libs still signed with SHA1 add-in lib signed with SHA256
This behavior is also reflected in the log
1>------ Rebuild All started: Project: SignTest2, Configuration: Debug Any CPU ------
1> SignTest2 -> c:\users\tom\documents\visual studio 2015\Projects\SignTest2\SignTest2\bin\Debug\SignTest2.dll
SignTest2 -> Sign SignTest2.dll... Success
SignTest2 -> Sign adxloader.dll.manifest... Success
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ========== |
|
Posted 20 Feb, 2018 04:53:23
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18787
Joined: 2006-05-11
|
What Windows version are you using?
Andrei Smolin
Add-in Express Team Leader |
|
Posted 20 Feb, 2018 05:10:14
|
|
Top
|
|
OliverM
Guest
|
Windows 8.1 Pro
Visual Studio 2015
Office 2013
ADX 8.7.4430 |
|
Posted 20 Feb, 2018 05:39:37
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18787
Joined: 2006-05-11
|
Please create a new project in a folder other than Documents, use a test certificate to sigh the add-in, rebuild the project, zip the complete folder and send us the archive.
Andrei Smolin
Add-in Express Team Leader |
|
Posted 20 Feb, 2018 06:00:08
|
|
Top
|
|
OliverM
Guest
|
I have created another test add-in at root level and sent it to the support email address. Thanks for looking into this issue. |
|
Posted 20 Feb, 2018 06:46:28
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18787
Joined: 2006-05-11
|
Thank you Oliver,
I've looked into the manifest and it is signed: it contains the Signature element.
Andrei Smolin
Add-in Express Team Leader |
|
Posted 20 Feb, 2018 07:08:08
|
|
Top
|
|
Posts 1 - 10 of 19
First | Prev. | 1 2 | Next | Last
|