Closed sdegiacomi closed 2 years ago
Hi @sdegiacomi, thank you for opening an issue! I'll tag the appropriate folks so we can look into this as soon as possible.
hey @sdegiacomi, I'm sorry to inform you that support for Windows 7 ended on January 14, 2020 and we have no plan for our SDKs to keep supporting Windows 7.
is there anything else we could help with or is there a reason what Windows 7 is wanted by you?
latest update:
Simone Degiacomi is from internal team and reached out to me via Teams.
for short term fix, Simone is able to patch the C code, compile and get the sdk work on Windows7. for long term fix, we will have the pure python-based service bus sdk which should get rid of the C certificate issue, and we will get Simone to be our early adopter to try the SDK out.
cc: @kashifkhan @lmazuel
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
Describe the bug Latest Python ServiceBus SDK fails to connect to ServiceBus when using Windows 7. The same exact code works on other platforms (Windows 10, ubuntu 16.10, Mac 10.13 and others). The following logs are printed by the SDK:
The SDK fails to connect both with TransportType
Amqp
andAmqpOverWebsocket
, and the SDK reports the same error.To Reproduce Run the following script on Windows 7:
Expected behavior Latest version of SDK should connect to ServiceBus using Windows 7 platform.
Additional context Interestingly, in the same machine:
ServiceBusAdministrationClient
works without any issue;After some debugging, I found this SO answer. Can the issue be related to fields
hExclusiveRoot
andhExclusiveTrustedPeople
in structCERT_CHAIN_ENGINE_CONFIG
, which are not specified in x509_schannel.c?