You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certificate validation will return an error message (http-msg 400) if no public/private key is sent, but will continue processing and still end up calling (certs-update), because (http-msg 400) isn't final.
Luckily the backend scripts in Jidoteki Admin have safeguards and will return 1 (and fail) if there's no public/private key file, but this should still be corrected.
The bug can be found in the code here. It's a bit subtle, but essentially on L50 after calling (http-msg 400), the next condition (if Private.. will be called. Doh. Not what we expected.. 🤕 🌴
The text was updated successfully, but these errors were encountered:
Certificate validation will return an error message
(http-msg 400)
if no public/private key is sent, but will continue processing and still end up calling(certs-update)
, because(http-msg 400)
isn't final.Luckily the backend scripts in Jidoteki Admin have safeguards and will return 1 (and fail) if there's no public/private key file, but this should still be corrected.
The bug can be found in the code here. It's a bit subtle, but essentially on L50 after calling
(http-msg 400)
, the next condition(if Private..
will be called. Doh. Not what we expected.. 🤕 🌴The text was updated successfully, but these errors were encountered: