rabbitmqctl encode accepts plain text values #4216
-
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
CLI commands that operate on passwords do accept them via standard input. It is not meant to be used on production nodes. Used it to encode a value and use whatever configuration generation tooling you use |
Beta Was this translation helpful? Give feedback.
-
Curiously, both the passphrase and the value encrypted can in practice be considered sensitive. So which one should be accepted via standard input? Or both? I wonder if it would have any unintended consequences. Doing that for the passphrase would be trivial, as it is something that |
Beta Was this translation helpful? Give feedback.
-
See #4258. |
Beta Was this translation helpful? Give feedback.
CLI commands that operate on passwords do accept them via standard input.
rabbitmqctl encode
does not.It is not meant to be used on production nodes. Used it to encode a value and use whatever configuration generation tooling you use
to deploy it.