-
Notifications
You must be signed in to change notification settings - Fork 757
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
CRL: decode stored crl data before display #5965
Conversation
decode existing crl text
|
This is all a bit strange... if we save base64 encoded data and expect users to paste base64 encoded data (they certainly cannot paste binary data into a textarea very well) where is the need for any sort of decode/encode internally? |
|
@fichtner Hi! hm..if we encode user input for imorted/existing crl at core/src/www/system_crlmanager.php Lines 219 to 221 in f782ccb
i think we need to decode it before display (or we will double encode it later on save? ;) |
Do we expect base64 encoded data though? |
|
since all other certs data is encoded in conf (keys, internal crl's etc) i found it quiet logical ) |
|
I don't think we double-encode all PEM related input. It is what it is (and there could be more bugs). |
|
yep. and, for example, on the core/src/www/system_camanager.php Lines 168 to 179 in 0592276
Or did I miss the thread somewhere? |
|
@kulikov-a Thanks! |
|
Thanks!) |
(cherry picked from commit 88011ed)
Hi!
ref. https://forum.opnsense.org/index.php?topic=29937.0
Turned out that administrator may accidentally break the imported CRL by clicking Save when viewing crl data:
CRL datafield shows encoded string.Thanks!