![]() I am trying to identify the difference and looked thru "Local Group Policy" with "Do not preserve zone information in file attachment" and that was Not Configured. And therefore during my manual test run, I am okay. When I start up a vagrant image running Windows 2012 R2 (64bit) with NTFS system and download this signed installer, I noticed that the "Zone.Identifier" is NOT removed when I do a more < myinstaller.exe:Zone.Identifier and if I bring up the file's properties, I DON'T see this warning/error about "This file came from another computer and might be blocked to protect this computer". However, here are the discrepancies that I am trying to figure out. An internet search quickly points to this NTFS's feature. ![]() Yesterday, our tester for another product release noticed a problem on a Windows 2003 and Windows 2008 box and discovered this message from Files' properties. I will then manually open the File's properties to double check to be sure. Running signtool /verify option to check that the signing was done properly.ΔΆ. We had been doing this since end of July (it is not fully automated yet) and we had done more than 50 signings for different products' releases. ![]() Basically, we does a Symantec extended validation code signing on our windows product installer. I am encountering a strange inconsistency with this message. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |