You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have best practices in the core of the SDK. People developing with it should have a speed-up in developer experience but also adhere to security practices.
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
Describe the proposal
We should have best practices in the core of the SDK. People developing with it should have a speed-up in developer experience but also adhere to security practices.
gRPC in the ecosystem today always utilizes the
createInsecure()
method which creates an unencrypted channel and exposes channel credentials. (more: https://www.trendmicro.com/en_us/research/20/h/how-unsecure-grpc-implementations-can-compromise-apis.html)We should switch to utilizing
createSsl()
for several reason, but the main ones being:createFromMetadataGenerator
if we are not using an Ssl Channel)Extra info can be found here as well: wechaty/puppet-service#124 and https://github.com/wechaty/puppet-service/pull/159/files
The text was updated successfully, but these errors were encountered: