Skip to content

Make it possible to specify encrypted values in rabbitmq conf#11989

Merged
michaelklishin merged 6 commits intomainfrom
mk-encrypted-values-in-rabbitmq-conf
Aug 13, 2024
Merged

Make it possible to specify encrypted values in rabbitmq conf#11989
michaelklishin merged 6 commits intomainfrom
mk-encrypted-values-in-rabbitmq-conf

Conversation

@michaelklishin
Copy link
Copy Markdown
Collaborator

This is an extension of an existent advanced.config feature:

default_user = bunnies-444
default_pass = encrypted:F/bjQkteQENB4rMUXFKdgsJEpYMXYLzBY/AmcYG83Tg8AOUwYP7Oa0Q33ooNEpK9
definitions.tls.cacertfile = /tmp/tls-gen/basic/result/ca_certificate.pem
definitions.tls.certfile   = /tmp/tls-gen/basic/result/client_sunnyside_certificate.pem
definitions.tls.keyfile    = /tmp/tls-gen/basic/result/client_sunnyside_key.pem
definitions.tls.password   = encrypted:0GhvdGjqQ/EAPqr27/PtLj04ikzC7p4IBmM6X7Vqk4fDJGrCnXf5VV4MTAOyPQV5

This makes possible to specify an encrypted
value in rabbitmq.conf using a prefix.

For example, to specify a default user password
as an encrypted value:

``` ini
default_user = bunnies-444
default_pass = encrypted:F/bjQkteQENB4rMUXFKdgsJEpYMXYLzBY/AmcYG83Tg8AOUwYP7Oa0Q33ooNEpK9
```

``` erl
[
  {rabbit, [
      {config_entry_decoder, [
             {passphrase, <<"bunnies">>}
       ]}
    ]}
].
```
'ctl encode' is unfortunately name and targets
advanced.config commands.

This introduce a command that targets 'rabbitmq.conf'
values and has a more specific name.

Eventually 'ctl encode' will be aliased and deprecated,
although we still do not have an aliasing mechanism
and it won't be in scope for 4.0.
@michaelklishin michaelklishin added this to the 4.0.0 milestone Aug 13, 2024
@michaelklishin michaelklishin merged commit dad09e6 into main Aug 13, 2024
@michaelklishin michaelklishin deleted the mk-encrypted-values-in-rabbitmq-conf branch August 13, 2024 22:48
michaelklishin added a commit that referenced this pull request Aug 14, 2024
Make it possible to specify encrypted values in rabbitmq conf (backport #11989)
michaelklishin added a commit that referenced this pull request Mar 23, 2026
…keys

When the support for tagged values in `rabbitmq.conf` was introduced,
not all candidate keys were updated to include it.

This PR updates a few more sensitive `rabbitmq.conf` keys
to support `encrypted:...` values.

References #11989.
mergify Bot pushed a commit that referenced this pull request Mar 23, 2026
…keys

When the support for tagged values in `rabbitmq.conf` was introduced,
not all candidate keys were updated to include it.

This PR updates a few more sensitive `rabbitmq.conf` keys
to support `encrypted:...` values.

References #11989.

(cherry picked from commit e07cdf9)
mergify Bot pushed a commit that referenced this pull request Mar 23, 2026
…keys

When the support for tagged values in `rabbitmq.conf` was introduced,
not all candidate keys were updated to include it.

This PR updates a few more sensitive `rabbitmq.conf` keys
to support `encrypted:...` values.

References #11989.

(cherry picked from commit e07cdf9)
(cherry picked from commit 81fc0a8)
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

Successfully merging this pull request may close these issues.

1 participant