Vista - makecert.exe for Vista

Trying to assist a friend with creating a local authority cert and a personal
cert. The makecert file I sent him works fine on XP, but he has Vista. The
form pops up and then disappears immediately. Anyone know what is happening?

If a specific version of makecert is required, which one? And where can it
be downloaded by itself? Will it work if the person doesn't have the SDK
installed?

Thanks,

Extech

"eXtech" <eXtech@xxxxxx> wrote in message
news:E83947D4-F175-41D1-88EC-3C878358A5D1@xxxxxx

You'd need to run makecert.exe commands 'elevated' (ie 'Run as
administrator') with Vista - eg from an elevated cmd.exe or Powershell.exe
prompt.

--
Jon

I'd suggest using OpenSSL, since as far as I know, you're not allowed to
distribute makecert (plus, OpenSSL "just works" across platforms and doesn't
need elevation). Check out a script here to help you generate certs from
PowerShell
http://huddledmasses.org/code-signin...nd-powershell/

--
Joel "Jaykul" Bennett
http://HuddledMasses.org/
qotd: Man is the best computer we can put aboard a spacecraft ... and the
only one that can be mass produced with unskilled labor. -- Wernher von
Braun


"eXtech" <eXtech@xxxxxx> wrote in message
news:E83947D4-F175-41D1-88EC-3C878358A5D1@xxxxxx

"Jaykul" <Jaykul@xxxxxx> wrote in message
news:73651CF7-FD7C-4AE3-BC93-A8AD4AE3CA82@xxxxxxI'd disagree on a couple of bases:

1. OpenSSL is really poorly documented. If you thought it was an effort to
come up with the right syntax for makecert, you've got an even harder battle
coming when you try and divine the right OpenSSL command syntax to do ...
anything.
2. OpenSSL doesn't interface at all with the certificate stores in Windows.
3. Makecert only requires elevation when it's doing something "adminy" -
such as installing a certificate in the local machine's trusted root store,
to be used by all users on that machine. OpenSSL, as noted, doesn't touch
the local machine's trusted root store, so that's why it doesn't need
elevation. Using elevation as a reason to use OpenSSL is like saying that
you can use a bicycle instead of a car in order to save gas - while true, it
shouldn't be used to imply that the bicycle is a 1:1 replacement for the car
in all circumstances.
4. Why do you think you might need to redistribute makecert? It comes with
the Platform SDK - are your developers not using the Platform SDK?

Alun.
~~~~
--
Texas Imperial Software | Web: http://www.wftpd.com/
23921 57th Ave SE | Blog: http://msmvps.com/alunj/
Woodinville WA 98072-8661 | WFTPD, WFTPD Pro are Windows FTP servers.
Fax/Voice +1(425)807-1787 | Try our NEW client software, WFTPD Explorer.

On Sep 29, 1:37*pm, eXtech <eXt...@xxxxxx> wrote:You can make the certificate on any machine.
Once created, installing is as easy as clicking on the certificate
file.
Only installing in the root requires admin authority.

Alun Jones wrote:Points 1-3 are ... basically what was addressed by the script on the
page I linked to. Parameters, adding certs to stores, and elevation
*when needed* ...

Point 4 is the bottom line. That's EXACTLY correct -- they do not have
the platform SDK (if they didn't he wouldn't have been trying to pass
around makecert against licensing restrictions). But anyway, I don't
know who you mean by "developers" ... we're talking about PowerShell
scripters, I'd guess practically none of them have the PSDK. ;-)