trent nelson ktctpxaonresolvecom binaries signed makes installation process windows vista server 2008 little nicer instead getting unknownexecutablecould beavirusaaaaaahhhhwatchouttype dialog big red flag get less threatening message saying youre run something thats digitally signed python software foundation ive come across entities nsa government bodies etc mandate installersbinaries get must digitally signed required sign binaries 1 obtain code signing certificate someone used verisign end spc pvk file need combine single pfx file via tool called pvk2pfxexe usage pvk2pfx pvk pi spc pfx po f pvk input pvk file name spc input spc file name pfx output pfx file name pi pvk password po pfx password pi given f force overwrite existing pfx file pfx option given export wizard pop case options po f ignored c pvk2pfxexe pvk verisignprivatekeypvk pi spc onresolveverisignspc po pfx onresolveverisignpfx 3 resulting pfx file onresolveverisignpfx case installed personal certificate windows using certificate management facility certmgrexe install provide name certificate referred apps case used verisign name used signtoolexe app 4 sign executable msi dll follows c signtoolexe sign verisign python 260 du httpwwwpythonorg httptimestampverisigncomscriptstimstampdll python26msi successfully signed timestamped python26msi binaries signed personally figured steps hooked signing process visual studio projects postbuild step sign exe dll files really necessary eh advantage looking professional users view properties dll example see digitally signed psf additionally prevents tampering windows detect altered way since signed flat prevent loadedrun thats case trent _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 122155 0700 pythondev code signing windows msidllexes 2630