Skip to content

Commit 0a1b59d

Browse files
committed
win agent v6.33.0.0 - add ssl ca authority support
1 parent a73d1f3 commit 0a1b59d

5 files changed

Lines changed: 16 additions & 16 deletions

File tree

-4.22 KB
Binary file not shown.
-4.64 MB
Binary file not shown.
4.68 MB
Binary file not shown.

winagent/README.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ this agent performs the role that typically unix syslog does, the agent now uses
77
HTTP/HTTPS rather than syslog protocol.)
88

99
### Download
10-
[Download](LogZilla_SyslogAgent_6.32.1.0.msi) Here
10+
[Download](LogZilla_SyslogAgent_6.33.0.0.msi) Here
1111

1212
### Features
1313
This program supports the following:
@@ -94,16 +94,20 @@ There is an option to use TLS to send messages to one or both LogZilla servers.
9494
every message sent to the primary or secondary server will use a TLS communications link.
9595

9696
### Select Primary / Secondary Cert
97-
These buttons are used to select (PFX format) certificate files for the TLS communications
98-
to the primary or secondary server. When the button is clicked a window will pop up
99-
allowing selection of the file from which the cert is to be read. Please note that once
100-
the cert is read and imported (using the button) that certificate information is copied
101-
into the LogZilla settings and the source cert file is no longer used. The loaded
102-
certificate files are named primary.pfx and secondary.pfx, in the LogZilla installation
103-
directory (default c:\Program Files\Logzilla\SyslogAgent).
104-
If you do not have a .pfx file, but instead have .key and .crt files, if you have access
105-
to a unix machine with openssl installed, you can use the following command to produce a
106-
.pfx file from the .key and .crt files:
97+
These buttons are used to select (PFX format) certificate files for the
98+
TLS communications to the primary or secondary server. If you are using
99+
HTTPS/SSL and are not using a Certificate Authority (CA) to sign the
100+
certificate, you must provide the self-signed certificate files. When
101+
the button is clicked a window will pop up allowing selection of the
102+
file from which the cert is to be read. Please note that once the cert
103+
is read and imported (using the button) that certificate information is
104+
copied into the LogZilla settings and the source cert file is no longer
105+
used. The loaded certificate files are named primary.pfx and
106+
secondary.pfx, in the LogZilla installation directory (default
107+
c:\Program Files\Logzilla\SyslogAgent). If you do not have a .pfx file,
108+
but instead have .key and .crt files, if you have access to a unix
109+
machine with openssl installed, you can use the following command to
110+
produce a .pfx file from the .key and .crt files:
107111

108112
```
109113
root@agent-http # openssl pkcs12 -export -out cert.pfx -inkey cert.key\
@@ -155,7 +159,7 @@ The selected facility is included in all messages sent.
155159
By selecting `Dynamic`, the severity for each message is determined from the Windows
156160
event log type. Otherwise, the selected severity is included in all messages sent.
157161

158-
### Extra Key/Value Pairs
162+
### Extra Key/Values
159163

160164
This configures whether any supplemental key-value pairs will be included with the
161165
log messages, for processing by LogZilla rules. Key-value pairs should be separated
@@ -192,10 +196,6 @@ This configures the path and name of the file to which log messages will be save
192196
a path and directory are specified that specific combination will be used for the log
193197
file, otherwise, the log file will be saved in the directory with the SyslogAgent.exe file.
194198

195-
### Batch Interval
196-
197-
This setting is deprecated, leave it at the default value of 1000.
198-
199199
### File Watcher (tail)
200200

201201
The agent has the capability to "tail" a specified text file – this means that the agent

winagent/images/agent_config.png

100644100755
-3.85 KB
Loading

0 commit comments

Comments
 (0)