We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
无论是携程的apollo还是nacos,貌似配置信息最后存在数据库都是明文的,这个有打算存在数据库的时候之前加密吗? 数据库沦陷,全公司的配置信息都可以被获取了。
The text was updated successfully, but these errors were encountered:
是说配置加密存储功能吗? 目前还没有提供这个功能。 可以考虑在之后把配置数据整体加密存储。
Sorry, something went wrong.
是的,携程apollo貌似是叫开发们自己加密存储,但是我觉得不现实,毕竟各个开发水平不一。 主要是配置中心太核心,数据库被拿下,基本公司配置信息都可以获取。
整个配置统一加密 统一解密是可以的, 但是做不到对其中某一些加密,某一些解密。
而且这块考虑拓展性,需要封装成插件或SPI,允许用户配置自己的的加解密算法,具体方案还需要再讨论一下。
No branches or pull requests
无论是携程的apollo还是nacos,貌似配置信息最后存在数据库都是明文的,这个有打算存在数据库的时候之前加密吗?
数据库沦陷,全公司的配置信息都可以被获取了。
The text was updated successfully, but these errors were encountered: