Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

smortex
Copy link
Contributor

@smortex smortex commented Jun 29, 2025

When building an CRL from scratch, the crl member variable has no value, and when calling to_pem on the object, the following value is returned instead of the actual CRL:

-----BEGIN X509 CRL-----
MAA=
-----END X509 CRL-----

The function getCRL() return the crl member variable if it is non-null, and generate the CRL and store it in this variable otherwise. It seems adequate to use this getter function rather than accessing the member variable directly.

Fixes #163

When building an CRL from scratch, the `crl` member variable has no
value, and when calling `to_pem` on the object, the following value is
returned instead of the actual CRL:

```
-----BEGIN X509 CRL-----
MAA=
-----END X509 CRL-----
```

The function `getCRL()` return the `crl` member variable if it is
non-null, and generate the CRL and store it in this variable otherwise.
It seems adequate to use this getter function rather than accessing the
member variable directly.

Fixes jruby#163
@kares kares merged commit 9dd7159 into jruby:master Jul 25, 2025
0 of 21 checks passed
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.

Inconsistent handling of internal state in CRL
2 participants