Hello, 

I see that you have deleted your previous answer that said *"Although not 
the recommended option, creating a ticket with GCP tech support is an 
option for existing customers."*
This is quite annoying, and costly as well, because based on your previous 
answer, and since I was indeed an existing customer (since 2017), I went 
ahead and subscribed to paid support for this project.   I had understood, 
based on your answer, that this would allow we to have the TLS 
configuration modified.
I imagine that it is because I filed a support case asking for TLS 
configuration, with a reference to this conversation, that someone checked 
the answer that was given by Google here, and modified it.  Of course it is 
best to have correct answers in this conversation, and to remove incorrect 
answers.   But you have to understand that the incorrect answer given to me 
here cost me over 100$ in support subscription, with no result, since our 
GAE based application will not be made compliant with security test suites.

This erroneous answer and its consequences aside, *I think the question of 
TLS 1.0 and 1.1 should be answered by GCP* and should not require neither a 
support ticket nor a CLB subscription because it is not a whimsical desire, 
it is a general and major problem, affecting many if not all GAE 
applications, since *the use of these protocols that are deemed unsafe 
makes all applications fail compliance test suites*.  

I think GCP should make this setting readily available to all GAE 
applications.

In the meantime, I suppose I can now close my support subscription since it 
will not be of any use ?

On Tuesday, 31 August 2021 at 23:52:56 UTC+2 yananc wrote:

> Hi, 
> Although not the recommended option, creating a ticket with GCP tech 
> support is now an option only for GAE customers with previously existing 
> custom TLS configs.
>
> On Saturday, July 17, 2021 at 4:51:22 AM UTC-4 [email protected] 
> wrote:
>
>> Thank you for your reply @David.  May I ask if creating a ticket with GCP 
>> support, although not the recommended option, could still be one available 
>> option ?  
>> Because setting up  Cloud Load Balancing and serverless NEGS would be 
>> quite an endeavor, plus some added costs, while we don't actually have any 
>> need for these features at the moment, all we need is the deactivation of 
>> TLS 1.0 and 1.1.
>> Thanks
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9019ea43-bdeb-4045-b7f0-666a7c7769f6n%40googlegroups.com.

Reply via email to