When connecting to a syslog-ng server using an encrypted connection, the syslog-ng Agent for Windows verifies the certificate of the server. The connection can be established only if the syslog-ng Agent for Windows can verify the certificate of the syslog server. For this, import one of the following certificates into the Certificate Store (
) of the Windows-based host:The certificate of the Certificate Authority (CA) that issued the certificate of the server
If your server uses a self-signed certificate, import the self-signed certificate
For details on importing certificates, see Procedure 6.3, “Importing certificates with the Microsoft Management Console”.
|
NOTE:
This certificate (sometimes also called the CACert of the server) is not the certificate of the server: it is the certificate of the CA that signed the certificate of the server. |
Procedure 6.1. Enabling encrypted connections
Purpose:
To enable SSL-encrypted connections to the server, complete the following steps:
Steps:
Start the configuration interface of the syslog-ng Agent for Windows application.
Select
.Right-click on the server that accepts encrypted connections and select
.Select the
option.
|
Caution:
The connection is established only if the syslog-ng Agent for Windows can verify the certificate of the syslog server. For this, import one of the following certificates into the Certificate Store ( ) of the Windows-based host:
For details on importing certificates, see Procedure 6.3, “Importing certificates with the Microsoft Management Console”. |
Click
.To compress the messages during transfer to save bandwidth, select the
option. Note that for syslog-ng Agent to actually use compression, the following points must be met.The
option must be enabled.You must use SSL and/or RLTP to send messages to the logserver (that is, at least one of the
or options must be enabled.The logserver must be configured to enable compression. If the logserver is syslog-ng PE the proper allow-compress()
option must be enabled in the source. If the logserver is syslog-ng Store Box, enable the option. Note that to send compressed messages to syslog-ng Store Box, you must use the RLTP™ protocol (for details, see the syslog-ng Documentation page).
Select
, then . To activate the changes, restart the syslog-ng Agent service.When the syslog-ng server is configured to use mutual authentication, it requests a certificate from the syslog-ng clients. The syslog-ng Agent application can automatically show the requested certificate to the server when the connection is established, provided it is available in the Procedure 6.3, “Importing certificates with the Microsoft Management Console”.
store ( ) of the Local Computer. Use the to import this certificate. For details, seeProcedure 6.2. Configuring mutual authentication with the syslog-ng Agent for Windows
Purpose:
If the syslog-ng server requests authentication from the syslog-ng Agent, complete the following steps.
Steps:
Create certificates for the clients. By default, the syslog-ng Agent will look for a certificate that contains the hostname or IP address of the central syslog-ng server in its Common Name. If you use a different Common Name, do not forget to complete Step 3 to set the Common Name of the certificate.
The certificate must contain the private key and must be in PKCS12 format.
|
TIP:
To convert a certificate and a key from PEM format to PKCS12 you can use the following command: openssl pkcs12 -export -in agentcertificate.pem -inkey agentprivatekey.pem -out agentcertificatewithkey.pfx |
Import this certificate into the Procedure 6.3, “Importing certificates with the Microsoft Management Console”.
store of the Local Computer using the Certificate Import Wizard. For details, seeBy default, the syslog-ng Agent will look for a certificate that contains the hostname or IP address of the central syslog-ng server in its Common Name. (The agent will look for the server name or address set in the
field of the destination.) If the certificate of the client has a different Common Name, complete the following steps:Start the configuration interface of the syslog-ng Agent for Windows application.
Select
.Right-click on the server that requires mutual authentication and select
.Select the
option, click , then select the certificate to use. You can also type the Common Name of the certificate into the field.If you have more than one certificates with the same Common Name, alternatively, you can type the Distinguished Name (DN) of the certificate into the US, Maryland, Pasadena, Example Inc, Sample Department, mycommonname
Select
, then . To activate the changes, restart the syslog-ng Agent service.Procedure 6.3. Importing certificates with the Microsoft Management Console
Purpose:
To import a certificate, complete the following steps.
Steps:
Start Microsoft Management Console by executing mmc.exe
( menu ).
|
NOTE:
Running |
Click on the
item of the menu.Click
, select the module, and click .Select
in the displayed window and click .Select
and click .To import the CA certificate of the syslog-ng server's certificate, navigate to
.To import a certificate for the syslog-ng Agent to perform mutual authentication, navigate to
.Right-click on the
folder and from the appearing menu select . The will be displayed. Click .Optional step: Certificates used to authenticate the syslog-ng Agent in mutual authentication include the private key. Provide the password for the private key when requested.
Windows offers a suitable certificate store by default, so click
.Click
on the summary window and on the window that marks the successful importing of the certificate.© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center