yaSSL made dramatic progress this year on a number of fronts, notably in open source community usage, embedded systems adoption, and technology improvements! Here’s what we’ve done this year, with an outline of our plans for the year to come in a blog post to follow: 1. Participated in 4 industry events, including OSCON, Embedded Live, […]
Read MoreMore TagCategory: Uncategorized
wolfSSL and TomatoUSB
Hi! The TomatoUSB community has integrated wolfSSL into the TomatoUSB Firmware as of release 53. wolfSSL is being used in non-VPN editions of the firmware to provide SSL support for httdp and dyndns. They have upgraded to TLS 1.0 from SSL v 2/3 which was previously being used. TomatoUSB is an alternative linux-based firmware for […]
Read MoreMore TagyaSSL Annual Report
yaSSL made dramatic progress this year on a number of fronts, notably in open source community usage, embedded systems adoption, and technology improvements! Here’s what we’ve done this year, with an outline of our plans for the year to come in a blog post to follow: 1. Participated in 4 industry events, including OSCON, Embedded […]
Read MoreMore TagInitial Results of wolfSSL on mbed
Recently we’ve been working on porting wolfSSL over to mbed (http://mbed.org/). Now that we have things working, we can report some initial results. wolfSSL takes 2.9 kB of RAM (10% of total) and 63 kB of Flash (13%). That includes our test driver code which is about 3 kB. On our test machine, we ran […]
Read MoreMore TagStatistics and Projections on Connected Consumer Devices
The average consumer in the US will “own 5-10 web-enabled devices by 2014” according to In-Stat. See here for details: http://www.embeddedinternetdesign.com/showArticle.jhtml?articleID=228300296 (as of 26 March 2018 at 9:20am MDT, this link is broken and has no alternative). By our reckoning, that means about 200 Million devices that need to be enabled with embedded SSL to […]
Read MoreMore TagA great article that can act as a primer on extracting data from embedded systems, as well as give some ideas on securing them in the first place.
From the article: “During a forensic autopsy an artificial pacemaker was secured for forensic information analysis. An academic hospital was contacted and they had equipment to read the data from this pacemaker via a wireless interface. The extracted information contained around 10 pages of details like name and date of birth of the patient, timestamps […]
Read MoreMore TagInitial results in porting wolfSSL to the mbed MCU
As previously stated here, wolfSSL is getting ported to the mbed chip. We’ve done the initial build and the results were pretty good. wolfSSL takes 2.9 kB of RAM (10% of total) and 63 kB of Flash (13%). That includes the test driver code which is about 3 kB. More information to follow! If you’re […]
Read MoreMore TagTLS extension parsing race condition issue affects only OpenSSL, not wolfSSL
Hi! If you’re wondering, as some are, whether there is any issues with wolfSSL for CVE-2010-3864, the TLS extension parsing race condition, then please note that this issue only affects OpenSSL, not wolfSSL. CVE-2010-3864 is an issue specific to OpenSSL, which is an entirely different SSL library than wolfSSL. This issue is not general to […]
Read MoreMore TagEmbedded Web Server for AVR
The yaSSL Embedded Web Server for AVR has some optimizations our users might want to hear about: Assembly code for the AVR and AVR 32 instruction sets in the SSL cryptography. Assembly code for the AVR 32 instruction set speeds up public key operation during the SSL handshake. Need to use it? Already using it? […]
Read MoreMore TagWhat’s the difference between wolfSSL Embedded SSL and OpenSSL?
Hi! If you came to our site because you are considering wolfSSL as an alternative to OpenSSL, this blog post is your cheat sheet that details the differences between the two products: 1. Size: With a 30-40k build size, wolfSSL is 20 times smaller than OpenSSL. wolfSSL is a better choice for resource constrained environments.2. Standards […]
Read MoreMore Tag