You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "taopanwoaini (via GitHub)" <gi...@apache.org> on 2023/03/28 12:56:27 UTC
[GitHub] [shardingsphere-elasticjob] taopanwoaini opened a new issue, #2201: Database password may be compromised
taopanwoaini opened a new issue, #2201:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2201
## Question
**For English only**, other languages will not accept.
Before asking a question, make sure you have:
- Googled your question.
- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere-elasticjob/issues).
- Read documentation: [ElasticJob Doc](https://shardingsphere.apache.org/elasticjob/current/en/overview/).
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will **close it**.
Thanks for see this question!
today , i find the config of job in zookeeper, and this config context contain ( username, password, ip:port:url ) for my mysql db;
i think , that will expose my database info;
i do not konw why do this of design?
appliction is has datasource already , but Putting the configuration into the zookeeper is something I cannot understand;
and it makes me feel scared;
thanks you answering!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Database password may be compromised [shardingsphere-elasticjob]
Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian closed issue #2201: Database password may be compromised
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2201
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] linghengqian commented on issue #2201: Database password may be compromised
Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #2201:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2201#issuecomment-1725387071
- One design issue involved here is that we should not provide this encryption operation on the ElasticJob side. We always assume that everything with ElasticJob occurs in an intranet environment, and this includes Zookeeper Server.
- I think cryptographic behavior like this should be left to the user to try to handle themselves, or expose a configurable SPI on the ElasticJob side.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Database password may be compromised [shardingsphere-elasticjob]
Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #2201:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2201#issuecomment-2451422645
- Consider https://shardingsphere.apache.org/elasticjob/current/en/user-manual/configuration/external-integration/sasl/ . Please enable SASL for Zookeeper Server directly. Zookeeper Server should not expose access to itself directly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org