Skip to content

Commit de05123

Browse files
olszomalmtrojnar
authored andcommitted
update documentation
1 parent 180b352 commit de05123

File tree

1 file changed

+13
-10
lines changed

1 file changed

+13
-10
lines changed

README.md

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,24 +19,28 @@ tool would fail. And, so, osslsigncode was born.
1919

2020
## WHAT CAN IT DO?
2121

22-
It can sign and timestamp PE (EXE/SYS/DLL/etc), CAB and MSI files. It supports
23-
the equivalent of signtool.exe's "-j javasign.dll -jp low", i.e. add a
24-
valid signature for a CAB file containing Java files. It supports getting
25-
the timestamp through a proxy as well. It also supports signature verification,
26-
removal and extraction.
22+
It can sign and timestamp PE (EXE/SYS/DLL/etc), CAB, CAT and MSI files.
23+
It supports the equivalent of signtool.exe's "-j javasign.dll -jp low",
24+
i.e. add a valid signature for a CAB file containing Java files.
25+
It supports getting the timestamp through a proxy as well. It also
26+
supports signature verification, removal and extraction.
2727

2828
## BUILDING
2929

3030
This build technique works on Linux and macOS, if you have the necessary tools installed:
3131
```
32-
./autogen.sh
32+
./bootstrap
3333
./configure
3434
make
3535
make install
3636
```
3737

38-
* On Linux, (tested on Debian/Ubuntu) you may need `sudo apt-get update && sudo apt-get install build-essential autoconf libtool libssl-dev python3-pkgconfig libcurl4-gnutls-dev`
39-
* On macOS with Homebrew, you probably need to do these things before autogen.sh and configure:
38+
* On Linux, (tested on Debian/Ubuntu) you may need
39+
```
40+
sudo apt-get update && sudo apt-get install autoconf libtool python3-pkgconfig libssl-dev libcurl4-openssl-dev
41+
```
42+
43+
* On macOS with Homebrew, you probably need to do these things before bootstrap and configure:
4044
```
4145
brew install [email protected] automake pkg-config libtool
4246
export PKG_CONFIG_PATH="/usr/local/opt/[email protected]/lib/pkgconfig"
@@ -99,11 +103,10 @@ An example of using osslsigncode with SoftHSM:
99103
osslsigncode sign \
100104
-pkcs11engine /usr/lib64/engines-1.1/pkcs11.so \
101105
-pkcs11module /usr/lib64/pkcs11/libsofthsm2.so \
102-
-certs <cert-file> \
106+
-pkcs11cert 'pkcs11:token=softhsm-token;object=cert' \
103107
-key 'pkcs11:token=softhsm-token;object=key' \
104108
-in yourapp.exe -out yourapp-signed.exe
105109
```
106-
osslsigncode currently does not support reading certificates from engines.
107110

108111
You can check that the signed file is correct by right-clicking
109112
on it in Windows and choose Properties --> Digital Signatures,

0 commit comments

Comments
 (0)