-
Notifications
You must be signed in to change notification settings - Fork 128
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
TLS 1.2 support advertised but no SHA-384/SHA-512 capability #48
Comments
Cheers guys, let me know if you want any help testing the fix. |
I received the following request from Atmel Support, so could "cmagile" please provide the incident numbers he referred to, so we can try to escalate this issue: "Please respond above this email, avoid inline comments Commented by Anu Ramakrishnan (Atmel) 2016-03-28 23:56 PDT Hi Michael, I am following up on this internally. We will get back to you as soon as we have further information. Regards From #4730: |
Hi @mashikawa, We've heard back from Atmel on this. SHA-384 certificate support is scheduled to be added in the June 2016 firmware release. Also, as of now, there are no plans to support SHA-512. |
Hi, |
Hi @hiteule, I've contact Atmel support about this, unfortunately the June release is now pushed out to September. cc/ @ThibaultRichard |
In any case, if this issue succeed, please remember to update the line "Support TLS 1.1 (SHA256)" from https://www.arduino.cc/en/Main/ArduinoWiFiShield101 , please. |
Any updates? |
@erhanalankus unfortunately nothing to report yet. See: #90 (comment):
|
Hey, any news from Atmel about the firmware update ? |
postponed to January 2017 |
Someone have some news about de release date ? |
still remains the date of January. |
Any news with this problem? It is urgent. Thx |
I gave up waiting for this a long time ago; this was a simple fix, so it appears that Atmel are not supporting this device. About six months when I realised this was not going to be fixed, I switched to ESP8266 board and added my own SHA-256 hashing to the IOT data uploads as a workaround. Sounds like the new ESP-32 chip is worth checking out for secure uploads.
Regards,
Michael
… On Feb 13, 29 Heisei, at 11:09 PM, eliavgnessin ***@***.***> wrote:
Any news with this problem? It is urgent. Thx
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
FW 19.5.2 is finally out of the beta, you can check the integration status here : #148 |
Closing as #148 is now merged. The 19.5.2 firmware is only available for model B of the WINC1500, this is used in the MKR1000 board. Unfortunately, the WiFi101 shield uses model A, which Atmel has stopped supporting, so there is no 19.5.2 firmware release for it, 19.4.4 will be the latest firmware version that is compatible. |
There's a PR build that contains the new firmware updater and the IDE available here for testing: arduino/Arduino#6069 (comment). |
Moved from arduino/Arduino#4730
@mashikawa wrote:
Hi, I purchased the Arduino Wifi 101 shield for an IoT project and found that I could not connect to certain servers via SSL. Some worked (www.google.com:443) and others did not (plot.ly:443).
Using Wireshark to monitor the TLS handshake I found that the WINC1500 hardcodes the TLS Client Hello value to 1.2 ( since firmware version 9.3.0 ), although the device does not handle ciphers longer than 256bits ( SHA-256 ). This actually makes it only TLS1.1 compatible. Some servers now implement SHA-384 and SHA-512 ciphers as part of the TLS1.2 protocol and they can respond to the TLS1.2 request with these ciphers, which the WINC1500 (Wifi101) cannot decrypt and so the connection fails. I have recreated the issue using OpenSSL and have attached the output to this request for info.
I raised a support request with Atmel ( Case 00037229 ), suggesting they allow the TLS value to be modified by the user via the software and they responded with the following message:
Created By: Anu Ramakrishnan (3/21/2016 4:09 AM)
[Recipients: Michael Kelsall]
Hi Micheal,
Yes, we do not support SHA-384 and 512. Thank you for the feedback regarding the usage of TLS1.2 mode. We have raised a bug internally for this and we will follow up to get it fixed in future releases.
We do not share firmware sources of the ATWINC1500, sorry for the inconvenience.
Regards,
Anu
This is a good response but I am now worried the issue may sit on a development list with low priority for an extended period of time..... Can anyone help to progress this as I am sure the problem will get worse as more website implement longer ciphers to improve security.
Regards,
Michael.
OpenSSL_ATWINC1500_TLS_Examples.txt
The text was updated successfully, but these errors were encountered: