Rainer Gerhards 919d409e0a Add 'doc/' from commit 'a001c0e188ee266a3face91efe0211fff5c07043'
git-subtree-dir: doc
git-subtree-mainline: 0d1c4ffdd28ddfd1ec13bfcd41597360ac077678
git-subtree-split: a001c0e188ee266a3face91efe0211fff5c07043
2025-06-14 17:45:10 +02:00

74 lines
1.8 KiB
ReStructuredText

GSSAPI module support in rsyslog v3
===================================
What is it good for.
- client-serverauthentication
- Log messages encryption
Requirements.
- Kerberos infrastructure
- rsyslog, rsyslog-gssapi
Configuration.
Let's assume there are 3 machines in Kerberos Realm:
- the first is running KDC (Kerberos Authentication Service and Key
Distribution Center),
- the second is a client sending its logs to the server,
- the third is receiver, gathering all logs.
1. KDC:
- Kerberos database must be properly set-up on KDC machine first. Use
kadmin/kadmin.local to do that. Two principals need to be add in our
case:
#. sender@REALM.ORG
- client must have ticket for principal sender
- REALM.ORG is kerberos Realm
#. host/receiver.mydomain.com@REALM.ORG - service principal
- Use ktadd to export service principal and transfer it to
/etc/krb5.keytab on receiver
2. CLIENT:
- set-up rsyslog, in /etc/rsyslog.conf
- $ModLoad omgssapi - load output gss module
- $GSSForwardServiceName otherThanHost - set the name of service
principal, "host" is the default one
- \*.\* :omgssapi:receiver.mydomain.com - action line, forward logs to
receiver
- kinit root - get the TGT ticket
- service rsyslog start
3. SERVER:
- set-up rsyslog, in /etc/rsyslog.conf
- $ModLoad `imgssapi <imgssapi.html>`_ - load input gss module
- $InputGSSServerServiceName otherThanHost - set the name of service
principal, "host" is the default one
- $InputGSSServerPermitPlainTCP on - accept GSS and TCP connections
(not authenticated senders), off by default
- $InputGSSServerRun 514 - run server on port
- service rsyslog start
The picture demonstrate how things work.
.. figure:: gssapi.png
:align: center
:alt: rsyslog gssapi support
rsyslog gssapi support