php / php/doc-en

openssl_csr_export($csr, $csrout, true); : issue

Open
#4,665 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Extension: openssl
Dominant language
XML
Stars
596
Forks
890
Avg merge
1d 15h
Merged PRs (30d)
55

Description

From manual page: https://php.net/function.openssl-csr-export


Hi
When I want to export a CSR, the variable returns a bad format.
This is the result :
-----BEGIN CERTIFICATE REQUEST----- MIIC9DCCAdwCAQAwga4xCzAJBgNVBAYTAkdCMREwDwYDVQQIDAhTb21lcnNldDEU MBIGA1UEBwwLR2xhc3RvbmJ1cnkxHzAdBgNVBAoMFlRoZSBCcmFpbiBSb29tIExp bWl0ZWQxHzAdBgNVBAsMFlBIUCBEb2N1bWVudGF0aW9uIFRlYW0xFDASBgNVBAMM C1dleiBGdXJsb25nMR4wHAYJKoZIhvcNAQkBFg93ZXpAZXhhbXBsZS5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCy24RXClmumj4DBc73+7Bpdx0l jJ61OcMgQAjIdQkwXg97gtDlyfeYOf20KueKIuxWBng7TAvuFo9CvtHAVkcRKpLk NiABlUYLO+z6SJZUMgCJH9K2zVgyKhI5l6M6qxXkHhfIZth1n9QbQtJJc1Tfz7Tu zbRlvigXw1kb2HL98SYH5G8VgMPQtPLV190+BbqZkOnlBfPDzz7OBNrReFwmGShQ nkkoYsZhOhK8O8lOsJ+uRAccSvtsWGlO1F0fmixrbh0xNHraFyPqf8SluXT+hMnK CrA75v3nN/AMoYBSMw6LDrdNRfIs7sIoOoBSLFyypvpe458smfYdHKq4hL85AgMB AAGgADANBgkqhkiG9w0BAQsFAAOCAQEAGAHL/f1ZD7F7EYkBVMeiQzqcGolYcln/ +hdnVGJAikhL+MXQkGObEClSryW4ZkTvh++R19DCNRr5dVYEVDCJUiUSxcGXoSA/ AV8Vz9NWpg3ZrB4nbJ6KtQJGIg1vHkcwpnOVFr7R/v86BQ3h6yRIHYmurlJ9tBqJ OHHjrscg9AWJVjDhWvegtLYcjmQfvDfRLAmw5qTlJFPvLYHynrYcfeudo99Z4lLP //5VMNYU9UopocMY+vz0LD7uyerRcyx5yku0jfDBLteXjuvtNymXCGA/S+/WFNG4 5uUD6UmekNMzzNpEp7ewwGm+hpKPCX1AGF/31iyBDczpa0unJOkaCA== -----END CERTIFICATE REQUEST-----

In fact, when I try to read it with openssl with this command --> openssl_csr_export($csr, $csrout, true);
openssl req -text -in csrout --> openssl failed.

In fact, the problem are the blocks are segments separated by spaces (20 in ASCII) instead of to have "line feed" (10 in ASCII).
So if I change manuelly 20 to 10, so openssl can read the CSR

All that can be read/modified with notepad with option hexa.

Regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked openssl_csr_export manual page and reproduce the reported output with the shown openssl req -text command. Compare the documented behavior with the observed formatting and determine whether the page needs clarification or a corrected example. Done means the documentation accurately explains the output format and gives readers a verifiable command.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.