Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle '\n' line breaks in PEM-encoded SSL/TLS certificates #92

Closed
wants to merge 1 commit into from
Closed

Handle '\n' line breaks in PEM-encoded SSL/TLS certificates #92

wants to merge 1 commit into from

Commits on Jan 25, 2021

  1. Handle '\n' line breaks in PEM-encoded SSL/TLS certificates 

    For example Podman, handling OCI containers, does not seem to have
a way to pass multi-line strings via env files (and Docker seems to
have the same issue at least outside of docker-compose). Thus this
change allows 'LDAP_CA_CERT' to handle a string with '\n', because
currently only 0x0A aka LF might work. An example for additionally
supported format:

LDAP_CA_CERT=-----BEGIN CERTIFICATE-----\n...\n...\n...\n-----END CERTIFICATE-----

See also: #91
    @robert-scheck
    robert-scheck committed Jan 25, 2021
    Configuration menu
    Copy the full SHA
    e15326c View commit details
    Browse the repository at this point in the history