Open werwaznadn opened 9 months ago
Hey,
I have tried some time ago same configuration and experienced the same result. Looking forward to see resolution.
Bump.
Thank you for the detailed bug report. We currently don't test with the tcp
transport backend, only with zeromq
. It's clearly a bug we need to look at.
Can you share more information on why you want to use tcp
over zeromq
? Having more background information will help us with prioritizing this bug appropriately.
Thank you for the detailed bug report. We currently don't test with the
tcp
transport backend, only withzeromq
. It's clearly a bug we need to look at.Can you share more information on why you want to use
tcp
overzeromq
? Having more background information will help us with prioritizing this bug appropriately.
Hi @agraul, In order to secure the traffic between minion and Master, we wanted to implement mutual TLS cert verification. Hence, this was only possible if we change the protocol to TCP as we found that zeromq does not support TLS client cert verification.
That's correct, Salt with zeromq does not use TLS client cert verification. What advantages do you expect from mTLS over the built-in authentication with self-generated public/private key-pairs?
That's correct, Salt with zeromq does not use TLS client cert verification. What advantages do you expect from mTLS over the built-in authentication with self-generated public/private key-pairs?
Hi @agraul in order to secure minion - master communication when used on public internet.
Hi @shivamsaraiya!
To elaborate agraul's answer a bit further:
In short: Communication between Salt master and minion is already encrypted (afaik, you cannot even disable this).
Source: https://docs.saltproject.io/salt/user-guide/en/latest/topics/security.html
Problem description
Hello
I enabled tcp communication for salt minion-master. After that action remote commands execution via uyuni Ui stopped working. Ui is not able to get existing minions.
The same problem occurs during any highstate execution via uyuni UI. Commands executed via salt cli works fine. When tcp transport is disabled everything works fine from UI.
Setup Uyuni VM running on a public cloud
/etc/salt/master.d/ssl.conf transport: tcp
Steps to reproduce
UyuniUI -> Salt -> Remote Commands -> Find targets on master VM: journalctl --follow -u salt-master
Uyuni version
Uyuni proxy version (if used)
No response
Useful logs
Events monitored during remote_command execution:
Communication between master and minion works fine. tasks executed via cli works:
Additional information
No response