Jump to content

Recommended Posts

  • 1 year later...
  • 6 months later...
On 10/26/2018 at 2:00 PM, MaxTrax said:

Since I cannot seem to find it: Where are the logs for this? I am getting a failure that says to check logs, but the its not alluding the location. 

Sorry I haven't been on the forum in a while and didn't seem to get notified of your post.

The log should be made in the same directory as the sign tool.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Tankbuster
      If someone gets offended by this, because he knows already 200 posts about it. Do not reply.
      Yes, some wrote already here some words what to do. Yes, you are right I created nothing new.
      But I want this summed up for forum searchers, that maybe find this posting useful in spending less time to find an answer in one place.
      I don't want to re-animate very old postings. So forgive me if I try to help other idiots like myself.
      First I need to give credits to:
      For summing it up in a nearly complete way.
      There is a nice Gui existing that wrapps it up: Digital Sign Tool
      Below you also find some instructions how to add it to the compiler.
      I tested this on a Windows 7 (x64) - but all codes used is x86 (32bit) - for 64bit I need to create another package (or make the script smarter).
      So here is the sequence in general:
      general purpose: I created several EXE files of the years, and I do not want to use the SIGNUI to click each file. So I want a command line version.
      Create a folder - I named it x:cert4me Download from : http://www.kastaban.de/cert4me/MAKE_MY_CERT_FILE.zip The zip: Contains: 1999-04-15 17:10:28 PVKIMPRT.EXE 2003-03-24 23:03:00 makecert.exe 2005-09-23 07:56:00 cert2spc.exe 2006-03-03 23:22:44 signtool.exe 2007-04-11 11:11:20 capicom.dll 2007-09-27 14:17:44 pvk2pfx.exe 2013-03-13 15:24:27 MAKE_MY_CERT_FILE.CMD 2013-03-13 15:31:52 SIGN_FILE.CMD Extract the files in : X:Cert4me now open a cmd in the created folder with the extracted files (the script will also work from other folder but so you are closer to the result...) cd /D x:\cert4me Now you either watch this little video with a sample of the signing process (a little bit fast - but you are to pause it if you like, and sorry for the German screen texts)
      http://www.kastaban.de/cert4me/CERT4ME/CERT4ME.html or
      First start : MAKE_MY_CERT_FILE.CMD myNewCertificate secret01 MAKE_MY_CERT_FILE.CMD needs two arguments
      1=the name of the certificate
      2=your password
      Sign now the EXE with: SIGN_FILE.CMD "d:\1work\mit space\TFTP_HELPER.exe" keys\myNewCertificate_cert.pfx secret01 SIGN_FILE.CMD needs three arguments
      1=the file path of your executable
      2=the filepath to the pfx folder (created before !)
      3=your password
      in case you want to sign more than one EXE repeat the "Sign now" step with the other EXE.
      I packed the files from the original post and added additional files to offer a complete package.
      this was tested on Windows 7 (64bit) but all tools and my EXE are 32bit . Keep this in mind.
      For 64bit the similar tools of 64bit are maybe needed (not sure).
      Maybe someone could start to convert this to a AU3.....because some fields are still left open. Like the End DATE, email field, timestamps URL.....
      And "if" someone got additional stuff to add here (for other idio.....mmmh......searchers), do it.
      And most important , in case I wrote something wrong or it does not work for you please comment.
      //edit: 16.03.2013 - Thx Emiel - as always I face problems with the NOT and Or :-)
  • Create New...