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.

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

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

Conversation

robert-scheck
Copy link
Contributor

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

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
Copy link
Contributor Author

Closing because upstream code has been moved (and there wekan/wekan#3485 as clone has been merged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant