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

wazuh-certs-tool.sh should not hardcode distinguished name #17

Open
majorthorn opened this issue Sep 17, 2023 · 0 comments
Open

wazuh-certs-tool.sh should not hardcode distinguished name #17

majorthorn opened this issue Sep 17, 2023 · 0 comments

Comments

@majorthorn
Copy link

In the lines below should not hardcode the DN as it will hamstring future users into using SOCFORTRESS as their Cert DN. These should either have their values referenced in the tutorial or have an alternate script that references the default Wazuh config DN reference.

eval "openssl req -new -key ${cert_tmp_path}/admin-key.pem -out ${cert_tmp_path}/admin.csr -batch -subj '/C=US/L=Texas/O=SOCFortress/OU=SOCFortress/CN=admin' ${debug}"

C = US
L = Texas
O = SOCFortress
OU = SOCFortress
CN = cname

In my opinion, and its just that an opinion, the tutorials should have scripts that live as if they are deploying a near productions, or have script breaks or input requests to stop the user from using the deployment and inform them of the changes required.

I do not know if I am making sense, it is 2am.

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

No branches or pull requests

1 participant