Call sequence: slogkey --master-ḱey <filename>

<filename>: The name of the file to which the master key will be written.

Call sequence: slogkey --derive-key <master key file> <host MAC address> <host serial number> <host key file>

<master key file>: The master key from which the host key will be derived.

<host MAC address>: The MAC address of the host on which the key will be used. Instead of the MAC address, any other string that uniquely identifies a host can be supplied, e.g. the company inventory number.

<host serial number>: The serial number of the host on which the key will be used. Instead of the serial number, any other string that uniquely identifies a host can be supplied, e.g. the company inventory number.

<host key file>: The name of the file to which the host key will be written.

NOTE: The newly created host key has its counter set to 0 indicating that it represents the initial host key k0. This host key must be kept secret and not be disclosed to third parties. It will be required to successfully decrypt and verify log archives processed by the secure logging environment. As each log entry will be encrypted with its own key, a new host key will be created after successful processing of a log entry and will replace the previous key. Therefore, the initial host key needs to be stored in a safe place before starting the secure logging environment, as it will be deleted from the log host after processing of the first log entry.

Call sequence: slogkey --counter <host key file>

<host key file>: The host key file from which the sequence will be read.

Generates a mew master key. <filename> is the name of the file storing the newly generated master key.

Derive a host key using a previously generated master key.

Display the current log sequence counter of a key.

Display a help message.

Note

For the detailed documentation of see The syslog-ng Administrator Guide[1]

If you experience any problems or need help with syslog-ng, visit the syslog-ng mailing list[2].

For news and notifications about of syslog-ng, visit the syslog-ng blogs[3].

For specific information requests related to secure logging send a mail to the Airbus Secure Logging Team <secure-logging@airbus.com>.