Author: Daniel Stenberg (cross posted from daniel.haxx.se) Friends of mine know that I’ve tried for a long time to get confirmation that curl is used in space. We’ve believed it to be likely but I’ve wanted to get a clear confirmation that this is indeed the fact. Today GitHub posted their article about open source […]
Read MoreMore TagCategory: Uncategorized
wolfSentry vs Suricata
With our new release of wolfSentry people might wonder how it compares to Suricata. Suricata is an open source IDS / IPS / NSM engine. While it seems that Suricata is in rivalry with wolfSentry, our embedded IDPS; they actually have a synergy, it would make sense for sophisticated users to deploy both of them. […]
Read MoreMore TagSecure Boot and TLS 1.3 Firmware Update with FreeRTOS and wolfSSL on NXP “Freedom Board” K64
Secure boot and remote updates are becoming a mandatory requirement in the market of IoT connected and secured embedded systems. wolfSSL offers multiple solutions to update your remote embedded systems connected to the Internet. The core component that authenticates the firmware and regulates the installation of a new version is wolfBoot, the secure bootloader for […]
Read MoreMore TagstrongSwan + wolfSSL + FIPS!
As some may be aware, wolfSSL added support for strongSwan in April of 2019. The upstream commit can be reviewed here: https://github.com/strongswan/strongswan/pull/133 Users can test the latest development master of wolfSSL with the latest version of strongSwan using the following setup: wolfSSL Build and Installation Steps $ git clone https://github.com/wolfSSL/wolfssl.git $ cd wolfssl $ ./autogen.sh […]
Read MoreMore TagwolfSSL and MIKEY-SAKKE
wolfSSL is implementing MIKEY-SAKKE! MIKEY-SAKKE is a standard created by the UK government’s National Cyber Security Center (NCSC). MIKEY-SAKKE is a standard designed to enable secure, cross-platform multimedia communications. It is highly scalable, requiring no prior setup between users or distribution of user certificates. It is designed to be centrally-managed, giving a domain manager full […]
Read MoreMore TagFIPS certificate #2425 is being added to NIST sunset list: wolfSSL customers can achieve effortless transition to FIPS cert #3389
FIPS 140-2 requires the use of validated cryptography in the security systems implemented by federal agencies to protect sensitive information. The wolfCrypt Module is a comprehensive suite of FIPS Approved algorithms. All key sizes and modes have been implemented to allow flexibility and efficiency. The National Institute of Standards and Technology (NIST) is sending FIPS […]
Read MoreMore TagSecure wolfMQTT SN with wolfSSL DTLS
The sensor network sub-specification of MQTT does not designate a method for securing the communication between the clients and the gateway. We here at wolfSSL think that is unacceptable! Using the DTLS library of wolfSSL, we would like to protect the sensor data all the way from the client to the gateway, and then from […]
Read MoreMore TagMQTT Embeddable Broker
Stay tuned for an MQTT embeddable broker coming soon. We are going to be expanding our wolfMQTT library to include a lightweight, embeddable broker. The wolfMQTT embedded broker will allow for a low cost, low power, MQTT enabled network, all implemented in a C-based library. wolfMQTT secures MQTT communication using the wolfSSL embedded SSL/TLS library […]
Read MoreMore TagwolfSSL Support for DO-178 DAL A
wolfSSL is adding support for complete RTCA DO-178C level A certification! wolfSSL will offer DO-178 wolfCrypt as a commercial off -the-shelf (COTS) solution for connected avionics applications. Adherence to DO-178C level A will be supported through the first wolfCrypt COTS DO-178C certification kit release that includes traceable artifacts for the following encryption algorithms: SHA-256 for […]
Read MoreMore TagACVP and FIPS 140-3
As many in the FIPS world are aware NIST retired CAVP (Cryptographic Algorithm Validation Protocol) testing on June 30th of 2020, permanently replacing CAVP with ACVP (Automated Cryptographic Validation Protocol), also referred to as ACVTS (Automated Cryptographic Validation Test System). In order to prepare for this transition NIST offered a “demo server” that Vendors like […]
Read MoreMore Tag
