Hi Mark,
Thanks for your last message. I will be adding the information provided to the Feature Request that we’ve already filed, they will be useful! I will be closing this private issue as I understand that no changes are required to your specific project but more of a possible general improvement of the product. You can follow the progress of the possible implementation of this feature here <http://issuetracker.google.com/issues/80295154>. Please note that there are no ETAs or guarantees of implementation for feature requests. Thank you for your understanding. On Thursday, January 10, 2019 at 5:23:17 PM UTC-5, Mark Kubacki wrote: > > Hi Nicolas, > > Thanks for relying this as request for enhancement to the engineering team! > > Just so we get the wording right—I am neither asking for customized TLS > settings/versions, nor non-standard cipher suites. It's about the > certificate, which I'd like to be an "ECDSA one". That is, the > public-private key pair won't be RSA with 2048 bit but instead for ECDSA > with curve P-256. > > Your stack will adjust the available cipher suites accordingly, > automatically, being presented that kind of certificate. > > You've opened a bug for my domain, thanks. I've followed up there. Again, > this email is just a clarification. > > -- > Cheers! > Mark Kubacki > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/303909dc-676d-4e97-975e-fc28877438ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
