We tested the application for PCI Compliance and ended up with an error stating that
**SSL Medium Strength Cipher Suites Supported**
And the solution for this is given as
Reconfigure the affected application if possible to avoid use of medium strength ciphers
Can anyone help me how to implement in windows server 2003 using IIS 6.0
Go to the following location from registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\
You will see a list of cipher key size.
Add a new DWORD key name 'Enabled' with value '0' to the cipher key with the size less than '128'.
Hope this help.
Myo Zaw.
Related
Windows 11 Pro
Netbeans 12.3
Latest Simulator
Generation of IOS development certificate is producing an Error
Please see screen shot.
Also note some of the text is cut
off in the dialog message.
Thoughts?
Best Regards
2 Apple Developers Certificate Pics
Does anyone know whether Driver exe for New Microsoft Chromium Edge Available ?
If Yes, please share link.
Thanks.
Yes, it can be found here:
https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/#downloads
It's version 75 but I've been testing it out and it works fine with Edge 76. Make sure that you have the correct Edge executable on your path depending on whether you have Dev or Canary.
Dev:
C:\Program Files (x86)\Microsoft\Edge Dev\Application\
Canary:
C:\Users\boni\AppData\Local\Microsoft\Edge SxS\Application\
There's a bit more info on my other answer:
I wouldn't recommend testing Canary, as it's unstable and it changes so fast, maintaining results will not be fun. I'm testing Dev and I'll switch to Beta when that's released.
Just a point regarding Dmitri's answer about market shares:
While accurate, they are global figures, so may be entirely irrelevant to what you're testing. If for example you're developing web applications for businesses, it's not unusual to find that the vast majority of your users are on IE or Edge, because companies have policies about only using Microsoft browsers. Sometimes this is about perceived security, but more often than not, it's about supporting legacy systems and documents, which can only be viewed in IE or chromium Edge's IE mode.
I would not go for automation till official release of the EdgeChromium-based browser from Microsoft, moreover looking into current browser market share I don't think you should be investing any efforts into it.
Chrome 61.75%
Safari 15.12%
Firefox 4.92%
UC Browser 4.22%
Opera 3.15%
IE 2.8%
Edge 2.15%
Others 5.89%
Just in case if you still want to assess the EdgeChromium automation the driver is available since 24th of April 2019 at normal Edge Driver downloads page
For example direct link for MS Edge 75 driver:
https://msedgecdn.azurewebsites.net/webdriver/index.html
I'm trying to run the azure iothub sdk c sample of the mqtt protocol.
I've compiled hte project but when I run the program it returns some error about SSL routines
This i the complete error:
error:1416F086: SSL routines:tls_process_server_certificate:certificate verify failed
Info: Closing tlsio from a state other than TLSIO_STATE_EXT_OPEN or TLSIO_STATE_EXT_ERROR
I got only this error repeated five times, one for each accepted message ready to be transmitted to the IoTHub.
I've read that I need to set trust to the openssl certs in the sample directory but I've not figured out how to do this task or how to avoid this problem.
Is there someone who has already faced this issue?
This document describes in detail how to prepare your development environment as well as how to run the samples on Linux, Windows or other platforms. Please refer to the section to rebuild you code and then run to test.
Try using the TrustedCerts option. With this option you can pass to the SDK the certificate that is used to validate the server's certificate. This is typically used when either you don't have the root certificate, Baltimore CyberTrust, or your device does not have the concept of a trusted root certificate store. You can find an example of this option being used in
<repositoryRoot>\iothub_client\samples\iothub_client_sample_amqp_shared\iothub_client_sample_amqp_shared.c
https://github.com/Azure/azure-iot-sdk-c/blob/44827986929af7f4fbb41806b880a6da4e13d3e8/iothub_client/samples/iothub_client_sample_amqp_shared/iothub_client_sample_amqp_shared.c#L261
I am developing a kernel-mode driver and I 'd like it to be able to run on all Windows platforms (including Windows 10). I have read the driver signing policy in Win10 from http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx. I don't know if I am understanding it right, does it mean that if I buy a non-EV cert before Win10 release (AKA 2015/7/29), I can still use the cert to sign a driver to any platform including Win10 until the cert expires. For example, I can just buy a 3-year long cert before 7/29 and use it to sign any drivers for these 3 years (the longest period for a cert seems to be 3 years). 3 years later, I have no other choice but to buy an EV cert, is this understanding right? Thanks.
You're basically asking if you can slip a driver that wasn't signed with Extended Validation ("EV") certificate through the door before Windows 10 release.
The salient point is this:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx
Beginning with the release of Windows 10, all new Windows 10 kernel
mode drivers must be submitted to and digitally signed by the Windows
Hardware Developer Center Dashboard portal. Windows 10 will not load
new kernel mode drivers which are not signed by the portal.
My guess is "maybe".
But you'd better hurry.
And you'd better have a Plan B if your Windows 10 customers discover that your driver won't work.
How do I determine the Remote Desktop Protocol version supported by a particular client?
Note that I am NOT asking for the ActiveX control version but the underlying protocol version. As examples from two machines I checked using Help->About (or just About in the case of Windows XP):
On Windows 8, I do NOT want 6.2.9200, I want 8.0.
On Windows XP, I do NOT want 6.0.6001, I want 6.1.
And I am not asking for the protocol version in use in a given session (which is what Determine Remote Desktop Protocol version programatically? is referring to) because we're not in a session, we are validating a client's configuration.
Thanks!
I eventually contact Microsoft about this question and the (somewhat amazing) answer I got back is as follows:
That string is hard-coded and not retrieved from the server or AX (in
fact mstsc.exe checks the build number of mstsax.dll before loading it
to make sure it is consistent with its own build number).
So I guess I will need to fall back on hard-coded OS version information - perhaps the mstsc.exe version. That's yucky but I don't see what choice I have.