# SSL \*slower\* ConnectME 9210 than NS7520?!

**URL:** <https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287>\
**Category:** NET+OS\
**Tags:** ssl\
**Created:** [January 27, 2011, 6:40pm UTC](https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287 "2011-01-27T18:40:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce.Lueckenhoff](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@Bruce.Lueckenhoff](https://forums.digi.com/u/Bruce.Lueckenhoff)\
**Post date:** [January 27, 2011, 6:40pm UTC](https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287/1 "2011-01-27T18:40:59Z")

</div>

I recently received a shiny new ConnectME 9210.

To provide a apples-to-apples comparison with my existing NS7520 that runs 7.3, I built the ConnectME 9210 firmware with 7.3 as well.

I’m running the same code on both.  
(serving a static web page over SSL)  
The trusty old NS7520 @ 55Mhz takes a little over 3 seconds.

The ConnectME 9210 takes a little over 6 seconds.  
(both times as measured by Firebug)  
This is repeatable behavior.

What gives?

- Is the AES acceleration HW is not enabled by the stock BSP?
- Does libcrypto.a just not use it?
- Or something else?

The same rev. of Net+OS (7.3) is running on both.

---

<div class="post-metadata">

**Author:** ![bobthomas13](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@bobthomas13](https://forums.digi.com/u/bobthomas13)\
**Post date:** [January 28, 2011, 7:50am UTC](https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287/2 "2011-01-28T07:50:26Z")

</div>

Digi Connect ME 9210 is not supported in NET+OS 7.3, only NET+OS 7.4 and later. try that

---

<div class="post-metadata">

**Author:** ![Bruce.Lueckenhoff](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@Bruce.Lueckenhoff](https://forums.digi.com/u/Bruce.Lueckenhoff)\
**Post date:** [January 28, 2011, 5:14pm UTC](https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287/3 "2011-01-28T17:14:49Z")

</div>

Using 7.5 (as provided by Digi along with the module ordered and delivered last week) I built the HTTPS sample program, and FTP’d the various .PEM and .CRL files it requires to get SSL happy.

Attempting to browse to the device using Firefox on a windoze XP PC fails to work at all!

Any advice?

---

<div class="post-metadata">

**Author:** ![Bruce.Lueckenhoff](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@Bruce.Lueckenhoff](https://forums.digi.com/u/Bruce.Lueckenhoff)\
**Post date:** [January 28, 2011, 7:55pm UTC](https://forums.digi.com/t/ssl-slower-connectme-9210-than-ns7520/4287/4 "2011-01-28T19:55:47Z")

</div>

okay, i need to modify root.c  
to specify

```auto
SSL_CERTIFICATE_VERIFY_NONE

```

in the call to

```auto
naSslSetCertVerify()

```

it does indeed seem much more sprightly, but I haven’t run a consistent test yet.

Why on earth would Digi ship the HTTPS demo program with a setting that is virtually guaranteed to fail to work with any common PC+browser?