-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Link OSS #18228
Link OSS #18228
Conversation
grpcServer := grpc.NewServer( | ||
grpc.KeepaliveParams(keepalive.ServerParameters{ | ||
Time: 2 * time.Second, | ||
}), | ||
grpc.MaxSendMsgSize(math.MaxInt32), | ||
grpc.MaxRecvMsgSize(math.MaxInt32), | ||
) |
Check failure
Code scanning / Semgrep Scanner
Found an insecure gRPC server without 'grpc.Creds()' or options with credentials. This allows for a connection without encryption to this server. A malicious attacker could tamper with the gRPC message, which could compromise the machine. Include credentials derived from an SSL certificate in order to create a secure gRPC connection. You can create credentials using 'credentials.NewServerTLSFromFile("cert.pem", "cert.key")'.
grpcServer := grpc.NewServer( | ||
grpc.KeepaliveParams(keepalive.ServerParameters{ | ||
Time: 2 * time.Second, | ||
}), | ||
grpc.MaxSendMsgSize(math.MaxInt32), | ||
grpc.MaxRecvMsgSize(math.MaxInt32), | ||
) |
Check failure
Code scanning / Semgrep Scanner
Found an insecure gRPC server without 'grpc.Creds()' or options with credentials. This allows for a connection without encryption to this server. A malicious attacker could tamper with the gRPC message, which could compromise the machine. Include credentials derived from an SSL certificate in order to create a secure gRPC connection. You can create credentials using 'credentials.NewServerTLSFromFile("cert.pem", "cert.key")'.
@@ -0,0 +1,46 @@ | |||
syntax = "proto3"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just raising an idea here. We have a subdirectory for node status protobuf file. Would it make sense to move all protobuf files for other capabilities there too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, that was my thinking too. We'll definitely need to do that but was thinking of doing it in a separate PR. I didn't want to introduce too many structural changes yet.
Looks great! Just posted a couple refactoring comments. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I just have one last question in the change log.
* add Link config, init, and capabilities * add node status proto * bump protoc version to 3.21.9 * make proto * adding link tests * remove wrapped link * add changelog entry * update changelog entry
No description provided.