TLSMGR(8)

πŸ“¦
version 3.11.7 Β· 2 versions
  • 3.11.7 Β· alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 11.0 Β· nixpkgs unstable
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ NAME ✨

okay so bestie, welcome to tlsmgr β€” the Postfix TLS session cache and PRNG manager πŸ’– (it lives in the System Manager's Manual, section 8, daemon territory, iykyk)


πŸŽ€ SYNOPSIS πŸŽ€

tlsmgr [generic Postfix daemon options]

πŸ’… DESCRIPTION πŸ’…

The tlsmgr(8) runs the Postfix TLS session caches. It stores and retrieves cache entries whenever smtpd(8) and smtp(8) processes ask for them, and it periodically yeets out the entries that have expired. housekeeping queen πŸ‘‘

It also runs the PRNG (pseudo random number generator) pool. It answers queries from the smtpd(8) and smtp(8) processes so they can seed their own internal PRNG pools. sharing is caring fr fr 🫢

The tlsmgr(8)'s PRNG pool gets initially seeded from an external source β€” that's EGD, /dev/urandom, or a regular file. Then it gets updated at configurable pseudo-random intervals with data from that external source. It also gets updated periodically with data from TLS session cache entries and with the time of day, and it gets updated with the time of day every single time a process requests tlsmgr(8) service. it's giving constantly-refreshed 🌸

And it saves the PRNG state to an exchange file periodically and when the process terminates, then reads the exchange file back when it's initializing its PRNG. save your work bestie πŸ’Ύ


πŸ”’ SECURITY πŸ”’

The tlsmgr(8) is not security-sensitive. The code that maintains the external and internal PRNG pools does not "trust" the data that it manipulates, and the code that maintains the TLS session cache does not touch the contents of the cached entries β€” except for seeding its internal PRNG pool. no snooping, just vibes ✨

The tlsmgr(8) can be run chrooted and with reduced privileges. At process startup it connects to the entropy source and the exchange file, and it creates or truncates the optional TLS session cache files.

With Postfix version 2.5 and later, the tlsmgr(8) no longer uses root privileges when opening cache files. These files should now be stored under the Postfix-owned data_directory. As a migration aid, an attempt to open a cache file under a non-Postfix directory is redirected to the Postfix-owned data_directory, and a warning is logged. glow up πŸ’…


🩺 DIAGNOSTICS 🩺

Problems and transactions are logged to syslogd(8) or postlogd(8). it will tell on you (lovingly) πŸ’€


πŸ› BUGS πŸ›

There is no automatic means to limit the number of entries in the TLS session caches and/or the size of the TLS cache files. so it will simply keep growing, no cap 😭


βš™οΈ CONFIGURATION PARAMETERS βš™οΈ

Changes to main.cf are not picked up automatically, because tlsmgr(8) is a persistent process. Use the command "postfix reload" after a configuration change. she does not check her notifications, you must ping her directly πŸ“²

The text below provides only a parameter summary. See postconf(5) for more details including examples.

🌈 TLS SESSION CACHE 🌈

  • lmtp_tls_loglevel (0) β€” The LMTP-specific version of the smtp_tls_loglevel configuration parameter.
  • lmtp_tls_session_cache_database (empty) β€” The LMTP-specific version of the smtp_tls_session_cache_database configuration parameter.
  • lmtp_tls_session_cache_timeout (3600s) β€” The LMTP-specific version of the smtp_tls_session_cache_timeout configuration parameter.
  • smtp_tls_loglevel (0) β€” Enable additional Postfix SMTP client logging of TLS activity.
  • smtp_tls_session_cache_database (empty) β€” Name of the file containing the optional Postfix SMTP client TLS session cache.
  • smtp_tls_session_cache_timeout (3600s) β€” The expiration time of Postfix SMTP client TLS session cache information.
  • smtpd_tls_loglevel (0) β€” Enable additional Postfix SMTP server logging of TLS activity.
  • smtpd_tls_session_cache_database (empty) β€” Name of the file containing the optional Postfix SMTP server TLS session cache.
  • smtpd_tls_session_cache_timeout (3600s) β€” The expiration time of Postfix SMTP server TLS session cache information.

🎲 PSEUDO RANDOM NUMBER GENERATOR 🎲

  • tls_random_source (see postconf -d output) β€” The external entropy source for the in-memory tlsmgr(8) pseudo random number generator (PRNG) pool.
  • tls_random_bytes (32) β€” The number of bytes that tlsmgr(8) reads from $tls_random_source when (re)seeding the in-memory pseudo random number generator (PRNG) pool.
  • tls_random_exchange_name (see postconf -d output) β€” Name of the pseudo random number generator (PRNG) state file that is maintained by tlsmgr(8).
  • tls_random_prng_update_period (3600s) β€” The time between attempts by tlsmgr(8) to save the state of the pseudo random number generator (PRNG) to the file specified with $tls_random_exchange_name.
  • tls_random_reseed_period (3600s) β€” The maximal time between attempts by tlsmgr(8) to re-seed the in-memory pseudo random number generator (PRNG) pool from external sources.

🧁 MISCELLANEOUS CONTROLS 🧁

  • config_directory (see postconf -d output) β€” The default location of the Postfix main.cf and master.cf configuration files.
  • data_directory (see postconf -d output) β€” The directory with Postfix-writable data files (for example: caches, pseudo-random numbers).
  • daemon_timeout (18000s) β€” How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer.
  • process_id (read-only) β€” The process ID of a Postfix command or daemon process.
  • process_name (read-only) β€” The process name of a Postfix command or daemon process.
  • syslog_facility (mail) β€” The syslog facility of Postfix logging.
  • syslog_name (see postconf -d output) β€” A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix 3.3 and later:

  • service_name (read-only) β€” The master.cf service name of a Postfix daemon process.

πŸ‘€ SEE ALSO πŸ‘€


πŸ“š README FILES πŸ“š

Use "postconf readme_directory" or "postconf html_directory" to locate this information.

TLS_README, Postfix TLS configuration and operation


πŸ“œ LICENSE πŸ“œ

The Secure Mailer license must be distributed with this software. read it, respect it 🫑


πŸ•°οΈ HISTORY πŸ•°οΈ

This service was introduced with Postfix version 2.2. a true OG πŸ‘‘


πŸ’– AUTHOR(S) πŸ’–

Lutz Jaenicke BTU Cottbus Allgemeine Elektrotechnik Universitaetsplatz 3-4 D-03044 Cottbus, Germany

Adapted by:

Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA

Wietse Venema Google, Inc. 111 8th Avenue New York, NY 10011, USA


okay bestie that's the whole thing, and yes I read every single line of the fine print so you don't have to πŸ’… this was tlsmgr(8) from the System Manager's Manual β€” go forth and manage those TLS session caches, you absolute icon 🌟 mwah πŸŽ€

πŸ“¦ where this page comes from