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

How to handle multiple IPs in CSRParams ip_address field in gnoi cert #31

Open
matibens opened this issue Dec 4, 2019 · 4 comments
Open

Comments

@matibens
Copy link

matibens commented Dec 4, 2019

Its quite common scenario that you want to cover multiple IPs in one certificate via subjectAltName, do you have any recommendation how to implement this in gnoi cert?
Can we just send comma separated list of IPs in ip_address field and parse it on target?

@samribeiro samribeiro self-assigned this Dec 5, 2019
@samribeiro
Copy link
Member

Hi @matibens, the x509 Certificate IPAddresses SAN is clearly a list of IP addresses. Given that the gnoi cert proto states ip_address in singular I would settle that it only supports one IP address and avoid possible ambiguities by stating that it could use comma separated values. Therefore I believe we have a gap here that can be covered with a simple proto agumentation. Infact I think it would be of use to clearly state what are Extensions and what are SANs in the CSR.

@matibens
Copy link
Author

Hi @samribeiro, do you mean something like repeated CertificateExtenstion message in CSRParams? CertificateExtenstion could include some oneof with messages for specific extensions.
Or do you have something more sophisticated in mind?

@samribeiro
Copy link
Member

For simplicity I would settle with just the SANs:

message CSRParams {

  <...>

  // SANs for x509 certificates.
  repeated string dns_names = 12
  repeated string email_addresses = 13
  repeated string ip_ddresses = 14
  repeated string uris = 15

}

@matibens
Copy link
Author

That also works for us, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants