Secure Socket Layers and Public Key Infrastructure

Secure Socket Layers (SSL) enables the use of digital certificates, certificate authorities, extensive network encryption, and checksums for all network packets.

Starting with v3.0, Privilege Management supports Public Key Infrastructure (PKI) through SSL. This feature enables the use of Privacy Enhanced Mail (PEM) format certificates, private keys, and certificate authority files. The SSL features are controlled through the ssl setting, the ssloptions setting, and the client and server settings.

Many of the SSL settings enable token expansion for some useful strings. These are summarized in the following table.

Symbol Replacement
%% A % character.
%g User’s group ID.
%G User’s group ID number.
%h Local host name. The unqualified name of the current machine.
%H Remote host name of the current machine in Fully Qualified Domain Name (FQDN) format (if available from uname).
%I Unqualified local host name as determined by the network interface.
%L Local host interface name. The local host name, as determined by the network interface, in FQDN format (if available).
%n Program name with neither a prefix of suffix.
%N Program name with a prefix and suffix.
%p Program prefix.
%r Unqualified host name, as determined by the network interface.
%R Remote host interface name. The remote host name, as determined by the network interface, in FQDN format.
%s Program suffix.
%u User’s login ID.
%U User’s UID.

ssl

When set to yes, the ssl setting enables the use of Privilege Management for Unix and Linux SSL features. When set to no, the ssl setting disables the use of these features.

ssl yes
ssl yes
  • Log hosts
  • Policy server hosts
  • Submit hosts
  • Run hosts

restssloptions

  • Version 10.1.0 and earlier: restssloptions setting not available.
  • Version 10.2.0 and later: restssloptions setting available.

The current restssloptions include: TLSMinV1, TLSMinV1.1, TLSMinV1.2, MinHMACMD5, and MinHMACSHA512.

For FIPS compliance, all Privilege Management for Unix and Linux hosts must add MinHMACSHA512 to the restssloptions setting.

ssloptions

  • Version 4.0.0 and later: ssloptions setting available.

The ssloptions setting controls the following system-wide options:

Option Description
ClientCertificates To require certificates on the client side, add ClientCertificates to the ssloptions line.
AllowNonSSL

To communicate with older, non-SSL versions of Privilege Management for Unix and Linux, add AllowNonSSL to your ssloptions line. Doing so allows SSL-enabled versions to communicate with non-SSL versions.

If a Privilege Management for Unix and Linux client is SSL-enabled and the policy server host specifies AllowNonSSL, but not ClientCertificates, then the communications do not use SSL.

TLSMinV1.0, TLSMinV1.1, TLSMinV1.2 When SSL is enabled, this option allows you to set the minimum SSL/TLS value to use in the protocol.
TLSMaxV1.0, TLSMaxV1.1, TLSMaxV1.2 When SSL is enabled, this option allows you to set the maximum SSL/TLS value to use in the protocol.
RequireSSL

To require SSL communications between Privilege Management components without requiring Privilege Management for Unix and Linux client certificates, then add RequireSSL to your ssloptions line.

This option is not compatible with the AllowNonSSL option. If you specify both AllowNonSSL and RequireSSL, then the last one that is specified takes precedence.

SSLFirst

If the SSLFirst option is selected, this option forces the SSL handshake to happen before the Privilege Management for Unix and Linux handshake.

The SSLFirst option must be set on every Privilege Management for Unix and Linux host including clients and servers.

The SSLFirst option is turned on by default in version 10.3.2 and later.

sslverbose If the sslverbose option is selected, server components log informational messages that are sent to error logs, detailing connections, SSL/TLS protocols, and the encryption ciphers used to communicate. This is a debugging and diagnostic option
validateClient

The option validateClient enables Privilege Management for Unix and Linux servers (pbmasterd, pblocald, pblogd) to use SSL verifypeer and verifyhost features to validate the connected client host. Note that pbmasterd is also a client to pblocald, and both pbmasterd and pblocald are clients to pblogd.

This can be used when the client hosts have certificates installed, and the servers’ ssloptions includes the ClientCertificates option (validateClient forces ClientCertificates).

Enabling the validateClient ssloption on the server requires that pb.settings on the server includes the sslservercafile keyword, specifying the CA that signed the client’s certificate. The pb.settings file on the client must include the sslpbruncertfile and sslpbrunkeyfile keywords, specifying the client’s certificate and key. This feature alternatively uses the sslpbruncertdir, sslpbrunkeydir, and sslservercadir keywords.

The pb.settings file on pbmasterd and pblocald must include sslservercertfile and sslserverkeyfile keywords, specifying the client's certificate and key. This feature alternatively uses the sslservercertdir and sslserverkeydir keywords.

Enabling the AllowNonSSL with validateClient results in an error. Non-SSL connections are not allowed with validateClient.

The client host’s hostname should be listed in the Subject Alternative Name (SAN) field of the certificate.

validateServer

The option validateServer enables Privilege Management for Unix and Linux SSL clients to verify the server with the SSL verifypeer and verifyhost features. Note that pbmasterd is a client to pblocald, and both pbmasterd and pblocald are clients to pblogd.

Enabling the validateServer on the client requires that pb.settings on the client includes the sslpbruncafile keyword (sslpbservercafile keyword on pbmasterd and pblocald), specifying the CA that signed the server’s certificate. The pb.settings file on the server must include the sslservercertfile and sslserverkeyfile keywords, specifying the server’s certificate and key. This feature alternatively uses the sslservercertdir, sslserverkeydir, and sslpbruncadir keywords.

Enabling the AllowNonSSL with validateServer results in an error. Non-SSL connections are not allowed with validateServer.

The hostname should be listed in the Subject Alternative Name (SAN) field of the certificate.

The program terminates if invalid values are provided for ssloptions.

ssloptions AllowNonSSL
ssloptions requiressl sslfirst
ssloptions ClientCertificates
ssloptions AllowNonSSL ClientCertificates
requiressl
  • Log hosts
  • Policy server hosts
  • Submit hosts
  • Run hosts

Server-Side SSL

For client hosts where optimized run mode is always used (the submit host is always the run host), a server-side SSL scenario can be set up where the client machine does not need a server key/certificate pair or a client key/certificate pair.

The sslpbruncafile keyword is optional. If sslpbruncafile is specified, sslpbruncafile is the certificate authority (CA) that signed the server’s certificate. If sslpbruncafile is not specified, then the server’s certificate authenticity is not verified.

If the submit host is not the same host as the run host or if a log server is not used, then the pblocald server is used to execute the secured task. pblocald is an SSL server and requires the sslservercafile, sslservercertfile, and sslserverkeyfile settings.

SSL Client Settings

The SSL client settings configure SSL for Privilege Management for Unix and Linux client programs.

sslpbruncadir and sslpbruncafile

  • Version 4.0.0 and later: sslpbruncadir and sslpbruncafile settings available.

These settings specify the path to a certificate authority directory or file.

A certificate authority file is a PEM-formatted file that contains one or more PEM-formatted signature certificates. The programs pbrun, pbksh, and pbsh use these certificate authority files to validate certificates from pbmasterd and pblocald. This file should not contain private keys.

If sslpbruncafile contains an absolute path, then that file is used as the certificate authority file. If sslpbruncafile contains a relative path, then the value of the sslpbruncadir setting is prepended to form an absolute path. The pbrun certificate authority file and certificate authority directory must be owned by root and no one else should have write permission.

These settings enable the parameter substitutions shown in SSL Parameter Substitutions.

sslpbruncafile /secure/ca/pbrun/OurAuthority.pem
sslpbruncadir /secure/ca/pbrun
sslpbruncafile OurAuthority.pem
sslpbruncadir /secure/ca/pbrun sslpbruncafile %N.pem

No default value

Submit hosts

sslpbruncertdir and sslpbruncertfile

  • Version 4.0.0 and later: sslpbruncertdir and sslpbruncertfile settings available.

The sslpbruncertdir and sslpbruncertfile settings specify the path of a Privacy Enhanced Mail (PEM) format certificate file for clients to communicate with pbmasterd and pblocald.

If a full absolute path is provided for sslpbruncertfile, then it is used. If a relative path is provided for sslpbruncertfile, then the directory specified in the sslpbruncertdir setting is prepended to form the certificate file path.

root or the submitting user must own the pbrun certificate file and certificate directory. No one else should have write permission.

These settings allow the parameter substitutions that are shown in SSL Parameter Substitutions.

sslpbruncertfile /secure/certificates/pbrun/pbrun.pem
sslpbruncertdir /secure/certificates/pbrun
sslpbruncertfile pbrun.pem
sslpbruncertdir /home/%u/certificates
sslpbruncertfile %u.pem

No default value

Submit hosts

sslpbruncipherlist

  • Version 4.0.0 and later: sslpbruncertdir setting available.

OpenSSL provides a variety of algorithms that can be used for encryption. The sslpbruncipherlist setting enables the administrator to restrict or promote the set of encryption algorithms that are used by Privilege Management clients to communicate with SSL enabled server services.

These ciphers are limited to the set of ciphers available in the given version of OpenSSL used by the Privilege Management installation.

For more information, please see the Release Notes.

Refer to the following table for the valid values for the sslpbruncipherlist. To specify more than one cipher set, separate the values with colons.

OpenSSL Cipher Set Setting Value
SSL_RSA_WITH_NULL_MD5 NULL-MD5
SSL_RSA_WITH_NULL_SHA NULL-SHA
SSL_RSA_EXPORT_WITH_RC4_40_MD5 EXP-RC4-MD5
SSL_RSA_WITH_RC4_128_MD5 RC4-MD5
SSL_RSA_WITH_RC4_128_SHA RC4-SHA
SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5 EXP-RC2-CBC-MD5
SSL_RSA_EXPORT_WITH_DES40_CBC_SHA EXP-DES-CBC-SHA
SSL_RSA_WITH_DES_CBC_SHA DES-CBC3-SHA
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA EXP-EDH-DSS-DES-CBC-SHA
SSL_DHE_DSS_WITH_DES_CBC_SHA EDH-DSS-CBC-SHA
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA EDH-DSS-DES-CBC3-SHA
SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA EXP-EDH-RSA-DES-CBC-SHA
SSL_DHE_RSA_WITH_DES_CBC_SHA EDH-RSA-DES-CBC-SHA
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA EDH-RSA-DES-CBC3-SHA
sslpbruncipherlist NULL-MD5:EDH-DSS-CBC-SHA
HIGH:!SSLv2:!3DES:!MD5:@STRENGTH

Submit hosts

sslpbrunkeydir and sslpbrunkeyfile

  • Version 4.0.0 and later: sslpbrunkeydir and sslpbrunkeyfile settings available.

The sslpbrunkeyfile and sslpbrunkeydir settings enable you to specify the location of a PEM-formatted private key for the client certificate file that is used to communicate with pbmasterd and pblocald.

If sslpbrunkeyfile is a full path name, then it is used for the private key. If sslpbrunkeyfile does not contain an absolute path, then sslpbrunkeydir is prepended to it.

The clients are usually interactive, so the private keys can be encrypted. The clients prompt for the passphrase when needed. If you are invoking a client non-interactively (for example, from cron), then the private key should not be encrypted.

root or the submitting user must own the private key file and the private key directory. No one else should have read or write permission.

If the key file and directory are not set, then the client looks in the certificate file to see if the key is there. In this case, the certificate file and directory must be read-only and owned by root or the submitting user. No one else should have read or write permission.

These settings enable the parameter substitutions that are shown in SSL Parameter Substitutions.
sslpbrunkeyfile /secure/privatekeys/pbrun.pem
sslpbrunkeydir /secure/privatekeys/
sslpbrunkeyfile %u.pem
sslpbrunkeydir /home/%u/privatekeys
sslpbrunkeyfile %u.pem

No default value

Submit hosts

sslpbrunverifysubject

  • Version 4.0.0 and later: sslpbrunverifysubject setting available.

sslpbrunverifysubject contains a series of regular expressions to check against the policy server’s certificate subject line. If the subject line matches all patterns, then the connection is allowed to proceed. If any of the patterns do not match, then the connection fails.

This example verifies that the CN attribute (common name) matches the host name of the remote machine:
sslpbrunverifysubject /CN=%R/
This example verifies that the O attribute equals Company Name and that the OU attribute starts with Technology:
sslpbrunverifysubject '/O=Company Name/' /OU=Technology

Single quotation marks should surround the attribute if there are embedded spaces.

No default value

Submit hosts

SSL Server Settings

The SSL server settings configure SSL for Privilege Management for Unix and Linux server programs.

sslservercadir and sslservercafile

  • Version 4.0.0 and later: sslservercadir and sslservercafile settings available.

The sslservercadir and sslservercafile settings specify the path to a certificate authority directory or file. A certificate authority file is a PEM-formatted file that contains one or more PEM-formatted signature certificates that are used to validate server certificates. This file should not contain private keys.

If sslservercafile contains an absolute path, then that file is used as the certificate authority file. If sslservercafile contains a relative path, then the value of the sslservercadir setting is prepended to form an absolute path.

The server certificate authority file and certificate authority directory must be owned by root and no one else should have write permission.

These settings allow the parameter substitutions that are shown in SSL Parameter Substitutions.
sslservercafile /secure/ca/servers/OurAuthority.pem
sslservercadir /secure/ca/servers
sslservercafile OurAuthority.pem
sslservercadir /secure/ca/servers sslservercafile %h.pem
/etc/<prefix>pbssl.pem<suffix>
  • GUI hosts
  • Log hosts
  • Policy server hosts
  • Run hosts

sslservercertdir and sslservercertfile

  • Version 4.0.0 and later: sslservercertdir and sslservercertfile settings available.

The sslservercertdir and sslservercertfile settings specify the path of a Privacy Enhanced Mail (PEM) format certificate file for pbmasterd, pblocald, pblogd, and pbguid to communicate with each other or with client programs. If a full absolute path is provided for sslservercertfile, then it is used as specified. If a relative path is provided for sslservercertfile, then the directory that is specified in the sslservercertdir setting is prepended to form the certificate file path.

The server certificate file and certificate directory must be owned by root and no one else should have write permission.

These settings allow the parameter substitutions that are shown in SSL Parameter Substitutions.
sslservercertfile /secure/certificates/servers/pbmasterd.pem
sslservercertdir /secure/certificates/servers
sslservercertfile pbmasterd.pem
sslservercertdir /secure/certificates/servers
sslservercertfile %N.pem

/etc/pbssl.pem

  • GUI hosts
  • Log hosts
  • Policy server hosts
  • Run hosts

sslservercipherlist

  • Version 4.0.0 and later: sslservercipherlist setting available.

OpenSSL provides a variety of algorithms that can be used for encryption. The sslservercipherlist setting enables the administrator to restrict or promote the set of encryption algorithms that are used by Privilege Management servers when they receive communications from SSL enabled clients.

These ciphers are limited to the set of ciphers available in the given version of OpenSSL used by the Privilege Management installation.

To specify more than one cipher set, separate the values with colons.

sslservercipherlist NULL-MD5:EDH-DSS-CBC-SHA
sslservercipherlist HIGH:!SSLv2:!3DES:!MD5:@STRENGTH
  • GUI hosts
  • Log hosts
  • Policy server hosts
  • Run hosts
For more information, please see the following:

sslserverkeydir and sslserverkeyfile

  • Version 4.0.0 and later: sslserverkeydir and sslserverkeyfile settings available.

The sslserverkeyfile and sslserverkeydir settings enable you to specify the location of a PEM- formatted private key for the server certificate file that is used by pbmasterd, pblocald, pblogd, and pbguid to communicate with each other or with client programs.

If sslserverkeyfile is a full path name, then it is used for the private key. If sslserverkeyfile does not contain an absolute path, then sslserverkeydir is prepended to it.

The servers are not interactive, so the private keys should not be encrypted.

The private key file and the private key directory must be owned by root and no one else should have read or write permission.

If the key file and directory are not set, then the daemons look in the certificate file to see if the key is there. In this case, the certificate file and directory must be read-only and owned by root. No one else should have read or write permission.

These settings allow the parameter substitutions that are shown in SSL Parameter Substitutions.
sslserverkeyfile /secure/certificates/serverkeys/pbmasterd.pem
sslserverkeydir /secure/certificates/serverkeys
sslserverkeyfile pbmasterd.pem
sslserverkeydir /secure/certificates/serverkeys
sslserverkeyfile %N.pem
/etc/<prefix>pbssl.pem<suffix>
  • GUI hosts
  • Log hosts
  • Policy server hosts
  • Run hosts

sslserververifysubject

  • Version 4.0.0 and later: sslserververifysubject setting available.

sslserververifysubject contains a series of regular expressions to check against the client’s or other server’s certificates subject line. If the subject line matches all patterns, then the connection is allowed to proceed. If any of the patterns do not match, then the connection fails.

This example verifies that the CN attribute (common name) matches the host name of the remote machine:
sslserververifysubject /CN=%R/
This example verifies that the O attribute equals Company Name and the OU attribute starts with Technology:
sslserververifysubject '/O=Company Name/' /OU=Technology

Single quotation marks should surround the attribute if there are embedded spaces.

No default value

  • GUI hosts
  • Log hosts
  • Policy server hosts
  • Run hosts

Additional Configuration to Improve PMUL Security

Privilege Management for Unix and Linux does not contain a Certificate Authority (CA), therefore certificates generated during install are self-signed, and cannot be used to properly identify the host. Creating and deploying proper x509 certificates, with hostname information in the Subject Alternative Name field, allows Privilege Management for Unix and Linux hosts to properly identify hosts. TLS clients can verify the server’s certificate and hostname by adding the validateServer option to the ssloptions keyword in /etc/pb.settings. For TLS, pbmasterd and pblocald are clients to pblogd. Additionally, servers can validate the certificates and hostnames of the client hosts by adding the validateClient option to the ssloptions keyword in /etc/pb.settings.

Configure Privilege Management for Unix and Linux to use the SSLFirst keyword in /etc/pb.settings. This keyword must have the same value on all hosts in the PMUL domain. The SSLFirst keyword results in SSL/TLS occurring prior to any Privilege Management for Unix and Linux proprietary protocol negotiations that use symmetric keys, reducing any issue with compromised symmetric networkencryption keys.

The TLS ciphers should be changed to disallow anonymous ciphers.

Edit the sslpbruncipherlist and sslservercipherlist entries in /etc/pb.settings:

sslpbruncipherlist      TLSv1.2:!SSLv2:!3DES:!MD5:!ADH:!AECDH:!DHE:!eNULL:@STRENGTH
sslservercipherlist     TLSv1.2:!SSLv2:!3DES:!MD5:!ADH:!AECDH:!DHE:!eNULL:@STRENGTH

Edit the ssl.cipher-list entry in /usr/lib/beyondtrust/pb/rest/etc/pblighttpd.conf:

ssl.cipher-list         = " TLSv1.2:!SSLv2:!3DES:!MD5:!ADH:!AECDH:!DHE:!eNULL:@STRENGTH"

In the following sections the diagram shows the SSL server and SSL client connections between pbmasterd, pblocald, pblogd and pbrun and the table shows the required certificate keywords in pb.settings file on each host when validateServer or validateClient is added to ssloptions.

 

SSL Connections in Default Architecture: Classic pbrun

SSL connections in a default PMUL architecture: classic pbrun

 

On Submithost (pbrun) On Masterhost (pbmasterd) On Loghost (pblogd)

On Runhost (pblocald)

(submithost != runhost) or (pbrun --di) or (pbmasterd --disable_optimized_runmode)

ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

  -  

sslservercertfile

sslserverkeyfile

  -

validateServer

(pbmasterd is client to pblocald, pblogd)

sslservercafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

  -
  -   -  

sslservercertfile

sslserverkeyfile

validateServer sslservercafile
validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -   -   -
  sslpbruncertfile

sslpbrunkeyfile

validateClient sslservercafile  

**sslservercertfile

sslserverkeyfile

  **sslservercertfile

sslserverkeyfile

 

-

 

sslservercertfile

sslserverkeyfile

validateClient sslservercafile  

sslservercertfile

sslserverkeyfile

***sslpbruncertfile

sslpbrunkeyfile

  sslpbruncertfile

sslpbrunkeyfile

 

sslservercertfile

sslserverkeyfile

 

**sslservercertfile

sslserverkeyfile

validateClient sslservercafile

* Mentioning sslpbruncafile with or without validateServer and validateClient options requires pbmasterd and pblocald certificates.

** Mentioning sslservercafile on a SSL client (pbmasterd and pblocald) with or without validateServer and validateClient options always requires certificates from its immediate SSL server or servers.

*** pblocald needs sslpbruncertfile and sslpbrunkeyfile to log finish event.

SSL Connections in Optimized Runmode

PMUL SSL connections in optimized runmode

 

On Submithost (pbrun) On Masterhost (pbmasterd) On Loghost (pblogd)
ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

(for IOLogging and finish event)

  -

validateServer

(pbmasterd is client to pblogd)

sslservercafile  

sslservercertfiel

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -  

-

 

sslpbruncertfile

sslpbrunkeyfile

validateClient

sslservercafile

  **sslservercertfile

sslpbrunkeyfile

  sslpbruncertfile

sslpbrunkeyfile

(for IOLogging and to log finish event)

 

sslservercertfile

sslserverkeyfile

validateClient

sslservercafile

* Mentioning sslpbruncafile with or without validateServer and validateClient options requires pbmasterd and pblogd certificates.

** Mentioning sslservercafile on pbmasterd with or without validateServer and validateClient options always requires certificates from pblogd.

SSL Connections with noreconnect=1 in the Policy

  • noreconnect=1 : pbrun does not connect to pblocald directly

Privilege Management for Unix and Linux SSL connections with noreconnect=1 in the policy

 

On Submithost (pbrun)

On Masterhost (pbmasterd)

noreconnect=1 in the policy

On Loghost (pblogd)

On Runhost (pblocald)

(submithost != runhost) or (pbrun --di) or (pbmasterd --disable_optimized_runmode)

ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

  -  

-

  -

validateServer

(pbmasterd is client to pblocald, pblogd)

sslservercafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

  -
  -   -  

sslservercertfile

sslserverkeyfile

validateServer sslservercafile
validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -   -   -
 

sslpbruncertfile

sslpbrunkeyfile

validateClient sslservercafile  

**sslservercertfile

sslserverkeyfile

  **sslservercertfile

sslserverkeyfile

 

-

 

sslservercertfile

sslserverkeyfile

validateClient sslservercafile  

sslservercertfile

sslserverkeyfile

***sslpbruncertfile

sslpbrunkeyfile

  -  

sslservercertfile

sslserverkeyfile

 

**sslservercertfile

sslserverkeyfile

validateClient sslservercafile

* Mentioning sslpbruncafile with or without validateserver and validateclient options requires pbmasterd certificates.

** Mentioning sslservercafile on a SSL client (pbmasterd and pblocald) with or without validateserver and validateclient options always requires certificates from its immediate SSL server or servers.

*** pblocald needs sslpbruncertfile and sslpbrunkeyfile to log finish event.

SSL Connections with lognoreconnect=1 in the Policy

  • lognoreconnect=1 : pblocald does not connect to pblogd directly and pbrun does not connect to pblocald directly.

PMUL SSL connections with lognoreconnect=1 in the policy

 

On Submithost (pbrun)

On Masterhost (pbmasterd)

lognoreconnect=1 in the policy

On Loghost (pblogd)

On Runhost (pblocald)

(submithost != runhost) or (pbrun --di) or (pbmasterd --disable_optimized_runmode)

ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

  -  

-

  -

validateServer

(pbmasterd is client to pblocald, pblogd)

sslservercafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

  -
  -   -  

-

validateServer

-

(pblocald is not a SSL client/server to pblogd as lognoreconnect=1)

validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -   -   -
 

sslpbruncertfile

sslpbrunkeyfile

validateClient sslservercafile  

**sslservercertfile

sslserverkeyfile

  **sslservercertfile

sslserverkeyfile

 

-

  sslservercertfilesslserverkeyfile validateClient sslservercafile  

-

 

-

(No direct connection between pbrun and pblocald when lognoreconnect=1)

 

sslservercertfile sslserverkeyfile

 

-

validateClient sslservercafile

* Mentioning sslpbruncafile with or without validateServer and validateClient options requires pbmasterd certificates.

** Mentioning sslservercafile on pbmasterd with or without validateserver and validateclient options always requires certificates from pblocald and pblogd.

SSL Connections with pbrunreconnection=1 in the Policy

  • pbrunreconnection=1 : pblocald listens for the connections that are initiated by pbrun under the control of pbmasterd.
  • pbrunreconnection=0 : pbrun listens for the connections that are initiated by pblocald under the control of pbmasterd. This value is the default.

PMUL SSL connections with pbrunreconnection=1 in the policy

On Submithost (pbrun)

On Masterhost (pbmasterd)

pbrunreconnection=1 in the policy

On Loghost (pblogd)

On Runhost (pblocald)

(submithost != runhost) or (pbrun --di) or (pbmasterd --disable_optimized_runmode)

ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

  -  

sslservercertfile

sslserverkeyfile

  -

validateServer

(pbmasterd is client to pblocald, pblogd)

sslservercafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

  -
  -   -  

sslservercertfile

sslserverkeyfile

validateServer sslservercafile
validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -   -   -
  sslpbruncertfile

sslpbrunkeyfile

validateClient sslservercafile  

**sslservercertfile

sslserverkeyfile

  **sslservercertfile

sslserverkeyfile

 

-

 

sslservercertfile

sslserverkeyfile

validateClient sslservercafile  

sslservercertfile

sslserverkeyfile

***sslpbruncertfile

sslpbrunkeyfile

  sslpbruncertfile

sslpbrunkeyfile

 

sslservercertfile

sslserverkeyfile

 

**sslservercertfile

sslserverkeyfile

validateClient sslservercafile

* Mentioning sslpbruncafile with or without validateserver and validateclient options requires pbmasterd and pblocald certificates.

** Mentioning sslservercafile on a SSL client (pbmasterd and pblocald) with or without validateserver and validateclient options always requires certificates from its immediate SSL server or servers.

*** pblocald needs sslpbruncertfile and sslpbrunkeyfile to log finish event.

SSL Connections with pblogdreconnection=1 in the Policy

  • pblogdreconnection=1 : pblocald listens for the connections that are initiated by pblogd under the control of pbmasterd.
  • pblogdreconnection=0 : pblogd listens for the connections that are initiated by pblocald under the control of pbmasterd. This value is the default.

diagram of PMUL SSL connections with pblogdreconndtion=1 in the policy

On Submithost (pbrun)

On Masterhost (pbmasterd)

pblogdreconnection=1 in the policy

On Loghost (pblogd)

On Runhost (pblocald)

(submithost != runhost) or (pbrun --di) or (pbmasterd --disable_optimized_runmode)

ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required ssloptions SSL cert/CA file required
validateServer *sslpbruncafile  

sslservercertfile

sslserverkeyfile

  -  

sslservercertfile

sslserverkeyfile

  -

validateServer

(pbmasterd is client to pblocald, pblogd)

sslservercafile  

sslservercertfile

sslserverkeyfile

 

sslservercertfile

sslserverkeyfile

  -   - validateServer

-

(pblogd is not an SSL client to any host)

  -
  -   -  

sslservercertfile

sslserverkeyfile

validateServer sslservercafile
validateClient

-

(pbrun is not an SSL server at any point, also refer to *)

  -   -   -
  sslpbruncertfile

sslpbrunkeyfile

validateClient sslservercafile  

**sslservercertfile

sslserverkeyfile

  **sslservercertfile

sslserverkeyfile

 

-

 

sslservercertfile

sslserverkeyfile

validateClient sslservercafile  

sslservercertfile

sslserverkeyfile

***sslpbruncertfile

sslpbrunkeyfile

  sslpbruncertfile

sslpbrunkeyfile

 

sslservercertfile

sslserverkeyfile

 

**sslservercertfile

sslserverkeyfile

validateClient sslservercafile

* Mentioning sslpbruncafile with or without validateServer and validateClient options requires pbmasterd and pblocald certificates.

** Mentioning sslservercafile on a SSL client (pbmasterd and pblocald) with or without validateserver and validateclient options always requires certificates from its immediate SSL server or servers.

*** pblocald needs sslpbruncertfile and sslpbrunkeyfile to log finish event.