Code Signing

[EdPellesC99]

Hi,
I have google searched for the command line tool: "pvk2pfx.exe".

It is the only file I lack to play with code signing.

I have Microsoft SDK 2003, apparently it came in Server 2008 SDK.

I sure don't want to download it for this tiny file. I suspect you must have a fully functioning .NET framework on your machine for this SDK, and I do not .... so I do not think it would install even if I DID download the monstrous file.

Anyone know where else I might be able to get it from?

Thanks much !
Ed

[TimoVJL]

A 32-bit version of thePvk2Pfx tool is located in the bin\i386 folder of the WDK. A 64-bit version of the tool is located in the bin\amd64 and bin\ia64 folders of the WDK.

So maybe it is in WDK (Windows Driver Kit).

EDIT:
That can be found from
WDK 7.1:
WDK\buildtools_x86fre_cab001.cab

Windows Server 2003 R2 Platform SDK:
\Setup\PSDK-SDK_Core_BIN-common.0.cab   pvk2pfx_exe.40ED341D_22C2_4704_B35D_E00CC4010EBE

PS:
How about using posign.exe ?

[EdPellesC99]

Yes it is. Here:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11800

The download is 618 Mb all to get the @100 kb file.

For me the download will fail 1/3 way thru for one reason or another.

I would order the SDK as a disc, but Microsoft declines my credit card. Support does not answer me when I ask why they are declining my card.

It is way too hard.

[Stefan Pendl]

Did you try to use the web-install and only select the tools to be installed?

[EdPellesC99]

The Windows Driver Kit seems to be Only available as the 619 Mb ISO image.
I could spend days trying to get the .Net 3.5 framework properly installed so that a Server 2008 install of any sort would not fail.

Stefan a web install of 2008 would fail because of the .net problem I have.

Timo:
Apparently the SDK I have is NOT Server 2003 SDK.

So it was ? something I got long ago. Anyway you show it in 2003, and I found:
http://www.microsoft.com/download/en/details.aspx?id=3069

Here I can download the 2003 SDK one by one in 25 Mb packages.

I will do this today.

Meanwhile I will look into Posign.exe   ........

Tx to both you Stefan and Timo for your replies !

.... Will get back, Ed

[TimoVJL]

Download least PSDK-FULL.4.cab and PSDK-FULL.5.cab.
Open PSDK-FULL.4.cab with 7Zip for extracting that file.
EDIT:
Open PSDK_SDK_Core_BIN-common.0.cab.
Extract that file.
Rename extracted file to it's real name.

[EdPellesC99]

Ok, I got it.

I tried to just unzip .cab 4 and 5 but NO go.

I got all 17 25 cab files, and into same folder, the 18th package: "PSDK-FULL.exe"

The last is a self extracting .exe containing: "PSDK-FULL.bat" and "extract.exe"
Having both in the same folder as all the cab files,
I ran the .bat file.
Usage:
"PSDK-FULL.bat" C:\Temp

*THEN* you run Setup.exe in C:\Temp

I chose the custom install, disabling almost all the features except the most likely ones.

Lo and behold in:
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin
was the 14 kb file I sought.

Quite a bit of effort, and it cost Microsoft a whole lot of bandwidth for that 14 kb file.

Mission accomplished, after disabling much during the install .....I still ended up with 758 Mb of junk in
"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2"

I will look into Posign.exe after a bit.

Time for a beer ! 

Thanks to you both,
Ed

[EdPellesC99]

EDIT:
Open PSDK_SDK_Core_BIN-common.0.cab.
Extract that file.
Rename extracted file to it's real name.

Ouch,

  Did not know I could just rename it. Tried it. Yup it works... confirmed by checking the Md5.

Wow that would have been easier !  Just haven't fooled with cab files much.

Good to know !

Story of my life .... I always end up doing it the hard way !

Tx, Ed

[Stefan Pendl]

Wow that would have been easier !  Just haven't fooled with cab files much.

A .CAB file is just a compressed archive, so not much of a difference to a .ZIP file

[EdPellesC99]

That is what I had always understood, this is a special one though as I guess the files are being renamed from something unrecognizable to a standard filename by the microsoft .msi installer.

Without knowing I could rename them, I was in the dark. totally...