Damit der Daemon beim Hochfahren unseres Servers automatisch gestartet wird, nutzen wir folgenden Befehl.

 # systemctl enable elasticsearch.service

Created symlink from /etc/systemd/system/multi-user.target.wants/elasticsearch.service to /usr/lib/systemd/system/elasticsearch.service.

Wollen wir wissen, ob die Autostartfunktion bereits gesetzt ist, verwenden wir diesen Aufruf.

 # systemctl is-enabled elasticsearch.service

enabled

Zum Testen unserer Konfigurationseinstellungen nutzen wir die Nodes Info API.

 # curl localhost:9200/_nodes/process?pretty

{
  "cluster_name" : "graylog",
  "nodes" : {
    "EdAnadZuTiOjxFR7_Kvdrg" : {
      "name" : "vml000117",
      "transport_address" : "inet[/10.0.0.117:9300]",
      "host" : "vml000117.dmz.nausch.org",
      "ip" : "10.0.0.117",
      "version" : "1.7.4",
      "build" : "0d3159b",
      "http_address" : "inet[/10.0.0.117:9200]",
      "process" : {
        "refresh_interval_in_millis" : 1000,
        "id" : 32221,
        "max_file_descriptors" : 65535,
        "mlockall" : true
      }
    }
  }
}

Den Zustand des elastic-Servers kann man sich mit folgendem Aufruf anzeigen lassen.

 # curl localhost:9200/_cluster/health?pretty

{
  "cluster_name" : "graylog",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 2,
  "active_shards" : 2,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0
}

Nachdem wir alle Vorbereitungen erfolgreich abgeschlossen haben, können wir uns nun der Konfiguration des graylog-server Daemons widmen.

Auf unserem System unter CentOS 7.x hatten wir als JAVA Runtime Enviroment das Paket openjdk in der Version 1.8 installiert. Ab Version 1.8 werden die beiden Parameter PermSize und MaxPermSize nicht mehr unterstützt. Wir werden daher in der Konfigurationsdatei /etc/sysconfig/graylog-server diese beiden Parameter bei den GRAYLOG_SERVERGRAYLOG_SERVER_JAVA_OPTS entfernen.

 # vim /etc/sysconfig/graylog-server

/etc/sysconfig/graylog-server

# Path to the java executable.
JAVA=/usr/bin/java
 
# Default Java options for heap and garbage collection.
#
# Django : 2015-12-28 - PermSize und MaxPermSize werden ab openjdk-1.8.0 nicht mehr unterstützt
# default: GRAYLOG_SERVER_JAVA_OPTS="-Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow"
GRAYLOG_SERVER_JAVA_OPTS="-Xms1g -Xmx1g -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow"
 
# Pass some extra args to graylog-server. (i.e. "-d" to enable debug mode)
GRAYLOG_SERVER_ARGS=""
 
# Program that will be used to wrap the graylog-server command. Useful to
# support programs like authbind.
GRAYLOG_COMMAND_WRAPPER=""

Die eigentliche Konfiguration unseres graylog-Servers wird in dessen Konfigurationsdatei /etc/graylog/server/server.conf vorgenommen.

Bevor wir diese öffnen und bearbeiten, erstellen wir uns noch zwei Dinge:

1. Passwort-Hash
   Mit Hilfe des Passwort-Hash werden die Nutzerpassworte verschlüsselt. Diesen hash-Wert erstellen wir wie folgt:

    # pwgen -N 1 -s 128

   yCWAd48fvOmR7xAmcKezZ2C0v3mtaXCJjA7NfhBlSf98PTxHrf9SrCQDX2xgjCzrHpxoV5UNOEfQZsOP1gkWkYlDarD75tbtztPhR59O70yZchaJcyQTeHBZllQc8RcT

2. Admin-Passwort
   Der administrative Benutzer admin benötigt noch ein zugehöriges Passwort, erzeugen wir nun mit folgendem Befehl.

   # echo -n N3v3r7ru57Y0URg0v3rnm3n7 | sha256sum

   38337fd07fd4ee02548053d7bed3ee33e3e0c593c2802941e2349fc52e80b98d  -

Diese beiden Werte hinterlegen wir nun in der Konfigurationsdatei unseres graylog-Daemon und passen anschließend die Konfigurationsoptionen unserer Umgebung an. Änderungen an den Default-Werten sind mit Django : <Zeitstempel> gekennzeichnet

 # vim /etc/graylog/server/server.conf

/etc/graylog/server/server.conf

# If you are running more than one instances of graylog2-server you have to select one of these
# instances as master. The master will perform some periodical tasks that non-masters won't perform.
is_master = true                                                                                    
 
# The auto-generated node ID will be stored in this file and read after restarts. It is a good idea
# to use an absolute file path here if you are starting graylog2-server from init scripts or similar.
node_id_file = /etc/graylog/server/node-id                                                           
 
# You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters.
# Generate one by using for example: pwgen -N 1 -s 96                                               
# Django : 2015-12-28                                                                               
# default: password_secret =                                                                        
password_secret = yCWAd48fvOmR7xAmcKezZ2C0v3mtaXCJjA7NfhBlSf98PTxHrf9SrCQDX2xgjCzrHpxoV5UNOEfQZsOP1gkWkYlDarD75tbtztPhR59O70yZchaJcyQTeHBZllQc8RcT
 
# The default root user is named 'admin'
# Django : 2015-12-28                   
# default: #root_username = admin       
root_username = admin                   
 
# You MUST specify a hash password for the root user (which you only need to initially set up the
# system and in case you lose connectivity to your authentication backend)                       
# This password cannot be changed using the API or via the web interface. If you need to change it,
# modify it in this file.                                                                          
# Create one by using for example: echo -n yourpassword | shasum -a 256                            
# and put the resulting hash value into the following line                                         
# Django : 2015-12-28                                                                              
# default: root_password_sha2 =                                                                    
root_password_sha2 = 38337fd07fd4ee02548053d7bed3ee33e3e0c593c2802941e2349fc52e80b98d     
 
# The email address of the root user.
# Default is empty                   
# Django : 2015-12-28                
# default: #root_email = ""          
root_email = "graylog_admin@nausch.org"
 
# The time zone setting of the root user.
# The configured time zone must be parseable by http://www.joda.org/joda-time/apidocs/org/joda/time/DateTimeZone.html#forID-java.lang.String-
# Default is UTC                                                                                                                             
# Django : 2015-12-28                                                                                                                        
# default: #root_timezone = UTC                                                                                                              
root_timezone = Europe/Berlin                                                                                                                
 
# Set plugin directory here (relative or absolute)
plugin_dir = /usr/share/graylog-server/plugin     
 
# REST API listen URI. Must be reachable by other graylog2-server nodes if you run a cluster.
rest_listen_uri = http://127.0.0.1:12900/                                                    
 
# REST API transport address. Defaults to the value of rest_listen_uri. Exception: If rest_listen_uri
# is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 system address is used.      
# If set, his will be promoted in the cluster discovery APIs, so other nodes may try to connect on   
# this address and it is used to generate URLs addressing entities in the REST API. (see rest_listen_uri)
# You will need to define this, if your Graylog server is running behind a HTTP proxy that is rewriting  
# the scheme, host name or URI.                                                                          
#rest_transport_uri = http://192.168.1.1:12900/                                                          
# Django : 2015-12-28                                                                                    
# default: unset                                                                                         
rest_transport_uri = http://127.0.0.1:12900/                                                             
 
# Enable CORS headers for REST API. This is necessary for JS-clients accessing the server directly.
# If these are disabled, modern browsers will not be able to retrieve resources from the server.   
# This is disabled by default. Uncomment the next line to enable it.                               
#rest_enable_cors = true                                                                           
# Django : 2015-12-28                                                                              
# default: unset                                                                                   
rest_enable_cors = true                                                                            
 
# Enable GZIP support for REST API. This compresses API responses and therefore helps to reduce
# overall round trip times. This is disabled by default. Uncomment the next line to enable it. 
#rest_enable_gzip = true                                                                       
# Django : 2015-12-28                                                                          
# default: unset                                                                               
rest_enable_gzip = true                                                                        
 
# Enable HTTPS support for the REST API. This secures the communication with the REST API with
# TLS to prevent request forgery and eavesdropping. This is disabled by default. Uncomment the
# next line to enable it.                                                                     
#rest_enable_tls = true                                                                       
 
# The X.509 certificate file to use for securing the REST API.
#rest_tls_cert_file = /path/to/graylog2.crt                   
 
# The private key to use for securing the REST API.
#rest_tls_key_file = /path/to/graylog2.key         
 
# The password to unlock the private key used for securing the REST API.
#rest_tls_key_password = secret                                         
 
# The maximum size of a single HTTP chunk in bytes.
#rest_max_chunk_size = 8192                        
 
# The maximum size of the HTTP request headers in bytes.
#rest_max_header_size = 8192                            
 
# The maximal length of the initial HTTP/1.1 line in bytes.
#rest_max_initial_line_length = 4096                       
 
# The size of the execution handler thread pool used exclusively for serving the REST API.
#rest_thread_pool_size = 16                                                               
 
# The size of the worker thread pool used exclusively for serving the REST API.
#rest_worker_threads_max_pool_size = 16                                        
 
# Embedded Elasticsearch configuration file
# pay attention to the working directory of the server, maybe use an absolute path here
#elasticsearch_config_file = /etc/graylog/server/elasticsearch.yml                     
 
# Graylog will use multiple indices to store documents in. You can configured the strategy it uses to determine
# when to rotate the currently active write index.                                                             
# It supports multiple rotation strategies:                                                                    
#   - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure                   
#   - "size" per index, use elasticsearch_max_size_per_index below to configure                                
# valid values are "count", "size" and "time", default is "count"                                              
# Django : 2015-12-28                                                                                          
# default: rotation_strategy = count                                                                           
rotation_strategy = time                                                                                       
 
# (Approximate) maximum number of documents in an Elasticsearch index before a new index
# is being created, also see no_retention and elasticsearch_max_number_of_indices.      
# Configure this if you used 'rotation_strategy = count' above.                         
# Django : 2015-12-28                                                                   
# default: elasticsearch_max_docs_per_index = 20000000                                  
 
# (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see
# no_retention and elasticsearch_max_number_of_indices. Default is 1GB.                                            
# Configure this if you used 'rotation_strategy = size' above.                                                     
#elasticsearch_max_size_per_index = 1073741824                                                                     
 
# (Approximate) maximum time before a new Elasticsearch index is being created, also see
# no_retention and elasticsearch_max_number_of_indices. Default is 1 day.               
# Configure this if you used 'rotation_strategy = time' above.                          
# Please note that this rotation period does not look at the time specified in the received messages, but is
# using the real clock value to decide when to rotate the index!                                            
# Specify the time using a duration and a suffix indicating which unit you want:                            
#  1w  = 1 week                                                                                             
#  1d  = 1 day                                                                                              
#  12h = 12 hours                                                                                           
# Permitted suffixes are: d for day, h for hour, m for minute, s for second.                                
#elasticsearch_max_time_per_index = 1d                                                                      
# Django : 2015-12-28                                                                                       
# default: unset                                                                                            
elasticsearch_max_time_per_index = 1d                                                                       
 
# Disable checking the version of Elasticsearch for being compatible with this Graylog release.
# WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss!
#elasticsearch_disable_version_check = true                                                            
 
# Disable message retention on this node, i. e. disable Elasticsearch index rotation.
#no_retention = false                                                                
 
# How many indices do you want to keep?
# Django : 2015-12-28                  
# default: elasticsearch_max_number_of_indices = 20
elasticsearch_max_number_of_indices = 30           
 
# Decide what happens with the oldest indices when the maximum number of indices is reached.
# The following strategies are availble:                                                    
#   - delete # Deletes the index completely (Default)                                       
#   - close # Closes the index and hides it from the system. Can be re-opened later.        
retention_strategy = delete                                                                 
 
# How many Elasticsearch shards and replicas should be used per index? Note that this only applies to newly created indices.
# Django : 2015-12-28                                                                                                       
# default: elasticsearch_shards = 4                                                                                         
elasticsearch_shards = 1                                                                                                    
elasticsearch_replicas = 0                                                                                                  
 
 
# Prefix for all Elasticsearch indices and index aliases managed by Graylog.
# Django : 2015-12-28                                                       
# default: elasticsearch_index_prefix = graylog2                            
elasticsearch_index_prefix = graylog                                        
 
# Name of the Elasticsearch index template used by Graylog to apply the mandatory index mapping.
# # Default: graylog-internal                                                                   
#elasticsearch_template_name = graylog-internal                                                 
 
# Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only
# be enabled with care. See also: https://www.graylog.org/documentation/general/queries/                     
allow_leading_wildcard_searches = false                                                                      
 
# Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and
# should only be enabled after making sure your Elasticsearch cluster has enough memory.                               
allow_highlighting = false                                                                                             
 
# settings to be passed to elasticsearch's client (overriding those in the provided elasticsearch_config_file)
# all these                                                                                                   
# this must be the same as for your Elasticsearch cluster                                                     
#elasticsearch_cluster_name = graylog2                                                                        
# Django : 2015-12-28                                                                                         
# default: unset                                                                                              
elasticsearch_cluster_name = graylog                                                                          
 
# you could also leave this out, but makes it easier to identify the graylog2 client instance
#elasticsearch_node_name = graylog2-server                                                   
# Django : 2015-12-28                                                                        
# default: unset                                                                             
elasticsearch_node_name = vml000117                                                          
 
# we don't want the graylog2 server to store any data, or be master node
# Django : 2015-12-28                                                   
# default: #elasticsearch_node_master = false                           
#          #elasticsearch_node_data = false                             
elasticsearch_node_master = false                                       
elasticsearch_node_data = false                                         
 
# use a different port if you run multiple Elasticsearch nodes on one machine
#elasticsearch_transport_tcp_port = 9350                                     
 
# we don't need to run the embedded HTTP server here
# Django : 2015-12-28                               
# default: #elasticsearch_http_enabled = false      
elasticsearch_http_enabled = false                  
 
# Django : 2015-12-28
# default: #elasticsearch_discovery_zen_ping_multicast_enabled = false
elasticsearch_discovery_zen_ping_multicast_enabled = false            
 
# Django : 2015-12-28
# default: #elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300            
 
# Change the following setting if you are running into problems with timeouts during Elasticsearch cluster discovery.
# The setting is specified in milliseconds, the default is 5000ms (5 seconds).                                       
#elasticsearch_cluster_discovery_timeout = 5000                                                                      
 
# the following settings allow to change the bind addresses for the Elasticsearch client in graylog2
# these settings are empty by default, letting Elasticsearch choose automatically,                  
# override them here or in the 'elasticsearch_config_file' if you need to bind to a special address 
# refer to http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/modules-network.html  
# for special values here                                                                           
#elasticsearch_network_host =                                                                       
#elasticsearch_network_bind_host =                                                                  
#elasticsearch_network_publish_host =                                                               
 
# The total amount of time discovery will look for other Elasticsearch nodes in the cluster
# before giving up and declaring the current node master.                                  
#elasticsearch_discovery_initial_state_timeout = 3s                                        
 
# Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea.
# All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom
# Elasticsearch documentation: http://www.elasticsearch.org/guide/reference/index-modules/analysis/            
# Note that this setting only takes effect on newly created indices.                                           
elasticsearch_analyzer = standard                                                                              
 
# Global request timeout for Elasticsearch requests (e. g. during search, index creation, or index time-range
# calculations) based on a best-effort to restrict the runtime of Elasticsearch operations.                  
# Default: 1m                                                                                                
#elasticsearch_request_timeout = 1m                                                                          
 
# Time interval for index range information cleanups. This setting defines how often stale index range information
# is being purged from the database.                                                                              
# Default: 1h                                                                                                     
#index_ranges_cleanup_interval = 1h                                                                               
 
# Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output
# module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been
# reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember 
# that every outputbuffer processor manages its own batch and performs its own batch write calls.              
# ("outputbuffer_processors" variable)                                                                         
output_batch_size = 500                                                                                        
 
# Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two
# batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages
# for this time period is less than output_batch_size * outputbuffer_processors.                              
output_flush_interval = 1                                                                                     
 
# As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and
# over again. To prevent this, the following configuration options define after how many faults an output will
# not be tried again for an also configurable amount of seconds.                                              
output_fault_count_threshold = 5                                                                              
output_fault_penalty_seconds = 30                                                                             
 
# The number of parallel running processors.
# Raise this number if your buffers are filling up.
processbuffer_processors = 5                       
outputbuffer_processors = 3                        
 
#outputbuffer_processor_keep_alive_time = 5000
#outputbuffer_processor_threads_core_pool_size = 3
#outputbuffer_processor_threads_max_pool_size = 30
 
# UDP receive buffer size for all message inputs (e. g. SyslogUDPInput).
#udp_recvbuffer_sizes = 1048576                                         
 
# Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping)
# Possible types:                                                                              
#  - yielding                                                                                  
#     Compromise between performance and CPU usage.                                            
#  - sleeping                                                                                  
#     Compromise between performance and CPU usage. Latency spikes can occur after quiet periods.
#  - blocking                                                                                    
#     High throughput, low latency, higher CPU usage.                                            
#  - busy_spinning                                                                               
#     Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores.
processor_wait_strategy = blocking                                                                               
 
# Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore.
# For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache.
# Start server with --statistics flag to see buffer utilization.                                     
# Must be a power of 2. (512, 1024, 2048, ...)                                                       
ring_size = 65536                                                                                    
 
inputbuffer_ring_size = 65536
inputbuffer_processors = 2   
inputbuffer_wait_strategy = blocking
 
# Enable the disk based message journal.
message_journal_enabled = true          
 
# The directory which will be used to store the message journal. The directory must me exclusively used by Graylog and
# must not contain any other files than the ones created by Graylog itself.                                           
message_journal_dir = /var/lib/graylog-server/journal                                                                 
 
# Journal hold messages before they could be written to Elasticsearch.
# For a maximum of 12 hours or 5 GB whichever happens first.          
# During normal operation the journal will be smaller.                
#message_journal_max_age = 12h                                        
#message_journal_max_size = 5gb                                       
 
#message_journal_flush_age = 1m
#message_journal_flush_interval = 1000000
#message_journal_segment_age = 1h        
#message_journal_segment_size = 100mb    
 
# Number of threads used exclusively for dispatching internal events. Default is 2.
#async_eventbus_processors = 2                                                     
 
# EXPERIMENTAL: Dead Letters
# Every failed indexing attempt is logged by default and made visible in the web-interface. You can enable
# the experimental dead letters feature to write every message that was not successfully indexed into the 
# MongoDB "dead_letters" collection to make sure that you never lose a message. The actual writing of dead
# letter should work fine already but it is not heavily tested yet and will get more features in future   
# releases.                                                                                               
dead_letters_enabled = false                                                                              
 
# How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual
# shutdown process. Set to 0 if you have no status checking load balancers in front.                       
lb_recognition_period_seconds = 3                                                                          
 
# Every message is matched against the configured streams and it can happen that a stream contains rules which
# take an unusual amount of time to run, for example if its using regular expressions that perform excessive backtracking.
# This will impact the processing of the entire server. To keep such misbehaving stream rules from impacting other        
# streams, Graylog limits the execution time for each stream.                                                             
# The default values are noted below, the timeout is in milliseconds.                                                     
# If the stream matching for one stream took longer than the timeout value, and this happened more than "max_faults" times
# that stream is disabled and a notification is shown in the web interface.                                               
#stream_processing_timeout = 2000                                                                                         
#stream_processing_max_faults = 3                                                                                         
 
# Length of the interval in seconds in which the alert conditions for all streams should be checked
# and alarms are being sent.                                                                       
#alert_check_interval = 60                                                                         
 
# Since 0.21 the graylog2 server supports pluggable output modules. This means a single message can be written to multiple
# outputs. The next setting defines the timeout for a single output module, including the default output module where all 
# messages end up.                                                                                                        
#                                                                                                                         
# Time in milliseconds to wait for all message outputs to finish writing a single message.                                
#output_module_timeout = 10000                                                                                            
 
# Time in milliseconds after which a detected stale master node is being rechecked on startup.
#stale_master_timeout = 2000                                                                  
 
# Time in milliseconds which Graylog is waiting for all threads to stop on shutdown.
#shutdown_timeout = 30000                                                           
 
# MongoDB connection string
# See http://docs.mongodb.org/manual/reference/connection-string/ for details
# Django : 2015-12-28                                                        
# default: mongodb_uri = mongodb://localhost/graylog2                        
mongodb_uri = mongodb://graylog-user:R7xAmcKezZ2C0v3mtaXCJjA7Nf@127.0.0.1:27017/graylog
 
# Authenticate against the MongoDB server
#mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog2
 
# Use a replica set instead of a single host
#mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog2
 
# Increase this value according to the maximum connections your MongoDB server can handle from a single client
# if you encounter MongoDB connection problems.                                                               
mongodb_max_connections = 100                                                                                 
 
# Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5
# If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5,
# then 500 threads can block. More than that and an exception will be thrown.             
# http://api.mongodb.org/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier
mongodb_threads_allowed_to_block_multiplier = 5                                                                 
 
# Drools Rule File (Use to rewrite incoming log messages)
# See: https://www.graylog.org/documentation/general/rewriting/
#rules_file = /etc/graylog/server/rules.drl                    
 
# Email transport
#transport_email_enabled = false
#transport_email_hostname = mail.example.com
#transport_email_port = 587                 
#transport_email_use_auth = true            
#transport_email_use_tls = true             
#transport_email_use_ssl = true             
#transport_email_auth_username = you@example.com
#transport_email_auth_password = secret         
#transport_email_subject_prefix = [graylog2]    
#transport_email_from_email = graylog2@example.com
#                                                 
# Django : 2015-12-28                             
# default: unset                                  
transport_email_enabled = true                    
transport_email_hostname = smtp.dmz.nausch.org    
transport_email_port = 25                         
transport_email_use_auth = false                  
transport_email_use_tls = false                   
transport_email_use_ssl = false                   
transport_email_auth_username = graylog-admin@nausch.org
transport_email_auth_password = 6zmNsgdrD4x1!                
transport_email_subject_prefix = [graylog]              
transport_email_from_email = graylog-admin@nausch.org   
 
# Specify and uncomment this if you want to include links to the stream in your stream alert mails.
# This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users.
#transport_email_web_interface_url = https://graylog2.example.com                                                            
# Django : 2015-12-28                                                                                                        
# default: transport_email_web_interface_url = https://graylog2.example.com                                                  
transport_email_web_interface_url = https://panopticon.nausch.org                                                            
 
# The default connect timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 5s
#http_connect_timeout = 5s
 
# The default read timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_read_timeout = 10s
 
# The default write timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_write_timeout = 10s
 
# HTTP proxy for outgoing HTTP connections
#http_proxy_uri =
 
# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
# cycled indices.
#disable_index_optimization = true
 
# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch
# on heavily used systems with large indices, but it will decrease search performance. The default is 1.
#index_optimization_max_num_segments = 1
 
# The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification
# will be generated to warn the administrator about possible problems with the system. Default is 1 second.
#gc_warning_threshold = 1s
 
# Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
#ldap_connection_timeout = 2000
 
# Enable collection of Graylog-related metrics into MongoDB
# WARNING: This will add *a lot* of data into your MongoDB database on a regular interval (1 second)!
# DEPRECATED: This setting and the respective feature will be removed in a future version of Graylog.
#enable_metrics_collection = false
 
# Disable the use of SIGAR for collecting system stats
#disable_sigar = false
 
# Amount of time of inactivity after which collectors are flagged as inactive (Default: 1 minute)
#collector_inactive_threshold = 1m
 
# Amount of time after which inactive collectors are purged (Default: 14 days)
#collector_expiration_threshold = 14d
 
# The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second)
#dashboard_widget_default_cache_time = 10s
 
# Automatically load content packs in "content_packs_dir" on the first start of Graylog.
#content_packs_loader_enabled = true
 
# The directory which contains content packs which should be loaded on the first start of Graylog.
content_packs_dir = /usr/share/graylog-server/contentpacks
 
# A comma-separated list of content packs (files in "content_packs_dir") which should be applied on
# the first start of Graylog.
content_packs_auto_load = grok-patterns.json

Unsere Konfigurationsänderungen werden mit Hilfe von mongo der MongoDB Shell vorgenommen. Dieses JavaScript stellt die Benutzerschnittstelle zum eigentlichen MongoDN-Daemon zur Verfügung. Damit sich der Client mit dem Server auch verbinden kann, muss der Server natürlich laufen; wir starten also nun unsere NoSQL-Datenbank mit folgendem Befehl.

 # systemctl start graylog-server.service

Den Serverstatus können wir wie folgt abfragen.

 # systemctl status graylog-server.service

● graylog-server.service - Graylog server
   Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2015-12-28 14:27:40 CET; 6s ago
     Docs: http://docs.graylog.org/
 Main PID: 5057 (graylog-server)
   CGroup: /system.slice/graylog-server.service
           ├─5057 /bin/sh /usr/share/graylog-server/bin/graylog-server
           └─5058 /usr/bin/java -Xms1g -Xmx1g -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UsePa...

Dec 28 14:27:40 vml000117.dmz.nausch.org systemd[1]: Started Graylog server.
Dec 28 14:27:40 vml000117.dmz.nausch.org systemd[1]: Starting Graylog server...

 # /var/log/elasticsearch/elasticsearch.log

Dec 28 14:27:40 vml000117.dmz.nausch.org systemd[1]: Started Graylog server.
Dec 28 14:27:40 vml000117.dmz.nausch.org systemd[1]: Starting Graylog server...
[root@vml000117 yum.repos.d]# tailf /var/log/graylog-server/server.log
2015-12-28T14:27:55.595+01:00 INFO  [discovery] [vml000117] graylog/j4zrCy-gQpqKTAMqM_XGkg
2015-12-28T14:27:55.609+01:00 INFO  [RestApiService] Enabling CORS for REST API
2015-12-28T14:27:58.627+01:00 WARN  [discovery] [vml000117] waited for 3s and no initial state was set by the discovery
2015-12-28T14:27:58.627+01:00 INFO  [node] [vml000117] started
2015-12-28T14:27:59.138+01:00 INFO  [service] [vml000117] detected_master [vml000117][EdAnadZuTiOjxFR7_Kvdrg][vml000117.dmz.nausch.org][inet[/10.0.0.117:9300]], added {[vml000117][EdAnadZuTiOjxFR7_Kvdrg][vml000117.dmz.nausch.org][inet[/10.0.0.117:9300]],}, reason: zen-disco-receive(from master [[vml000117][EdAnadZuTiOjxFR7_Kvdrg][vml000117.dmz.nausch.org][inet[/10.0.0.117:9300]]])
2015-12-28T14:28:05.324+01:00 INFO  [IndexRotationThread] Deflector index <graylog_1> should be rotated, Pointing deflector to new index now!
2015-12-28T14:28:05.324+01:00 INFO  [Deflector] Cycling deflector to next index now.
2015-12-28T14:28:05.340+01:00 INFO  [Deflector] Cycling from <graylog_1> to <graylog_2>
2015-12-28T14:28:05.340+01:00 INFO  [Deflector] Creating index target <graylog_2>...
2015-12-28T14:28:06.218+01:00 INFO  [Deflector] Waiting for index allocation of <graylog_2>
2015-12-28T14:28:06.335+01:00 INFO  [Deflector] Done!
2015-12-28T14:28:06.335+01:00 INFO  [Deflector] Pointing deflector to new target index....
2015-12-28T14:28:06.531+01:00 INFO  [SystemJobManager] Submitted SystemJob <d4502600-ad66-11e5-8de7-5254005fa52f> [org.graylog2.indexer.ranges.CreateNewSingleIndexRangeJob]
2015-12-28T14:28:06.537+01:00 INFO  [CreateNewSingleIndexRangeJob] Calculating ranges for index graylog_1.
2015-12-28T14:28:06.610+01:00 INFO  [SystemJobManager] Submitted SystemJob <d4557d30-ad66-11e5-8de7-5254005fa52f> [org.graylog2.indexer.SetIndexReadOnlyJob]
2015-12-28T14:28:06.658+01:00 INFO  [SystemJobManager] Submitted SystemJob <d461b230-ad66-11e5-8de7-5254005fa52f> [org.graylog2.indexer.ranges.CreateNewSingleIndexRangeJob]
2015-12-28T14:28:06.658+01:00 INFO  [Deflector] Done!
2015-12-28T14:28:06.618+01:00 INFO  [CreateNewSingleIndexRangeJob] Calculating ranges for index graylog_2.
2015-12-28T14:28:06.720+01:00 INFO  [MongoIndexRangeService] Calculated range of [graylog_1] in [182ms].
2015-12-28T14:28:06.807+01:00 INFO  [CreateNewSingleIndexRangeJob] Created ranges for index graylog_1.
2015-12-28T14:28:06.807+01:00 INFO  [SystemJobManager] SystemJob <d4502600-ad66-11e5-8de7-5254005fa52f> [org.graylog2.indexer.ranges.CreateNewSingleIndexRangeJob] finished in 269ms.
2015-12-28T14:28:06.879+01:00 INFO  [MongoIndexRangeService] Calculated range of [graylog_2] in [180ms].
2015-12-28T14:28:06.930+01:00 INFO  [CreateNewSingleIndexRangeJob] Created ranges for index graylog_2.
2015-12-28T14:28:06.931+01:00 INFO  [SystemJobManager] SystemJob <d461b230-ad66-11e5-8de7-5254005fa52f> [org.graylog2.indexer.ranges.CreateNewSingleIndexRangeJob] finished in 312ms.
2015-12-28T14:28:08.315+01:00 INFO  [RestApiService] Adding security context factory: <org.graylog2.security.ShiroSecurityContextFactory@79ffbf1a>
2015-12-28T14:28:08.354+01:00 INFO  [RestApiService] Started REST API at <http://127.0.0.1:12900/>
2015-12-28T14:28:08.355+01:00 INFO  [ServiceManagerListener] Services are healthy
2015-12-28T14:28:08.357+01:00 INFO  [ServerBootstrap] Services started, startup times in ms: {InputSetupService [RUNNING]=5, OutputSetupService [RUNNING]=32, BufferSynchronizerService [RUNNING]=33, MetricsReporterService [RUNNING]=36, JournalReader [RUNNING]=45, KafkaJournal [RUNNING]=45, PeriodicalsService [RUNNING]=304, IndexerSetupService [RUNNING]=4286, RestApiService [RUNNING]=13364}
2015-12-28T14:28:08.360+01:00 INFO  [ServerBootstrap] Graylog server up and running.
2015-12-28T14:28:08.361+01:00 INFO  [InputSetupService] Triggering launching persisted inputs, node transitioned from Uninitialized [LB:DEAD] to Running [LB:ALIVE]

# openssl genrsa -out /etc/pki/tls/serverkey.pem -aes256 4096

Generating RSA private key, 4096 bit long modulus
.......................................................................................................................................................................................................................++
........................................................................................................................................................................................++
e is 65537 (0x10001)
Enter pass phrase for serverkey.pem: 12qwasyx
Verifying - Enter pass phrase for serverkey.pem: 12qwasyx

Wie schon erwähnt, entfernen wir die Passphrase nun wieder, in dem wir bei der Frage Enter pass phrase: einfach die Taste [ENTER] drücken.

# openssl rsa -in /etc/pki/tls/serverkey.pem -out /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem

Enter pass phrase:
writing RSA key

Wie schon zuvor schützen wir auch hier den Serverschlüssel über die Dateirechte.

# chmod 400 /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem

Da wir die Schlüsseldatei mit der unsicheren Passphrase nicht mehr benötigen, vernichten wir die zugehörige Datei.

# shred -u /etc/pki/tls/serverkey.pem

2015-12-23T23:42:21.666+01:00 WARN  [AbstractNioSelector] Failed to initialize an accepted socket.
java.lang.IllegalArgumentException: Unsupported key type PKCS#1, please convert to PKCS#8

Wir konvertieren also noch den Schlüssel in das passende Format mit folgendem openssl Kommando.

# openssl pkcs8 -topk8 -in /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem \
          -inform pem -out /etc/pki/tls/private/graylog-server.dmz.nausch.org.key_pk8.pem -outform pem -nocrypt

Graylog selbst läuft mit den Nutzerrechten des Users graylog; wir müssen also auch noch dafür sorgen, dass der User graylog den Schlüssel auch lesen darf. Wir ändern daher die Berechtigungen wie folgt:

# chown graylog.root /etc/pki/tls/private/graylog-server.dmz.nausch.org.key_pk8.pem

Nachdem wir unseren privaten Schlüssel erzeugt haben, können wir uns nun unserem CSR⁹⁾ widmen. Wie schon zuvor, sind die Eingaben auch hier zur besseren Unterscheidung fett und kursiv in der Farbe blau und die Rückmeldungen in der Farbe grau gekennzeichnet.

# openssl req -new -key /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem \
              -out /etc/pki/tls/private/graylog-server.dmz.nausch.org.csr.pem -nodes

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:DE
State or Province Name (full name) []:Bayern
Locality Name (eg, city) [Default City]:Pliening
Organization Name (eg, company) [Default Company Ltd]:nausch.org
Organizational Unit Name (eg, section) []:IT-Monitoring
Common Name (eg, your name or your server's hostname) []:graylog-server.dmz.nausch.org
Email Address []:graylog-admin@nausch.org

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:

Möchten wir den Inhalt unseres Certificate Signing Request ausgeben und ansehen, verwenden wir den folgenden openssl-Aufruf.

 # openssl req -noout -text -in /etc/pki/tls/private/graylog-server.dmz.nausch.org.csr.pem

Certificate Request:
    Data:
        Version: 0 (0x0)
        Subject: C=DE, ST=Bayern, L=Pliening, O=nausch.org, OU=IT-Monitoring, CN=graylog-server.dmz.nausch.org/emailAddress=graylog-admin@nausch.org
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:a4:89:62:85:af:56:b3:04:0c:34:86:4a:e3:b8:
                    6a:f4:23:6c:7f:bc:4c:a6:4e:cd:2e:fe:38:ad:74:
                    19:a1:de:cb:36:fa:c4:b4:85:31:1e:62:05:a5:f5:
                    f5:f0:7b:94:69:21:b3:48:ae:27:1c:bd:bd:52:2f:
                    9b:ee:ad:cf:5f:fe:e4:0f:a4:8c:0a:91:e0:75:fd:
                    47:e9:11:35:94:bd:86:b5:9e:47:1c:f8:b7:13:c4:
                    60:68:b5:8f:2e:8f:0d:75:fe:7a:41:d8:e7:2b:1e:
                    cb:d7:f2:4f:99:e6:c1:d9:c3:df:07:3b:0b:e4:cd:
                    1f:c3:0b:39:7a:15:38:09:df:a8:29:3c:73:c5:e1:
                    58:50:1e:4b:ef:cb:3c:63:e6:be:d2:ab:54:b7:ce:
                    03:69:3b:1f:d5:80:5a:be:98:af:a3:c9:3f:a8:84:
                    44:21:5d:f5:36:e8:11:ae:3f:7d:51:29:80:51:64:
                    bd:96:ff:32:36:9c:66:1f:9c:8b:4a:f0:f4:0d:50:
                    2b:3b:ea:32:2f:1c:22:0f:ca:87:78:d5:1f:de:4c:
                    45:64:c4:42:ae:d3:bc:47:98:c5:19:15:17:db:d3:
                    e3:1d:4e:84:76:d2:ba:ab:db:97:03:ff:bf:01:d7:
                    21:46:56:09:16:52:58:38:64:d0:8a:9b:7e:ba:5f:
                    9b:ec:f9:67:37:70:66:aa:b2:be:f2:af:ca:70:da:
                    8f:6e:5b:1d:5f:fa:97:da:6e:bf:f3:fb:6b:33:58:
                    74:bd:68:90:7d:21:c2:d3:9c:31:37:f1:88:f8:95:
                    8c:6e:68:ce:6c:71:83:35:8b:97:d8:94:78:fa:d7:
                    d7:c5:bd:26:6f:30:28:ac:0c:08:5e:9b:98:f7:4c:
                    7b:48:8c:a8:3c:2a:9a:01:d0:51:7f:9d:8b:a3:5b:
                    09:a2:60:42:81:fc:18:c1:53:56:9f:78:d5:3b:96:
                    94:59:70:b7:44:a1:f9:8f:88:22:55:9e:e6:67:e4:
                    4f:b5:8b:dd:e2:7c:a7:09:b9:52:91:23:2b:7f:13:
                    5c:2b:f1:05:54:a6:a4:85:df:6c:fd:4e:0b:6f:96:
                    53:2a:01:e4:fa:af:2d:3e:af:93:c4:05:88:d4:be:
                    99:74:d1:be:b7:2d:e4:bc:20:3d:34:36:e4:0e:35:
                    fc:d3:71:58:60:ec:91:b7:2b:35:76:4d:ae:ea:49:
                    ac:4b:64:93:01:ce:3a:38:ea:38:8c:2f:5a:8e:af:
                    d3:7f:aa:e4:17:0a:87:e4:92:94:06:2f:ca:b9:67:
                    20:7d:dc:65:f1:ff:f7:2b:a8:8c:55:71:d4:26:e0:
                    c8:87:c8:1c:8f:0d:42:77:1c:8f:31:8a:b1:66:4c:
                    18:88:79
                Exponent: 65537 (0x10001)
        Attributes:
            a0:00
    Signature Algorithm: sha512WithRSAEncryption
         2b:35:c6:1e:b4:d6:d6:3d:91:60:1a:e1:05:f8:00:dc:82:e6:
         5b:4c:71:dc:3a:46:f2:8e:78:ba:3b:6c:2f:f7:fa:79:c5:e1:
         8c:82:08:bf:3c:69:77:57:b6:a5:39:73:63:2b:a1:04:5b:1c:
         24:c1:ba:55:59:d5:13:18:c1:88:02:e1:b1:82:c9:de:77:08:
         41:d1:1d:72:e2:67:21:25:e5:43:de:3c:2e:13:ed:bc:a5:d1:
         8d:d2:e5:71:37:b3:d1:4d:92:90:4f:71:b1:1f:e7:01:c0:66:
         8c:7a:7b:29:5f:2d:96:f6:9e:bb:77:56:23:3d:5e:76:56:13:
         db:1f:88:54:ce:58:f1:4b:bf:b3:b2:33:7f:b8:a8:79:2d:01:
         76:85:18:7f:7d:40:bf:da:05:cf:07:86:43:df:6f:58:56:f7:
         fc:a7:6c:b0:33:95:33:05:be:6f:d8:c0:cc:33:2f:3d:a0:a0:
         7e:0a:5b:27:98:47:ab:44:2c:2a:bb:29:4f:de:70:27:24:59:
         b4:d0:98:08:a8:c8:22:f3:fb:de:7d:d2:5a:e9:8c:8f:3f:c8:
         14:47:2b:7e:e3:82:89:98:f7:4c:11:39:59:a3:82:26:e9:24:
         e3:b2:9a:e0:73:11:01:aa:44:4f:12:6a:da:7e:ec:e8:6d:5d:
         fd:66:04:3f:f6:d6:2e:07:64:1d:3f:38:56:b4:6e:28:73:6a:
         e8:57:ca:27:99:12:51:17:03:f5:41:02:de:ba:b0:cb:29:8e:
         28:eb:2b:61:81:9e:8f:d3:aa:9c:63:d5:e4:09:e0:1c:43:96:
         3a:95:60:62:69:d2:38:45:ad:e2:26:0a:83:3c:13:16:e1:53:
         8d:bc:e1:9e:6f:8a:a5:fd:c1:ac:8e:8b:01:66:e8:ff:51:8c:
         a0:c1:82:7c:2b:60:09:be:12:72:8b:a7:f7:29:e4:95:f0:02:
         17:f8:6a:3d:82:a2:e8:f2:52:d5:ac:2d:14:f2:f9:63:04:e1:
         e0:1a:2f:98:4e:95:31:36:43:d4:b2:22:79:2c:7e:0a:a8:dd:
         f7:4b:86:2c:13:d4:c5:86:8f:ca:4f:18:13:3d:7c:6a:81:69:
         35:76:fd:31:f7:ec:55:c7:57:08:9f:bf:b5:4c:36:8a:34:ab:
         7a:79:91:be:11:da:e9:a0:58:a8:a6:9d:3d:5b:26:5c:7c:c4:
         0d:ab:80:5b:15:ee:61:d9:a5:63:cb:ea:6b:fb:16:41:01:64:
         dc:b3:fd:43:1c:8b:86:a8:6d:45:49:fd:67:75:7a:73:43:9d:
         55:db:90:d4:82:41:de:3a:c5:cf:1b:52:8c:59:0a:6a:6e:b6:
         7e:7d:ed:ea:45:6d:8e:11

Wie auch schon beim Root CA Zertifikat können wir uns auch den CSR BASE64 kodiert ausgeben lassen.

 # cat /etc/pki/tls/private/graylog-server.dmz.nausch.org.csr.pem

-----BEGIN CERTIFICATE REQUEST-----
MIIE9TCCAt0CAQAwga8xCzAJBgNVBAYTAkRFMQ8wDQYDVQQIDAZCYXllcm4xETAP
BgNVBAcMCFBsaWVuaW5nMRMwEQYDVQQKDApuYXVzY2gub3JnMRYwFAYDVQQLDA1J
VC1Nb25pdG9yaW5nMSYwJAYDVQQDDB1ncmF5bG9nLXNlcnZlci5kbXoubmF1c2No
Lm9yZzEnMCUGCSqGSIb3DQEJARYYZ3JheWxvZy1hZG1pbkBuYXVzY2gub3JnMIIC
IjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEApIliha9WswQMNIZK47hq9CNs
f7xMpk7NLv44rXQZod7LNvrEtIUxHmIFpfX18HuUaSGzSK4nHL29Ui+b7q3PX/7k
D6SMCpHgdf1H6RE1lL2GtZ5HHPi3E8RgaLWPLo8Ndf56QdjnKx7L1/JPmebB2cPf
BzsL5M0fwws5ehU4Cd+oKTxzxeFYUB5L78s8Y+a+0qtUt84DaTsf1YBavpivo8k/
qIREIV31NugRrj99USmAUWS9lv8yNpxmH5yLSvD0DVArO+oyLxwiD8qHeNUf3kxF
ZMRCrtO8R5jFGRUX29PjHU6EdtK6q9uXA/+/AdchRlYJFlJYOGTQipt+ul+b7Pln
N3BmqrK+8q/KcNqPblsdX/qX2m6/8/trM1h0vWiQfSHC05wxN/GI+JWMbmjObHGD
NYuX2JR4+tfXxb0mbzAorAwIXpuY90x7SIyoPCqaAdBRf52Lo1sJomBCgfwYwVNW
n3jVO5aUWXC3RKH5j4giVZ7mZ+RPtYvd4nynCblSkSMrfxNcK/EFVKakhd9s/U4L
b5ZTKgHk+q8tPq+TxAWI1L6ZdNG+ty3kvCA9NDbkDjX803FYYOyRtys1dk2u6kms
S2STAc46OOo4jC9ajq/Tf6rkFwqH5JKUBi/KuWcgfdxl8f/3K6iMVXHUJuDIh8gc
jw1CdxyPMYqxZkwYiHkCAwEAAaAAMA0GCSqGSIb3DQEBDQUAA4ICAQArNcYetNbW
PZFgGuEF+ADcguZbTHHcOkbyjni6O2wv9/p5xeGMggi/PGl3V7alOXNjK6EEWxwk
wbpVWdUTGMGIAuGxgsnedwhB0R1y4mchJeVD3jwuE+28pdGN0uVxN7PRTZKQT3Gx
H+cBwGaMenspXy2W9p67d1YjPV52VhPbH4hUzljxS7+zsjN/uKh5LQF2hRh/fUC/
2gXPB4ZD329YVvf8p2ywM5UzBb5v2MDMMy89oKB+ClsnmEerRCwquylP3nAnJFm0
0JgIqMgi8/vefdJa6YyPP8gURyt+44KJmPdMETlZo4Im6STjsprgcxEBqkRPEmra
fuzobV39ZgQ/9tYuB2QdPzhWtG4oc2roV8onmRJRFwP1QQLeurDLKY4o6ythgZ6P
06qcY9XkCeAcQ5Y6lWBiadI4Ra3iJgqDPBMW4VONvOGeb4ql/cGsjosBZuj/UYyg
wYJ8K2AJvhJyi6f3KeSV8AIX+Go9gqLo8lLVrC0U8vljBOHgGi+YTpUxNkPUsiJ5
LH4KqN33S4YsE9TFho/KTxgTPXxqgWk1dv0x9+xVx1cIn7+1TDaKNKt6eZG+Edrp
oFiopp09WyZcfMQNq4BbFe5h2aVjy+pr+xZBAWTcs/1DHIuGqG1FSf1ndXpzQ51V
25DUgkHeOsXPG1KMWQpqbrZ+fe3qRW2OEQ==
-----END CERTIFICATE REQUEST-----

Damit unsere CA den gerade erstellten CSR prüfen und signieren kann, müssen wir den Certificate Signing Request der CA vorlegen. Im Fall unsere graylog-Server Zertificates können wir die CSR-Datei einfach an Ort und Stelle kopieren.

 # cp /etc/pki/tls/private/graylog-server.dmz.nausch.org.csr.pem /etc/pki/CA/csrs/

Nun prüfen wir die Angaben des CSR und signieren den öffentlichen Schlüssel des CSRs mit dem privaten Schlüssel unserer CA; dies wir auch als Zertifikatsgenerierung bezeichnet. Diese Arbeit erledigen wir mit Hilfe des folgenden openssl-Aufrufs. Auch hier sind die Eingaben zur besseren Unterscheidung fett und kursiv in der Farbe blau und die Rückmeldungen in der Farbe grau gekennzeichnet.

# openssl ca -in /etc/pki/CA/csrs/graylog-server.dmz.nausch.org.csr.pem \
              -out /etc/pki/CA/certs/graylog-server.dmz.nausch.org.certificate.pem -days 10950

Die Option days setzen wir dabei auf die bereits erwähnten 30 Jahre, was 10950 Tage entspricht. Bei der Frage nach der Passphrase des privaten Schlüssels geben wir das Passwort an, welches wir bei der Generierung unserer CA vergeben hatten.

Using configuration from /etc/pki/tls/openssl.cnf
Enter pass phrase for /etc/pki/CA/private/root-ca.key.pem:des-woas-blos-I-und-sunst-koana!
Check that the request matches the signature
Signature ok
Certificate Details:
        Serial Number: 0 (0x0)
        Validity
            Not Before: Jan  3 23:24:25 2016 GMT
            Not After : Dec 26 23:24:25 2045 GMT
        Subject:
            countryName               = DE
            stateOrProvinceName       = Bayern
            organizationName          = nausch.org
            organizationalUnitName    = IT-Monitoring
            commonName                = graylog-server.dmz.nausch.org
            emailAddress              = graylog-admin@nausch.org
        X509v3 extensions:
            X509v3 Basic Constraints: 
                CA:FALSE
            Netscape Comment: 
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier: 
                7A:F2:41:CE:1C:E7:CE:06:CB:30:00:AD:69:2D:6B:42:79:D7:9F:4D
            X509v3 Authority Key Identifier: 
                keyid:F7:C3:04:70:25:38:2F:02:82:5D:5F:2F:7F:1B:66:97:43:9F:D8:0E

Certificate is to be certified until Dec 26 23:24:25 2045 GMT (10950 days)
Sign the certificate? [y/n]:y


1 out of 1 certificate requests certified, commit? [y/n]y
Write out database with 1 new entries
Data Base Updated

Als letzten Schritt stellen wir nun das gerade erzeugte Server-Zertifikat dem graylog-server zur Verfügung. Hierzu kopieren wir einfach das gerade generierte Zertifikat an Ort und Stelle.

 # cp /etc/pki/CA/certs/graylog-server.dmz.nausch.org.certificate.pem /etc/pki/tls/certs/

Wollen wir den Inhalt unseres gerade erstellten Zertifikates ausgeben, können wir folgenden openssl-Aufruf verwenden.

 # openssl x509 -noout -text -in /etc/pki/tls/certs/graylog-server.dmz.nausch.org.certificate.pem

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 0 (0x0)
    Signature Algorithm: sha512WithRSAEncryption
        Issuer: C=DE, ST=Bayern, L=Pliening, O=nausch.org, OU=Zertifizierungsstelle, CN=graylog CA/emailAddress=ca-admin@nausch.org
        Validity
            Not Before: Jan  3 23:24:25 2016 GMT
            Not After : Dec 26 23:24:25 2045 GMT
        Subject: C=DE, ST=Bayern, O=nausch.org, OU=IT-Monitoring, CN=graylog-server.dmz.nausch.org/emailAddress=graylog-admin@nausch.org
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:a4:89:62:85:af:56:b3:04:0c:34:86:4a:e3:b8:
                    6a:f4:23:6c:7f:bc:4c:a6:4e:cd:2e:fe:38:ad:74:
                    19:a1:de:cb:36:fa:c4:b4:85:31:1e:62:05:a5:f5:
                    f5:f0:7b:94:69:21:b3:48:ae:27:1c:bd:bd:52:2f:
                    9b:ee:ad:cf:5f:fe:e4:0f:a4:8c:0a:91:e0:75:fd:
                    47:e9:11:35:94:bd:86:b5:9e:47:1c:f8:b7:13:c4:
                    60:68:b5:8f:2e:8f:0d:75:fe:7a:41:d8:e7:2b:1e:
                    cb:d7:f2:4f:99:e6:c1:d9:c3:df:07:3b:0b:e4:cd:
                    1f:c3:0b:39:7a:15:38:09:df:a8:29:3c:73:c5:e1:
                    58:50:1e:4b:ef:cb:3c:63:e6:be:d2:ab:54:b7:ce:
                    03:69:3b:1f:d5:80:5a:be:98:af:a3:c9:3f:a8:84:
                    44:21:5d:f5:36:e8:11:ae:3f:7d:51:29:80:51:64:
                    bd:96:ff:32:36:9c:66:1f:9c:8b:4a:f0:f4:0d:50:
                    2b:3b:ea:32:2f:1c:22:0f:ca:87:78:d5:1f:de:4c:
                    45:64:c4:42:ae:d3:bc:47:98:c5:19:15:17:db:d3:
                    e3:1d:4e:84:76:d2:ba:ab:db:97:03:ff:bf:01:d7:
                    21:46:56:09:16:52:58:38:64:d0:8a:9b:7e:ba:5f:
                    9b:ec:f9:67:37:70:66:aa:b2:be:f2:af:ca:70:da:
                    8f:6e:5b:1d:5f:fa:97:da:6e:bf:f3:fb:6b:33:58:
                    74:bd:68:90:7d:21:c2:d3:9c:31:37:f1:88:f8:95:
                    8c:6e:68:ce:6c:71:83:35:8b:97:d8:94:78:fa:d7:
                    d7:c5:bd:26:6f:30:28:ac:0c:08:5e:9b:98:f7:4c:
                    7b:48:8c:a8:3c:2a:9a:01:d0:51:7f:9d:8b:a3:5b:
                    09:a2:60:42:81:fc:18:c1:53:56:9f:78:d5:3b:96:
                    94:59:70:b7:44:a1:f9:8f:88:22:55:9e:e6:67:e4:
                    4f:b5:8b:dd:e2:7c:a7:09:b9:52:91:23:2b:7f:13:
                    5c:2b:f1:05:54:a6:a4:85:df:6c:fd:4e:0b:6f:96:
                    53:2a:01:e4:fa:af:2d:3e:af:93:c4:05:88:d4:be:
                    99:74:d1:be:b7:2d:e4:bc:20:3d:34:36:e4:0e:35:
                    fc:d3:71:58:60:ec:91:b7:2b:35:76:4d:ae:ea:49:
                    ac:4b:64:93:01:ce:3a:38:ea:38:8c:2f:5a:8e:af:
                    d3:7f:aa:e4:17:0a:87:e4:92:94:06:2f:ca:b9:67:
                    20:7d:dc:65:f1:ff:f7:2b:a8:8c:55:71:d4:26:e0:
                    c8:87:c8:1c:8f:0d:42:77:1c:8f:31:8a:b1:66:4c:
                    18:88:79
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: 
                CA:FALSE
            Netscape Comment: 
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier: 
                7A:F2:41:CE:1C:E7:CE:06:CB:30:00:AD:69:2D:6B:42:79:D7:9F:4D
            X509v3 Authority Key Identifier: 
                keyid:F7:C3:04:70:25:38:2F:02:82:5D:5F:2F:7F:1B:66:97:43:9F:D8:0E

    Signature Algorithm: sha512WithRSAEncryption
         ba:96:c5:fd:9d:1d:22:78:e3:1b:f4:c0:90:73:0c:7e:d6:e8:
         2f:ad:92:75:3a:8c:18:37:7b:74:2d:ba:01:dd:4f:e2:07:f0:
         6c:d2:e2:0b:a6:7f:67:f5:16:98:96:8a:71:fd:bd:ad:a2:5c:
         07:40:23:4e:e1:0d:da:b4:61:cc:83:56:a9:89:56:4b:69:a1:
         cb:ae:f2:bc:14:7a:c4:8e:15:da:f6:43:77:42:f2:42:da:82:
         a1:63:16:4d:d4:8a:86:00:54:71:98:c9:2e:4f:df:e5:19:26:
         7a:86:f3:62:88:81:64:75:8c:d0:1c:32:40:53:46:6c:cb:c0:
         61:7b:7a:58:be:09:e6:06:00:88:d6:23:f9:f3:9f:ac:61:2c:
         c3:f1:62:c2:25:09:91:d5:3b:11:47:47:e5:d3:ed:a7:11:99:
         d2:7e:af:b1:0d:ec:e0:7e:2b:ba:34:e6:c3:32:16:cc:81:70:
         fd:37:a0:ee:8d:2d:48:2c:47:43:fc:9d:3a:b6:8d:8d:2c:c2:
         68:2e:46:69:76:b7:33:a3:9b:56:ea:85:e4:93:62:1f:2a:3d:
         54:d9:38:46:e4:d6:91:0f:88:63:b1:4c:0f:d7:3f:3e:db:cb:
         dd:1b:18:9e:d1:19:a3:bd:a0:53:1f:c1:ac:d7:cf:2a:5a:29:
         ef:d2:8b:85:b0:91:6e:69:22:9d:bc:11:42:e4:d1:bd:85:85:
         f9:cf:e9:52:b0:52:75:10:4b:9b:84:f2:e5:fb:15:36:36:41:
         9b:0e:b2:d6:d4:7e:83:31:a3:b2:32:9d:39:5f:66:67:73:52:
         56:f0:66:d2:b5:9e:75:38:27:e8:85:4a:b3:bb:20:92:94:04:
         02:c8:d2:fb:24:67:48:6f:24:4e:6e:a4:b1:d6:ef:cf:e3:9a:
         e9:37:f2:73:32:b2:e5:be:e9:0c:52:1e:28:e5:c2:21:e7:b6:
         fc:52:88:15:a5:b2:0a:34:f3:de:89:1b:72:7c:1a:c6:55:3f:
         e3:43:24:62:8a:00:e3:9a:f9:02:7b:4e:77:0a:83:16:07:60:
         f6:21:b1:ee:47:4f:be:78:5a:36:38:c6:89:36:20:8a:d3:c0:
         f2:28:6d:db:4d:81:4b:2b:08:55:ed:23:e8:a7:e1:8f:46:9d:
         29:24:cb:bb:ca:bc:10:58:49:e3:bc:11:b3:55:35:ec:25:f7:
         66:2f:d9:c8:62:f2:d6:5a:c2:ff:b5:a3:ba:bd:5a:7d:05:59:
         04:91:98:3b:41:01:ac:2b:d9:20:d8:df:4a:92:dd:a3:82:c3:
         fe:38:3c:fa:f0:65:c0:5c:89:f2:42:47:56:6c:e4:7e:43:dd:
         70:7c:65:a7:52:b3:59:7e

Was uns nun noch für unser Glück fehlt, ist ein Server-Zertifikat für den rsyslog-Daemon; dieses werden wir nun noch generieren bzw. erstellen lassen. Im Prinzip unterscheidet sich die Generierung eines rsyslog Client-Zertifikate nicht vom Vorgehen des zuvor erstellten graylog-server Zertifikates.

Im folgenden Konfigurationsbeispiel werden wir für den Host vml.dmz.nausch.org ein Clientzertifikat erstellen.

Wie auch schon beim graylog-server Zertifikat erzeugen wir uns zunächst einen 4096 Bit langen RSA Schlüssel, den wir mit AES 256 verschlüsselt auf der Platte abgelegt lassen. Da OpenSSL keine leere Passphrase zulässt braucht die Passphrase diesmal nicht sonderlich geheim sein, da wir diese im Anschluss ohnehin sofort wieder entfernen werden.

Die Eingaben sind auch hier zur besseren Unterscheidung fett und kursiv in der Farbe blau und die Rückmeldungen in der Farbe grau gekennzeichnet.

# openssl genrsa -out /etc/pki/tls/clientkey.pem -aes256 4096

Generating RSA private key, 4096 bit long modulus
.......................................................................................................................................................................................................................++
........................................................................................................................................................................................++
e is 65537 (0x10001)
Enter pass phrase for clientkey.pem: 12qwasyx
Verifying - Enter pass phrase for clientkey.pem: 12qwasyx

Anschließend entfernen wir die Passphrase nun wieder, in dem wir bei der Frage Enter pass phrase: einfach die Taste [ENTER] drücken.

# openssl rsa -in /etc/pki/tls/clientkey.pem -out /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem

Enter pass phrase:
writing RSA key

Wie schon zuvor schützen wir auch hier den Serverschlüssel über die Dateirechte.

# chmod 400 /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem

Da wir die Schlüsseldatei mit der unsicheren Passphrase nicht mehr benötigen, vernichten wir die zugehörige Datei.

# shred -u /etc/pki/tls/clientkey.pem

Nachdem wir unseren privaten Schlüssel erzeugt haben, können wir uns nun unserem CSR¹⁰⁾ widmen. Wie schon zuvor, sind die Eingaben auch hier zur besseren Unterscheidung fett und kursiv in der Farbe blau und die Rückmeldungen in der Farbe grau gekennzeichnet.

# openssl req -new -key /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem \
              -out /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.csr.pem -nodes

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:DE
State or Province Name (full name) []:Bayern
Locality Name (eg, city) [Default City]:Pliening
Organization Name (eg, company) [Default Company Ltd]:nausch.org
Organizational Unit Name (eg, section) []:IT-Monitoring
Common Name (eg, your name or your server's hostname) []:rsyslog.vml000037.dmz.nausch.org
Email Address []:graylog-admin@nausch.org

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:

Möchten wir den Inhalt unseres Certificate Signing Request ausgeben und ansehen, verwenden wir den folgenden openssl-Aufruf.

 # openssl req -noout -text -in /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.csr.pem

Certificate Request:
    Data:
        Version: 0 (0x0)
        Subject: C=DE, ST=Bayern, L=Pliening, O=nausch.org, OU=IT-Monitoring, CN=rsyslog.vml000037.dmz.nausch.org/emailAddress=graylog-admin@nausch.org
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:ea:65:5c:9a:3b:3e:a9:2d:7f:f1:a5:9f:b3:e3:
                    cd:a4:53:fb:70:30:fd:c8:be:00:fd:04:2a:08:f4:
                    ea:d2:69:66:02:2d:c5:d9:b8:53:8d:d9:5a:7c:fd:
                    7a:92:12:4c:ab:83:ce:7a:8a:d3:0e:60:16:87:a0:
                    a6:21:5e:96:2b:36:87:e9:85:f1:1b:fe:56:87:e3:
                    6e:30:40:9e:f7:f8:f2:8f:05:fa:57:d0:fb:10:94:
                    a4:2e:16:ed:55:cb:22:61:e3:ac:4c:13:6c:70:da:
                    e6:8b:8b:54:f6:4e:d4:58:5a:18:06:f1:61:20:98:
                    0f:dc:4c:30:4e:ef:c4:b3:0c:63:93:82:4a:89:98:
                    2e:6b:ae:75:c7:3a:c9:60:25:ac:58:fc:da:d4:83:
                    35:c6:96:2c:d9:6f:5e:0c:9f:9d:7a:f2:2e:ab:f0:
                    06:5b:f5:4a:74:62:02:83:9a:76:e3:04:db:9f:ee:
                    40:d5:03:ad:45:0d:69:be:39:f4:00:75:db:4d:f0:
                    e9:56:7b:e5:3e:3e:63:69:23:c9:b4:0a:e2:d1:cd:
                    56:76:41:8b:43:f3:fc:2e:01:ca:21:16:7d:a9:24:
                    e5:65:9d:21:bc:64:bc:dd:e1:f7:89:33:28:38:4e:
                    09:7c:5d:7c:ec:1f:67:5a:c0:ac:3d:b2:32:9a:73:
                    cc:f2:c5:41:4c:17:b7:75:ca:ad:76:37:7e:a6:f2:
                    85:10:c5:e3:ee:95:94:b2:d2:51:cc:59:96:ca:e4:
                    0f:96:c1:7b:89:42:50:61:01:6c:33:32:33:9d:72:
                    57:a2:45:92:f0:bd:f7:47:6f:c1:51:c0:b9:05:fd:
                    a9:af:a8:6c:f6:9b:1a:a5:e4:2b:34:0b:62:04:b7:
                    c3:89:aa:83:5a:5c:82:b0:d1:72:ac:0b:e0:e4:94:
                    3c:44:0b:95:e9:a5:97:96:ee:e9:38:b9:92:74:89:
                    93:31:a6:5e:ca:dd:f8:d9:f8:ea:ff:b3:62:4a:45:
                    aa:1c:35:05:fc:2c:36:da:b2:59:af:82:69:2c:d7:
                    4d:6c:df:2e:fc:c1:4a:f6:e1:f9:57:b7:83:b3:b1:
                    4e:48:36:1e:57:94:65:1e:a9:3f:96:56:03:21:46:
                    02:dc:4a:54:46:f0:99:25:9c:c8:bf:25:8a:d6:1f:
                    ba:fd:ab:70:cd:96:cc:28:36:3b:66:b0:fb:48:47:
                    59:78:69:5b:69:6c:a9:ca:a1:23:56:7a:47:f7:49:
                    cf:25:b5:1d:37:83:84:fe:f9:8a:be:ff:be:e5:93:
                    9c:c0:05:99:d3:14:a6:ce:23:dc:75:ce:0c:a5:e3:
                    40:cf:f9:10:a6:40:93:1f:25:51:f6:7f:5c:a4:74:
                    b7:b3:39
                Exponent: 65537 (0x10001)
        Attributes:
            a0:00
    Signature Algorithm: sha256WithRSAEncryption
         dd:25:b7:55:94:ae:7d:24:9a:5e:4d:84:e8:bc:12:37:20:a2:
         64:f9:fd:15:83:9a:a1:59:72:fe:2a:2b:df:f8:f3:11:f0:0a:
         e0:b9:0e:ae:b8:93:ed:a3:3c:48:06:5a:5a:74:6d:62:c9:9d:
         f8:22:de:9b:5e:39:bd:a2:09:fa:9f:bd:3e:1d:87:37:f3:2f:
         9f:35:9a:5e:b0:c6:7a:66:0c:86:4f:f3:6c:5b:fb:4b:25:9f:
         83:ec:64:e2:43:ad:51:91:b7:56:eb:fc:00:4e:b4:36:0a:2f:
         3d:c7:53:67:e6:b0:8d:11:68:dd:19:b5:ee:25:d9:d8:0c:49:
         21:57:28:ec:ca:c8:ea:09:85:3b:14:54:72:73:58:5a:e3:4c:
         21:3e:d6:e6:b4:7d:25:1a:31:ec:a1:d8:c7:31:bc:fb:44:1d:
         2f:69:91:1a:11:8e:02:63:bf:f4:8f:ca:fc:45:3c:ef:a1:31:
         54:4e:9f:c3:b2:ab:68:69:69:93:ac:17:02:5c:ad:70:9f:73:
         98:ba:12:61:1e:94:d1:92:8a:8b:93:b0:f6:74:58:39:f8:96:
         26:7a:ba:fc:48:63:09:95:21:ee:8e:36:5f:c7:ce:5b:61:1c:
         6b:ed:75:a1:b1:9a:74:64:29:6d:03:64:7b:6e:8a:b5:5d:83:
         62:ce:54:96:c5:47:68:7a:63:2a:8c:3c:3c:5f:54:3a:4f:51:
         a7:ae:49:e8:a4:31:6e:58:34:97:74:9f:6d:72:c1:55:23:ea:
         75:7f:23:8b:0e:cb:f7:71:a0:11:64:50:c7:1e:3f:0f:1b:cd:
         4d:d9:3b:79:6c:a4:39:8a:94:72:33:61:5a:fb:07:8a:0c:02:
         73:77:72:c2:9d:6c:a6:d4:b9:32:e2:9a:6e:dc:ff:33:df:ee:
         75:ff:4d:b8:0c:ee:11:ac:a5:f6:39:cb:9b:b2:9b:98:db:db:
         89:8c:18:13:68:99:90:1d:65:99:21:10:14:b7:91:8f:0c:bd:
         2c:1e:fd:0f:fd:9d:f5:dc:2a:1b:8f:15:37:c0:98:6e:e9:0f:
         0d:96:cb:87:43:c5:1e:7e:28:7e:ca:d7:eb:58:e8:32:34:85:
         29:4c:b1:56:b1:57:c6:e5:72:a6:0a:3b:26:64:af:bc:1f:2f:
         72:ee:c7:50:c5:09:98:57:e6:92:5b:30:8b:f8:05:e5:8c:59:
         1b:53:15:96:dc:4a:de:b2:d0:db:9a:6c:ce:60:38:9c:94:0f:
         3c:21:63:ff:50:f9:a2:c1:64:78:02:fd:52:8c:41:ee:78:27:
         c8:d9:74:1c:31:dd:c2:b5:c9:82:48:2d:e5:e0:f3:e9:51:96:
         1a:c0:d3:58:1b:3c:91:b0

Wie auch schon beim graylog-server Zertifikat können wir uns auch den CSR BASE64 kodiert ausgeben lassen.

 # cat /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.csr.pem

-----BEGIN CERTIFICATE REQUEST-----
MIIE+DCCAuACAQAwgbIxCzAJBgNVBAYTAkRFMQ8wDQYDVQQIDAZCYXllcm4xETAP
BgNVBAcMCFBsaWVuaW5nMRMwEQYDVQQKDApuYXVzY2gub3JnMRYwFAYDVQQLDA1J
VC1Nb25pdG9yaW5nMSkwJwYDVQQDDCByc3lzbG9nLnZtbDAwMDAzNy5kbXoubmF1
c2NoLm9yZzEnMCUGCSqGSIb3DQEJARYYZ3JheWxvZy1hZG1pbkBuYXVzY2gub3Jn
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6mVcmjs+qS1/8aWfs+PN
pFP7cDD9yL4A/QQqCPTq0mlmAi3F2bhTjdlafP16khJMq4POeorTDmAWh6CmIV6W
KzaH6YXxG/5Wh+NuMECe9/jyjwX6V9D7EJSkLhbtVcsiYeOsTBNscNrmi4tU9k7U
WFoYBvFhIJgP3EwwTu/Eswxjk4JKiZgua651xzrJYCWsWPza1IM1xpYs2W9eDJ+d
evIuq/AGW/VKdGICg5p24wTbn+5A1QOtRQ1pvjn0AHXbTfDpVnvlPj5jaSPJtAri
0c1WdkGLQ/P8LgHKIRZ9qSTlZZ0hvGS83eH3iTMoOE4JfF187B9nWsCsPbIymnPM
8sVBTBe3dcqtdjd+pvKFEMXj7pWUstJRzFmWyuQPlsF7iUJQYQFsMzIznXJXokWS
8L33R2/BUcC5Bf2pr6hs9psapeQrNAtiBLfDiaqDWlyCsNFyrAvg5JQ8RAuV6aWX
lu7pOLmSdImTMaZeyt342fjq/7NiSkWqHDUF/Cw22rJZr4JpLNdNbN8u/MFK9uH5
V7eDs7FOSDYeV5RlHqk/llYDIUYC3EpURvCZJZzIvyWK1h+6/atwzZbMKDY7ZrD7
SEdZeGlbaWypyqEjVnpH90nPJbUdN4OE/vmKvv++5ZOcwAWZ0xSmziPcdc4MpeNA
z/kQpkCTHyVR9n9cpHS3szkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4ICAQDdJbdV
lK59JJpeTYTovBI3IKJk+f0Vg5qhWXL+Kivf+PMR8ArguQ6uuJPtozxIBlpadG1i
yZ34It6bXjm9ogn6n70+HYc38y+fNZpesMZ6ZgyGT/NsW/tLJZ+D7GTiQ61RkbdW
6/wATrQ2Ci89x1Nn5rCNEWjdGbXuJdnYDEkhVyjsysjqCYU7FFRyc1ha40whPtbm
tH0lGjHsodjHMbz7RB0vaZEaEY4CY7/0j8r8RTzvoTFUTp/DsqtoaWmTrBcCXK1w
n3OYuhJhHpTRkoqLk7D2dFg5+JYmerr8SGMJlSHujjZfx85bYRxr7XWhsZp0ZClt
A2R7boq1XYNizlSWxUdoemMqjDw8X1Q6T1GnrknopDFuWDSXdJ9tcsFVI+p1fyOL
Dsv3caARZFDHHj8PG81N2Tt5bKQ5ipRyM2Fa+weKDAJzd3LCnWym1Lky4ppu3P8z
3+51/024DO4RrKX2OcubspuY29uJjBgTaJmQHWWZIRAUt5GPDL0sHv0P/Z313Cob
jxU3wJhu6Q8NlsuHQ8Uefih+ytfrWOgyNIUpTLFWsVfG5XKmCjsmZK+8Hy9y7sdQ
xQmYV+aSWzCL+AXljFkbUxWW3ErestDbmmzOYDiclA88IWP/UPmiwWR4Av1SjEHu
eCfI2XQcMd3CtcmCSC3l4PPpUZYawNNYGzyRsA==
-----END CERTIFICATE REQUEST-----

Damit unsere CA den gerade erstellten CSR prüfen und signieren kann, müssen wir den Certificate Signing Request der CA vorlegen. Wir kopieren entweder den gerade erstellten CSR via scp zum Server auf dem unsere CA erstellt hatten, oder wir legen die CSR-Datei mit dem Editor direkt auf dem Server ab.

 # vim /etc/pki/CA/csrs/rsyslog.vml000037.dmz.nausch.org.csr.pem

-----BEGIN CERTIFICATE REQUEST-----
MIIE+DCCAuACAQAwgbIxCzAJBgNVBAYTAkRFMQ8wDQYDVQQIDAZCYXllcm4xETAP
BgNVBAcMCFBsaWVuaW5nMRMwEQYDVQQKDApuYXVzY2gub3JnMRYwFAYDVQQLDA1J
VC1Nb25pdG9yaW5nMSkwJwYDVQQDDCByc3lzbG9nLnZtbDAwMDAzNy5kbXoubmF1
c2NoLm9yZzEnMCUGCSqGSIb3DQEJARYYZ3JheWxvZy1hZG1pbkBuYXVzY2gub3Jn
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6mVcmjs+qS1/8aWfs+PN
pFP7cDD9yL4A/QQqCPTq0mlmAi3F2bhTjdlafP16khJMq4POeorTDmAWh6CmIV6W
KzaH6YXxG/5Wh+NuMECe9/jyjwX6V9D7EJSkLhbtVcsiYeOsTBNscNrmi4tU9k7U
WFoYBvFhIJgP3EwwTu/Eswxjk4JKiZgua651xzrJYCWsWPza1IM1xpYs2W9eDJ+d
evIuq/AGW/VKdGICg5p24wTbn+5A1QOtRQ1pvjn0AHXbTfDpVnvlPj5jaSPJtAri
0c1WdkGLQ/P8LgHKIRZ9qSTlZZ0hvGS83eH3iTMoOE4JfF187B9nWsCsPbIymnPM
8sVBTBe3dcqtdjd+pvKFEMXj7pWUstJRzFmWyuQPlsF7iUJQYQFsMzIznXJXokWS
8L33R2/BUcC5Bf2pr6hs9psapeQrNAtiBLfDiaqDWlyCsNFyrAvg5JQ8RAuV6aWX
lu7pOLmSdImTMaZeyt342fjq/7NiSkWqHDUF/Cw22rJZr4JpLNdNbN8u/MFK9uH5
V7eDs7FOSDYeV5RlHqk/llYDIUYC3EpURvCZJZzIvyWK1h+6/atwzZbMKDY7ZrD7
SEdZeGlbaWypyqEjVnpH90nPJbUdN4OE/vmKvv++5ZOcwAWZ0xSmziPcdc4MpeNA
z/kQpkCTHyVR9n9cpHS3szkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4ICAQDdJbdV
lK59JJpeTYTovBI3IKJk+f0Vg5qhWXL+Kivf+PMR8ArguQ6uuJPtozxIBlpadG1i
yZ34It6bXjm9ogn6n70+HYc38y+fNZpesMZ6ZgyGT/NsW/tLJZ+D7GTiQ61RkbdW
6/wATrQ2Ci89x1Nn5rCNEWjdGbXuJdnYDEkhVyjsysjqCYU7FFRyc1ha40whPtbm
tH0lGjHsodjHMbz7RB0vaZEaEY4CY7/0j8r8RTzvoTFUTp/DsqtoaWmTrBcCXK1w
n3OYuhJhHpTRkoqLk7D2dFg5+JYmerr8SGMJlSHujjZfx85bYRxr7XWhsZp0ZClt
A2R7boq1XYNizlSWxUdoemMqjDw8X1Q6T1GnrknopDFuWDSXdJ9tcsFVI+p1fyOL
Dsv3caARZFDHHj8PG81N2Tt5bKQ5ipRyM2Fa+weKDAJzd3LCnWym1Lky4ppu3P8z
3+51/024DO4RrKX2OcubspuY29uJjBgTaJmQHWWZIRAUt5GPDL0sHv0P/Z313Cob
jxU3wJhu6Q8NlsuHQ8Uefih+ytfrWOgyNIUpTLFWsVfG5XKmCjsmZK+8Hy9y7sdQ
xQmYV+aSWzCL+AXljFkbUxWW3ErestDbmmzOYDiclA88IWP/UPmiwWR4Av1SjEHu
eCfI2XQcMd3CtcmCSC3l4PPpUZYawNNYGzyRsA==
-----END CERTIFICATE REQUEST-----

Nun prüfen wir die Angaben des CSR und signieren den öffentlichen Schlüssel des CSRs mit dem privaten Schlüssel unserer CA; dies wir auch als Zertifikatsgenerierung bezeichnet. Diese Arbeit erledigen wir mit Hilfe des folgenden openssl-Aufrufs. Auch hier sind die Eingaben zur besseren Unterscheidung fett und kursiv in der Farbe blau und die Rückmeldungen in der Farbe grau gekennzeichnet.

# openssl ca -in /etc/pki/CA/csrs/rsyslog.vml000037.dmz.nausch.org.csr.pem \
              -out /etc/pki/CA/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem -days 10950

Die Option days setzen wir dabei wieder auf 30 Jahre, was 10950 Tage entspricht. Bei der Frage nach der Passphrase des privaten Schlüssels geben wir das Passwort an, welches wir bei der Generierung unserer CA vergeben hatten.

Using configuration from /etc/pki/tls/openssl.cnf
Enter pass phrase for /etc/pki/CA/private/root-ca.key.pem:des-woas-blos-I-und-sunst-koana!
Check that the request matches the signature
Signature ok
Certificate Details:
        Serial Number: 1 (0x1)
        Validity
            Not Before: Jan  4 10:08:53 2016 GMT
            Not After : Dec 27 10:08:53 2045 GMT
        Subject:
            countryName               = DE
            stateOrProvinceName       = Bayern
            organizationName          = nausch.org
            organizationalUnitName    = IT-Monitoring
            commonName                = rsyslog.vml000037.dmz.nausch.org
            emailAddress              = graylog-admin@nausch.org
        X509v3 extensions:
            X509v3 Basic Constraints: 
                CA:FALSE
            Netscape Comment: 
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier: 
                93:2E:9C:FB:B3:9D:5B:55:8A:09:81:B4:FB:C2:CA:86:28:9E:EA:88
            X509v3 Authority Key Identifier: 
                keyid:F7:C3:04:70:25:38:2F:02:82:5D:5F:2F:7F:1B:66:97:43:9F:D8:0E

Certificate is to be certified until Dec 27 10:08:53 2045 GMT (10950 days)
Sign the certificate? [y/n]:y


1 out of 1 certificate requests certified, commit? [y/n]y
Write out database with 1 new entries
Data Base Updated

 # openssl x509 -noout -text -in /etc/pki/CA/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 1 (0x1)
    Signature Algorithm: sha512WithRSAEncryption
        Issuer: C=DE, ST=Bayern, L=Pliening, O=nausch.org, OU=Zertifizierungsstelle, CN=graylog CA/emailAddress=ca-admin@nausch.org
        Validity
            Not Before: Jan  4 10:08:53 2016 GMT
            Not After : Dec 27 10:08:53 2045 GMT
        Subject: C=DE, ST=Bayern, O=nausch.org, OU=IT-Monitoring, CN=rsyslog.vml000037.dmz.nausch.org/emailAddress=graylog-admin@nausch.org
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:ea:65:5c:9a:3b:3e:a9:2d:7f:f1:a5:9f:b3:e3:
                    cd:a4:53:fb:70:30:fd:c8:be:00:fd:04:2a:08:f4:
                    ea:d2:69:66:02:2d:c5:d9:b8:53:8d:d9:5a:7c:fd:
                    7a:92:12:4c:ab:83:ce:7a:8a:d3:0e:60:16:87:a0:
                    a6:21:5e:96:2b:36:87:e9:85:f1:1b:fe:56:87:e3:
                    6e:30:40:9e:f7:f8:f2:8f:05:fa:57:d0:fb:10:94:
                    a4:2e:16:ed:55:cb:22:61:e3:ac:4c:13:6c:70:da:
                    e6:8b:8b:54:f6:4e:d4:58:5a:18:06:f1:61:20:98:
                    0f:dc:4c:30:4e:ef:c4:b3:0c:63:93:82:4a:89:98:
                    2e:6b:ae:75:c7:3a:c9:60:25:ac:58:fc:da:d4:83:
                    35:c6:96:2c:d9:6f:5e:0c:9f:9d:7a:f2:2e:ab:f0:
                    06:5b:f5:4a:74:62:02:83:9a:76:e3:04:db:9f:ee:
                    40:d5:03:ad:45:0d:69:be:39:f4:00:75:db:4d:f0:
                    e9:56:7b:e5:3e:3e:63:69:23:c9:b4:0a:e2:d1:cd:
                    56:76:41:8b:43:f3:fc:2e:01:ca:21:16:7d:a9:24:
                    e5:65:9d:21:bc:64:bc:dd:e1:f7:89:33:28:38:4e:
                    09:7c:5d:7c:ec:1f:67:5a:c0:ac:3d:b2:32:9a:73:
                    cc:f2:c5:41:4c:17:b7:75:ca:ad:76:37:7e:a6:f2:
                    85:10:c5:e3:ee:95:94:b2:d2:51:cc:59:96:ca:e4:
                    0f:96:c1:7b:89:42:50:61:01:6c:33:32:33:9d:72:
                    57:a2:45:92:f0:bd:f7:47:6f:c1:51:c0:b9:05:fd:
                    a9:af:a8:6c:f6:9b:1a:a5:e4:2b:34:0b:62:04:b7:
                    c3:89:aa:83:5a:5c:82:b0:d1:72:ac:0b:e0:e4:94:
                    3c:44:0b:95:e9:a5:97:96:ee:e9:38:b9:92:74:89:
                    93:31:a6:5e:ca:dd:f8:d9:f8:ea:ff:b3:62:4a:45:
                    aa:1c:35:05:fc:2c:36:da:b2:59:af:82:69:2c:d7:
                    4d:6c:df:2e:fc:c1:4a:f6:e1:f9:57:b7:83:b3:b1:
                    4e:48:36:1e:57:94:65:1e:a9:3f:96:56:03:21:46:
                    02:dc:4a:54:46:f0:99:25:9c:c8:bf:25:8a:d6:1f:
                    ba:fd:ab:70:cd:96:cc:28:36:3b:66:b0:fb:48:47:
                    59:78:69:5b:69:6c:a9:ca:a1:23:56:7a:47:f7:49:
                    cf:25:b5:1d:37:83:84:fe:f9:8a:be:ff:be:e5:93:
                    9c:c0:05:99:d3:14:a6:ce:23:dc:75:ce:0c:a5:e3:
                    40:cf:f9:10:a6:40:93:1f:25:51:f6:7f:5c:a4:74:
                    b7:b3:39
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: 
                CA:FALSE
            Netscape Comment: 
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier: 
                93:2E:9C:FB:B3:9D:5B:55:8A:09:81:B4:FB:C2:CA:86:28:9E:EA:88
            X509v3 Authority Key Identifier: 
                keyid:F7:C3:04:70:25:38:2F:02:82:5D:5F:2F:7F:1B:66:97:43:9F:D8:0E

    Signature Algorithm: sha512WithRSAEncryption
         5a:54:5d:08:53:1d:39:ef:85:c0:af:8e:85:bf:c9:b4:03:49:
         b7:dc:4a:42:ab:46:1f:54:d7:8e:6c:cc:70:00:b0:da:c1:8c:
         d8:92:d1:f1:d9:4d:d9:8f:8a:ad:8e:db:56:1b:8c:c2:63:1d:
         c4:06:41:f2:07:cd:e3:09:4a:68:06:9d:42:cb:e7:05:86:93:
         26:8a:aa:11:fe:74:38:e2:27:9a:0f:a8:38:e3:ea:e6:63:a4:
         70:09:7d:01:69:cc:60:f7:c1:32:3a:d6:3d:9a:3d:e1:6f:8e:
         54:a7:bc:fe:de:9a:e1:f7:cb:75:65:c3:2e:39:34:8b:fc:42:
         f2:05:ea:7f:8b:11:90:d7:fc:17:e6:3e:a1:2c:6f:51:89:dc:
         da:60:12:77:99:2e:b3:20:2a:9b:63:b6:2b:83:60:3c:21:2b:
         8d:a7:b6:a1:7c:31:75:08:e9:49:a9:23:60:22:49:b8:26:11:
         74:00:a9:1e:0c:25:5b:0d:e2:1e:30:61:07:ca:6c:7e:10:92:
         d1:19:73:d9:11:53:8c:cc:50:2d:22:23:9d:de:af:02:c8:c0:
         07:d3:2e:42:15:1a:78:76:03:93:8c:d1:3a:50:19:05:e2:c0:
         6b:58:ae:58:96:10:93:6e:08:7f:b2:c1:53:5c:0e:d2:a7:28:
         e3:74:34:ad:d6:e2:5c:3b:6d:8f:a6:ab:69:b0:c8:b9:52:28:
         be:1f:df:2f:b6:e4:e2:e2:b5:b1:c1:e8:b2:cd:ae:01:7c:ee:
         a1:ae:0d:e2:58:f5:cf:d3:61:d9:48:e2:b0:2e:9a:6c:ce:28:
         bf:3d:02:67:48:ee:25:28:01:4b:e5:48:97:88:80:66:82:29:
         cf:55:da:67:1b:b1:6e:99:88:25:92:f6:fc:bc:6f:89:e0:a1:
         ce:b3:55:8e:39:5a:52:12:ca:06:b7:9a:c3:8a:89:a1:43:53:
         cf:70:8a:94:87:2f:42:24:3c:12:e9:87:fa:d3:9e:de:33:28:
         55:8c:9b:f1:aa:b4:4d:ba:7d:de:b7:33:bc:6b:e2:8a:82:d4:
         d8:ae:84:78:90:27:3d:e2:15:da:fe:3a:b4:df:46:38:5c:a8:
         5b:55:81:91:f2:38:20:2a:f9:28:5d:88:9d:b6:b4:d1:4b:07:
         26:a4:ef:ab:fa:e7:e9:34:61:01:8d:77:8d:ae:4b:b7:19:93:
         dd:64:16:90:a0:86:eb:c2:51:a2:0c:a3:91:b5:d8:cb:70:1b:
         f0:42:c8:71:19:60:1f:5e:6a:4f:66:2d:42:75:d2:c2:3f:82:
         b1:3c:c1:5e:67:7b:99:f9:b1:35:16:00:ff:f8:c0:e8:91:8f:
         99:f6:cf:7e:07:2e:48:57

 # cat /etc/pki/CA/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem

-----BEGIN CERTIFICATE-----
MIIGNjCCBB6gAwIBAgIBATANBgkqhkiG9w0BAQ0FADCBnzELMAkGA1UEBhMCREUx
DzANBgNVBAgMBkJheWVybjERMA8GA1UEBwwIUGxpZW5pbmcxEzARBgNVBAoMCm5h
dXNjaC5vcmcxHjAcBgNVBAsMFVplcnRpZml6aWVydW5nc3N0ZWxsZTETMBEGA1UE
AwwKZ3JheWxvZyBDQTEiMCAGCSqGSIb3DQEJARYTY2EtYWRtaW5AbmF1c2NoLm9y
ZzAeFw0xNjAxMDQxMDA4NTNaFw00NTEyMjcxMDA4NTNaMIGfMQswCQYDVQQGEwJE
RTEPMA0GA1UECAwGQmF5ZXJuMRMwEQYDVQQKDApuYXVzY2gub3JnMRYwFAYDVQQL
DA1JVC1Nb25pdG9yaW5nMSkwJwYDVQQDDCByc3lzbG9nLnZtbDAwMDAzNy5kbXou
bmF1c2NoLm9yZzEnMCUGCSqGSIb3DQEJARYYZ3JheWxvZy1hZG1pbkBuYXVzY2gu
b3JnMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6mVcmjs+qS1/8aWf
s+PNpFP7cDD9yL4A/QQqCPTq0mlmAi3F2bhTjdlafP16khJMq4POeorTDmAWh6Cm
IV6WKzaH6YXxG/5Wh+NuMECe9/jyjwX6V9D7EJSkLhbtVcsiYeOsTBNscNrmi4tU
9k7UWFoYBvFhIJgP3EwwTu/Eswxjk4JKiZgua651xzrJYCWsWPza1IM1xpYs2W9e
DJ+devIuq/AGW/VKdGICg5p24wTbn+5A1QOtRQ1pvjn0AHXbTfDpVnvlPj5jaSPJ
tAri0c1WdkGLQ/P8LgHKIRZ9qSTlZZ0hvGS83eH3iTMoOE4JfF187B9nWsCsPbIy
mnPM8sVBTBe3dcqtdjd+pvKFEMXj7pWUstJRzFmWyuQPlsF7iUJQYQFsMzIznXJX
okWS8L33R2/BUcC5Bf2pr6hs9psapeQrNAtiBLfDiaqDWlyCsNFyrAvg5JQ8RAuV
6aWXlu7pOLmSdImTMaZeyt342fjq/7NiSkWqHDUF/Cw22rJZr4JpLNdNbN8u/MFK
9uH5V7eDs7FOSDYeV5RlHqk/llYDIUYC3EpURvCZJZzIvyWK1h+6/atwzZbMKDY7
ZrD7SEdZeGlbaWypyqEjVnpH90nPJbUdN4OE/vmKvv++5ZOcwAWZ0xSmziPcdc4M
peNAz/kQpkCTHyVR9n9cpHS3szkCAwEAAaN7MHkwCQYDVR0TBAIwADAsBglghkgB
hvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYE
FJMunPuznVtVigmBtPvCyoYonuqIMB8GA1UdIwQYMBaAFPfDBHAlOC8Cgl1fL38b
ZpdDn9gOMA0GCSqGSIb3DQEBDQUAA4ICAQBaVF0IUx0574XAr46Fv8m0A0m33EpC
q0YfVNeObMxwALDawYzYktHx2U3Zj4qtjttWG4zCYx3EBkHyB83jCUpoBp1Cy+cF
hpMmiqoR/nQ44ieaD6g44+rmY6RwCX0Bacxg98EyOtY9mj3hb45Up7z+3prh98t1
ZcMuOTSL/ELyBep/ixGQ1/wX5j6hLG9RidzaYBJ3mS6zICqbY7Yrg2A8ISuNp7ah
fDF1COlJqSNgIkm4JhF0AKkeDCVbDeIeMGEHymx+EJLRGXPZEVOMzFAtIiOd3q8C
yMAH0y5CFRp4dgOTjNE6UBkF4sBrWK5YlhCTbgh/ssFTXA7SpyjjdDSt1uJcO22P
pqtpsMi5Uii+H98vtuTi4rWxweiyza4BfO6hrg3iWPXP02HZSOKwLppszii/PQJn
SO4lKAFL5UiXiIBmginPVdpnG7FumYglkvb8vG+J4KHOs1WOOVpSEsoGt5rDiomh
Q1PPcIqUhy9CJDwS6Yf6057eMyhVjJvxqrRNun3etzO8a+KKgtTYroR4kCc94hXa
/jq030Y4XKhbVYGR8jggKvkoXYidtrTRSwcmpO+r+ufpNGEBjXeNrku3GZPdZBaQ
oIbrwlGiDKORtdjLcBvwQshxGWAfXmpPZi1CddLCP4KxPMFeZ3uZ+bE1FgD/+MDo
kY+Z9s9+By5IVw==
-----END CERTIFICATE-----

Als letzten Schritt stellen wir nun das gerade erzeugte Server-Zertifikat dem graylog-server zur Verfügung. Entweder kopieren wir das Zertifikat via scp auf den Clientrechner oder wir legen das BASE64 kodierte Zertifikat direkt mit dem Editor unserer Wahl auf dem Client Host ab.

 # vim /etc/pki/tls/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem

-----BEGIN CERTIFICATE-----
MIIGNjCCBB6gAwIBAgIBATANBgkqhkiG9w0BAQ0FADCBnzELMAkGA1UEBhMCREUx
DzANBgNVBAgMBkJheWVybjERMA8GA1UEBwwIUGxpZW5pbmcxEzARBgNVBAoMCm5h
dXNjaC5vcmcxHjAcBgNVBAsMFVplcnRpZml6aWVydW5nc3N0ZWxsZTETMBEGA1UE
AwwKZ3JheWxvZyBDQTEiMCAGCSqGSIb3DQEJARYTY2EtYWRtaW5AbmF1c2NoLm9y
ZzAeFw0xNjAxMDQxMDA4NTNaFw00NTEyMjcxMDA4NTNaMIGfMQswCQYDVQQGEwJE
RTEPMA0GA1UECAwGQmF5ZXJuMRMwEQYDVQQKDApuYXVzY2gub3JnMRYwFAYDVQQL
DA1JVC1Nb25pdG9yaW5nMSkwJwYDVQQDDCByc3lzbG9nLnZtbDAwMDAzNy5kbXou
bmF1c2NoLm9yZzEnMCUGCSqGSIb3DQEJARYYZ3JheWxvZy1hZG1pbkBuYXVzY2gu
b3JnMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6mVcmjs+qS1/8aWf
s+PNpFP7cDD9yL4A/QQqCPTq0mlmAi3F2bhTjdlafP16khJMq4POeorTDmAWh6Cm
IV6WKzaH6YXxG/5Wh+NuMECe9/jyjwX6V9D7EJSkLhbtVcsiYeOsTBNscNrmi4tU
9k7UWFoYBvFhIJgP3EwwTu/Eswxjk4JKiZgua651xzrJYCWsWPza1IM1xpYs2W9e
DJ+devIuq/AGW/VKdGICg5p24wTbn+5A1QOtRQ1pvjn0AHXbTfDpVnvlPj5jaSPJ
tAri0c1WdkGLQ/P8LgHKIRZ9qSTlZZ0hvGS83eH3iTMoOE4JfF187B9nWsCsPbIy
mnPM8sVBTBe3dcqtdjd+pvKFEMXj7pWUstJRzFmWyuQPlsF7iUJQYQFsMzIznXJX
okWS8L33R2/BUcC5Bf2pr6hs9psapeQrNAtiBLfDiaqDWlyCsNFyrAvg5JQ8RAuV
6aWXlu7pOLmSdImTMaZeyt342fjq/7NiSkWqHDUF/Cw22rJZr4JpLNdNbN8u/MFK
9uH5V7eDs7FOSDYeV5RlHqk/llYDIUYC3EpURvCZJZzIvyWK1h+6/atwzZbMKDY7
ZrD7SEdZeGlbaWypyqEjVnpH90nPJbUdN4OE/vmKvv++5ZOcwAWZ0xSmziPcdc4M
peNAz/kQpkCTHyVR9n9cpHS3szkCAwEAAaN7MHkwCQYDVR0TBAIwADAsBglghkgB
hvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYE
FJMunPuznVtVigmBtPvCyoYonuqIMB8GA1UdIwQYMBaAFPfDBHAlOC8Cgl1fL38b
ZpdDn9gOMA0GCSqGSIb3DQEBDQUAA4ICAQBaVF0IUx0574XAr46Fv8m0A0m33EpC
q0YfVNeObMxwALDawYzYktHx2U3Zj4qtjttWG4zCYx3EBkHyB83jCUpoBp1Cy+cF
hpMmiqoR/nQ44ieaD6g44+rmY6RwCX0Bacxg98EyOtY9mj3hb45Up7z+3prh98t1
ZcMuOTSL/ELyBep/ixGQ1/wX5j6hLG9RidzaYBJ3mS6zICqbY7Yrg2A8ISuNp7ah
fDF1COlJqSNgIkm4JhF0AKkeDCVbDeIeMGEHymx+EJLRGXPZEVOMzFAtIiOd3q8C
yMAH0y5CFRp4dgOTjNE6UBkF4sBrWK5YlhCTbgh/ssFTXA7SpyjjdDSt1uJcO22P
pqtpsMi5Uii+H98vtuTi4rWxweiyza4BfO6hrg3iWPXP02HZSOKwLppszii/PQJn
SO4lKAFL5UiXiIBmginPVdpnG7FumYglkvb8vG+J4KHOs1WOOVpSEsoGt5rDiomh
Q1PPcIqUhy9CJDwS6Yf6057eMyhVjJvxqrRNun3etzO8a+KKgtTYroR4kCc94hXa
/jq030Y4XKhbVYGR8jggKvkoXYidtrTRSwcmpO+r+ufpNGEBjXeNrku3GZPdZBaQ
oIbrwlGiDKORtdjLcBvwQshxGWAfXmpPZi1CddLCP4KxPMFeZ3uZ+bE1FgD/+MDo
kY+Z9s9+By5IVw==
-----END CERTIFICATE-----

Nachdem wir die benötigten Schlüssel und Zertifikate erfolgreich erstellt haben, machen wir uns nun an die Konfiguration des graylog-server.

Damit der graylog-server die zur Einlieferung von syslog-Daten berechtigten Clients prüfen kann, benötigt dieser ein Verzeichnis, in dem wir die Clientzertifikate ablegen können.

Zunächst erstellen wir uns ein Verzeichnis.

 # mkdir /etc/pki/tls/graylog-client-certs

Anschließend kopieren wir das Clientzertifikat unseres Clientrechners vml000037 in das Clientverzeichnis.

 # cp /etc/pki/CA/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem /etc/pki/tls/graylog-client-certs/

Bevor wir die Konfiguration über die WEB-GUI unseres graylog-Webservers vornehmen, rufen wir uns die benötigten Zertifikate und Schlüssel noch einmal kurz in Erinnerung. So können wir später die Pfadangaben einfach via cut 'n' paste kopieren.

 # ll /etc/pki/CA/certs/root-ca.certifikate.pem 

-rw-r--r--. 1 root root 2167 Jan  3 23:57 /etc/pki/CA/certs/root-ca.certifikate.pem

 # ll /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem 

-r--------. 1 root root 3243 Jan  4 00:12 /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem

 # ll /etc/pki/tls/certs/graylog-server.dmz.nausch.org.certificate.pem 

-rw-r--r--. 1 root root 2212 Jan  4 00:32 /etc/pki/tls/certs/graylog-server.dmz.nausch.org.certificate.pem

Nun öffnen wir den zu konfigurierenden Input in der WEB-GUI mit dem Browser unserer Wahl.

 $ firefox https://graylog.nausch.org/system/inputs

Folgende Optionen sind für die TLS-Aktivierung wichtig:

• Port = 6514
• TLS cert file (optional) = /etc/pki/tls/certs/graylog-server.dmz.nausch.org.certificate.pem
• TLS private key file (optional) = /etc/pki/tls/private/graylog-server.dmz.nausch.org.key.pem
• TLS client authentication (optional) = required
• TLS Client Auth Trusted Certs (optional) = /etc/pki/tls/graylog-client-certs
• Enable TLS (optional) * TCP keepalive (optional)

Über die Schaltfläche [ Update input ] verlassen und speichern wir unsere Änderungen.

Mit dem Update des Inputs wird auch der Port 6514 geöffnet; dies können wir mit Hilfe von netstat auch abfragen.

 # netstat -tulpen | grep 6514

tcp6       0      0 :::6514                 :::*                    LISTEN      988        9660525    1391/java

Damit sich unsere Clients auch mit dem Port 6514 verbinden können, benötigen wir eine passende Firewall-Regel, die wir nun noch anlegen müssen.

 # firewall-cmd --permanent --zone=public --add-rich-rule="rule family="ipv4" source address="10.0.0.0/24" port protocol="tcp" port="6514" destination address="10.0.0.117/32" accept"

success

Zum Aktivieren führen wir einen reload des firewalld Daemon durch.

 # firewall-cmd --reload

Zu guter letzt prüfen wir nun mit Hilfe von telnet, ob wir uns vom client vml000037 mit dem Port 6514 unseres graylog-servers vml000117 verbinden können

 # telnet vml000117 6514

Trying 10.0.0.117...
Connected to 10.0.0.117.
Escape character is '^]'.

Connection closed by foreign host.

Damit der rsyslog-Daemon TLS-gesicherte Verbindungen aufbauen kann, muss dieser über das Modul lmnsd_gtls verfügen. Dieses Modul ist Bestandteil des RPM-Paketes rsyslog-gnutls.

In aller Regel wird das RPM rsyslog-gnutlsnoch nicht installiert sein, so dass wir dieses nun mit Hilfe von yum noch nachholen müssen.

 # yum install rsyslog-gnutls -y

Den Inhalt dieses Paketes können wir wir folgt bei Bedarf ermitteln.

 # rpm -qil rsyslog-gnutls

Name        : rsyslog-gnutls
Version     : 7.4.7
Release     : 12.el7
Architecture: x86_64
Install Date: Sun 03 Jan 2016 02:12:09 PM CET
Group       : System Environment/Daemons
Size        : 33480
License     : (GPLv3+ and ASL 2.0)
Signature   : RSA/SHA256, Wed 25 Nov 2015 04:37:32 PM CET, Key ID 24c6a8a7f4a80eb5
Source RPM  : rsyslog-7.4.7-12.el7.src.rpm
Build Date  : Fri 20 Nov 2015 12:34:35 PM CET
Build Host  : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager    : CentOS BuildSystem <http://bugs.centos.org>
Vendor      : CentOS
URL         : http://www.rsyslog.com/
Summary     : TLS protocol support for rsyslog
Description :
The rsyslog-gnutls package contains the rsyslog plugins that provide the
ability to receive syslog messages via upcoming syslog-transport-tls
IETF standard protocol.
/usr/lib64/rsyslog/lmnsd_gtls.so

Wie schon bei der Konfiguration des graylog-server's, rufen wir uns auch hier nochmal die benötigten ins Gedächtnis. Lassen sich so so einfache Typo-Fehler bveim Bearbeiten vermeiden.

 # ll /etc/pki/CA/certs/root-ca.certifikate.pem

-rw-r--r--. 1 root root 2167 Jan  4 12:18 /etc/pki/CA/certs/root-ca.certifikate.pem

 # ll /etc/pki/tls/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem 

-rw-r--r--. 1 root root 2216 Jan  4 11:13 /etc/pki/tls/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem

 # ll /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem 

-r--------. 1 root root 3243 Jan  4 10:57 /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem

Nun bearbeiten wir die Konfigurationsdatei unseres rsyslog-Daemon und hinterlegen dort die entsprechenden Pfadangaben zu dem lmnsd_gtls-Modul, der Schlüsseldatei und den Zertifikaten. Die wichtigsten Änderungen sind hier noch einmal zusammengefasst:

• $DefaultNetstreamDriver gtls
• $DefaultNetstreamDriverCAFile /etc/pki/ca-trust/source/anchors/root-ca.nausch.org.pem
• $DefaultNetstreamDriverCertFile /etc/pki/tls/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem
• $DefaultNetstreamDriverKeyFile /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem
• $ActionSendStreamDriverAuthMode x509/name
• $ActionSendStreamDriverPermittedPeer graylog-server.dmz.nausch.org
• $ActionSendStreamDriverMode 1

Alle Änderungen in der Konfigurationsdatei sind mit dem Namen Django : <Datumsstempel> versehen.

 # vim /etc/rsyslog.conf

/etc/rsyslog.conf

# rsyslog configuration file
 
# For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html
# If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html
 
#### MODULES ####
 
# Django : 2016-01-03
# default: unset
$DefaultNetstreamDriver gtls #make gtls driver the default
 
# The imjournal module bellow is now used as a message source instead of imuxsock.
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal
#$ModLoad imklog # reads kernel messages (the same are read from journald)
#$ModLoad immark  # provides --MARK-- message capability
 
# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514
 
# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514
 
 
#### GLOBAL DIRECTIVES ####
 
# Where to place auxiliary files
$WorkDirectory /var/lib/rsyslog
 
# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
 
# File syncing capability is disabled by default. This feature is usually not required,
# not useful and an extreme performance hit
#$ActionFileEnableSync on
 
# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf
 
# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging on
 
# File to store the position in the journal
$IMJournalStateFile imjournal.state
 
# Django : 2016-01-03 - certificate files for TLS
# default: unset
$DefaultNetstreamDriverCAFile   /etc/pki/ca-trust/source/anchors/root-ca.nausch.org.pem
$DefaultNetstreamDriverCertFile /etc/pki/tls/certs/rsyslog.vml000037.dmz.nausch.org.certificate.pem
$DefaultNetstreamDriverKeyFile  /etc/pki/tls/private/rsyslog.vml000037.dmz.nausch.org.key.pem
 
$ActionSendStreamDriverAuthMode x509/name
$ActionSendStreamDriverPermittedPeer graylog-server.dmz.nausch.org
#          run driver in TLS-only mode
$ActionSendStreamDriverMode 1
 
#### RULES ####
 
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.*                                                 /dev/console
 
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none                /var/log/messages
 
# The authpriv file has restricted access.
authpriv.*                                              /var/log/secure
 
# Log all the mail messages in one place.
mail.*                                                  -/var/log/maillog
 
 
# Log cron stuff
cron.*                                                  /var/log/cron
 
# Everybody gets emergency messages
*.emerg                                                 :omusrmsg:*
 
# Save news errors of level crit and higher in a special file.
uucp,news.crit                                          /var/log/spooler
 
# Save boot messages also to boot.log
local7.*                                                /var/log/boot.log
 
# Django : 2015-07-14 Logging für OpenLDAP-Server aktiviert
local4.*                                                -/var/log/ldap.log
#
 
# ### begin forwarding rule ###
# The statement between the begin ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
#
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
#$ActionQueueFileName fwdRule1 # unique name prefix for spool files
#$ActionQueueMaxDiskSpace 1g   # 1gb space limit (use as much as possible)
#$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
#$ActionQueueType LinkedList   # run asynchronously
#$ActionResumeRetryCount -1    # infinite retries if host is down
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
#*.* @@remote-host:514
#
# Django : 2015-06-12
#$template GRAYLOGRFC5424,"<%PRI%>%PROTOCOL-VERSION% %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%\n"
#*.* @@10.0.0.117:514;GRAYLOGRFC5424
# Django : 2016-01-03
$template GRAYLOGRFC5424,"<%PRI%>%PROTOCOL-VERSION% %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%\n"
*.* @@10.0.0.117:6514;GRAYLOGRFC5424
#
# ### end of the forwarding rule ###

Zum Aktivieren der Änderungen führen wir nun einmal einen Reboot des rsyslog-Daemon durch.

 # systemctl restart rsyslog.service

Im Syslog unseres Servers wir der erfolgreiche Neustart des rsyslog-Daemon entsprechend positiv vermerkt.

 # tailf /var/log/messages

Jan  4 12:34:45 vml000037 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="28477" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jan  4 12:34:45 vml000037 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="28869" x-info="http://www.rsyslog.com"] start

Rufen wir nun wieder die Web-GUI unseres graylog-Webservers auf, wird sowohl die aktive Verbindung wie auch die bereits übertragenen Daten angezeigt.

 $ firefox https://graylog.nausch.org/system/inputs

Alles in allem können wir feststellen, dass mit einem überschaubaren Aufwand, die Kommunikation zwischen den rsyslog-Clients und unserem graylog-server sicher und nur noch von authorisierten Quellen gestattet werden kann.

• ⇐ Zurück zu Kapitel "Webserverinstallation unter CentOS 7.x"
• Zurück zu Projekte und Themenkapitel
• Zurück zur Startseite