Home Explore Help
Sign In
pascal
/
innosetup
mirror of https://github.com/jrsoftware/issrc.git
2
0
Fork 0
Files Issues 0 Wiki
Browse Source

Tweak.

Martijn Laan 2 months ago
parent
72a5c00108
commit
67094c8f5b
3 changed files with 6 additions and 6 deletions
Split View Show Diff Stats
  1. 1 1
      ISHelp/isetup.xml
  2. 4 4
      README.md
  3. 1 1
      whatsnew.htm

+ 1 - 1
ISHelp/isetup.xml
View File 

@@ -3615,7 +3615,7 @@ Filename: "{win}\MYPROG.INI"; Section: "InstallSettings"; Key: "InstallPath"; St
 
 <topic name="issig" title=".issig Signatures: Introduction">

 <body>

 

-<p>Inno Setup includes an integrated signature-verification capability that can be used to detect corruption or tampering in files at compile time, before files are included in an installer being built, or during installation, before Setup copies external files onto a user's system.</p>

+<p>Inno Setup includes an integrated signature-verification capability that can be used to detect corruption or tampering in your files at compile time, before files are included in an installer being built, or during installation, before Setup copies external files onto a user's system.</p>

 

 <p>Signatures are created using the included <link topic="issigtool">Inno Setup Signature Tool</link> utility (<tt>ISSigTool.exe</tt>) and are stored in separate files with an <tt>.issig</tt> extension. Because the signatures are stored in separate files — the original files are not touched — any type of file may be signed and verified.</p>

+ 4 - 4
README.md
View File 

@@ -138,10 +138,10 @@ Setup program into the user's TEMP directory and runs it from there. It also
 
 displays the "This will install..." and /HELP message boxes.

 

 **ISSigTool** - This is a command-line utility which can be used to sign and verify

-any file. Compil32, ISCC, and ISCmplr use these signatures to verify the

-authenticity of a number of DLL files before loading them. Note: this utility does

-not replace Microsoft's signtool.exe in any way and is in fact not related to

-Authenticode Code Signing at all.

+any of your files. Compil32, ISCC, and ISCmplr use these signatures to verify the

+authenticity of a number of DLL, E32 and EXE files before loading them. Note: this

+utility does not replace Microsoft's signtool.exe in any way and is in fact not

+related to Authenticode Code Signing at all.

 

 How do the projects link together?

+ 1 - 1
whatsnew.htm
View File 

@@ -40,7 +40,7 @@ For conditions of distribution and use, see <a href="files/is/license.txt">LICEN
 
 

 <p><a name="6.5.0"></a><span class="ver">6.5.0-dev </span><span class="date">(?)</span></p>

 <span class="head2">New signature-verification capability</span>

-<p>Inno Setup now includes an integrated signature-verification capability that can be used to detect corruption or tampering in files at compile time, before files are included in an installer being built, or during installation, before Setup copies external files onto a user's system.</p>

+<p>Inno Setup now includes an integrated signature-verification capability that can be used to detect corruption or tampering in your files at compile time, before files are included in an installer being built, or during installation, before Setup copies external files onto a user's system.</p>

 <p>Any type of file may be signed and verified, and creation of signatures does <i>not</i> require a certificate from a certificate authority. There is no cost involved.</p>

 <p>Note, however, that these signatures cannot be used to eliminate an "Unknown publisher" warning message shown by Windows when an installer or other EXE file is started. That requires a completely different kind of signature (Authenticode) embedded inside the EXE file by a different tool (Microsoft's <tt>signtool.exe</tt>), and it does require a (usually expensive) code-signing certificate from a certificate authority.</p>

 <p>A more detailed summary:</p>