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

Encrypt config file #2928

Closed
mike7ang1rdz opened this issue Oct 19, 2023 · 2 comments
Closed

Encrypt config file #2928

mike7ang1rdz opened this issue Oct 19, 2023 · 2 comments

Comments

@mike7ang1rdz
Copy link

Hello,
I have a use case when I distribute mosquitto along with an local app that works in offline mode, mosquitto holds messages and when the computer gets internet connection mosquttio forward messages using a bridge. However, the bridge (config file) has a plaintext user name and password which I don't like.

Is there a way to encrypt the config file or encrypt the bridge password? or any work around?

Thank you.

@Daedaluz
Copy link
Contributor

Daedaluz commented Oct 19, 2023

I don't think there is a way today, unless you encrypt the whole config and then decrypt before starting the broker.

Anyway, how would you keep the key secret?
And if you have a way, why can't the whole config be in this location?

Otherwise, I think (not 100) that mosquitto can use mtls, and you could have the key stored on some other secure location, like a tpm.

@mike7ang1rdz
Copy link
Author

It would be nice if config is encrypted just as the passwords file.

I'm going to use TLS and the cert is decrypted before start the service, basically a combination of your suggestions

Thanks,

I don't think there is a way today, unless you encrypt the whole config and then decrypt before starting the broker.

Anyway, how would you keep the key secret? And if you have a way, why can't the whole config be in this location?

Otherwise, I think (not 100) that mosquitto can use mtls, and you could have the key stored on some other secure location, like a tpm.

It would be nice if config is encrypted just as the passwords file.

I'm going to use TLS and the cert is decrypted before start the service, basically a combination of your suggestions

Thanks,

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants