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

Minor Security Improvement: Make Use of "protectedNative" and "encryptedNative" for Sensitive Data #534

Open
stevenengland opened this issue Mar 11, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@stevenengland
Copy link

Hi there,

I recognized that the native keys called
authToken
clientAuthToken
pin
in the io-package.json file that seem to contain sensitive data do not have counterparts in
encryptedNative
protectedNative
Thus the values will be stored in plain text and will be accessable by other adapters. See https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter for more information for those two arrays.

Maybe in of the next releases you could bring this imrovement in.
Hint: Adjusting these values would mean to release another major version of the adapter.

@mcm1957 mcm1957 added the enhancement New feature or request label Mar 11, 2024
GermanBluefox added a commit that referenced this issue May 24, 2024
@GermanBluefox
Copy link
Member

Adding of encryptedNative is not possible without breaking.
may be when major version changes

GermanBluefox added a commit that referenced this issue May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants