RECENT BLOG NEWS
Assembly-Based Performance Optimizations for ARM in wolfSSL
Earlier this week we stated our commitment to ARM by explaining our assembly code optimizations on a number of our math intensive cryptography operations. To give you more information, these optimizations are for Public Key operations with the CTaoCrypt fastmath option. This translates to a speed increase when using RSA, Diffie-Hellman, or DSA.
If you dive into our code, these optimizations can be found in the asm.c source file.
Today, Team yaSSL continues to exhibit at the ARM Technology Conference in Santa Clara, CA. If you are in the area, feel free to stop by our booth to visit or contact us at info@yassl.com with any questions.
The ARM Powered Corvette
The yaSSL booth at ARM TechCon is perfectly situated to check out the QNX based/ARM based Corvette on the show floor. It’s a silver beauty! See the pictures below.
Reminder: if you’re building a QNX based car computer and need to secure it with small embedded SSL solution, then contact us. One of the earliest wolfSSL users did just that, so we have some experience in the domain.
yaSSL lays plans to secure mbed based racing robots
Hi! As you may know from reading our posts here, Team yaSSL is exhibiting at ARM TechCon this week. What you may not know is that we’ve been working with ARM’s mbed.org team to facilitate a port of wolfSSL to mbed. Why? Because hobbyists need security too! And it is fun.
Here at ARM TechCon, mbed has paired with Pololu to create an mbed-based robot. Additionally, these two companies have created a contest for developers to race the robots based on the program they write. We’re going to help ensure a robot does not lose because its communication is subject to an MITM attack!
How to use the CTaoCrypt crypto library in standalone mode
Hi! About 20% of our users are using CTaoCrypt to provide standalone cryptographic functionality, and about 80% of our users have not thought about using it that way. The purpose of this blog post is to inform users on how to use CTaoCrypt as a standalone library:
1. CTaoCrypt is available as a function set within wolfSSL, licensed under GPL or commercially. If you are interested in using it outside of wolfSSL, then let us know. Basically this means that 100% of the CTaoCrypt functions are available through the wolfSSL API set.
2. Support for various development environments is included in the download, including GCC, Visual Studio, and Xcode.
3. The build process is described in the README. A program to test your build is included.
4. If you are a benchmark junkie, and since we know you probably are, we include a simple benchmark application to get you started.
5. CTaoCrypt has a lot of useful features, including:
– AES-NI support for super fast AES on the newer intel chips.
– One way hash functions: SHA-1, MD2, MD4, MD5, RIPEMD-160
– Message authentication codes: HMAC
– Block Ciphers: DES, Triple-DES, AES
– Stream Ciphers: ARC4, Rabbit and HC-128
– Public Key Crypto: RSA, DSA, Diffie-Hellman
– Password based key derivation: PBKDF2 from PKCS #5
– Pseudo Random Number Generators
– Large Integer Support
– Base 16/64 encoding/decoding
– DER encoding/decoding
– X.509 processing
– x86, x86_64, SSE2, ARM, PPC32, and PPC64 and AVR32
– Support for FastMath
6. If you need porting, support, or just regular help with CTaoCrypt, then get in contact with us at info@yassl.com.
SHODAN: Sentient Hyper-Optimized Data Access Network automates port scanning, simplifies exploiting embedded devices
“The Register” reported on using SHODAN to pinpoint embedded devices that are not properly secured yesterday. See http://www.theregister.co.uk/2010/11/02/scada_search_engine_warning/ for details. In summary, SHODAN can be used to quickly identify internet connected devices with known exploits. For us, it points to yet another reason why mobile and embedded systems developers should harden their devices with the wolfSSL embedded SSL library and the yaSSL Embedded Web Server.
OCSP, RFC 2560 for Embedded SSL
Hi! Do you need OCSP (Online Certificate Status Protocol) in wolfSSL? Let us know. We’re currently considering it for a feature addition to our next release. Sometimes OCSP may be necessary to obtain timely information about the revocation status of a certificate. OCSP solves that problem. Additional status information is also available under the protocol. More information on the protocol is available here: http://www.ietf.org/rfc/rfc2560.txt. This is not a big feature for us to add, but we’re weighing it against other development priorities. So let us know what you think! Send in your vote for or against OCSP being a high priority for wolfSSL to info@yassl.com.
yaSSL Embedded Web Server – CGI Support
The yaSSL Open Source Embedded Web Server has support for CGI (Common Gateway Interface). Using CGI, a web server can communicate with other types of programs running on the server. Because the yaSSL Embedded Web Server by itself is only able to deal with HTML file, it can “pass off” scripts written in other languages to their specific interpreter, thus allowing the functionality of many CGI languages to be used. Some of the possible languages include: PHP, Perl, ASP, ASP.NET, Python, Ruby on Rails, and C.
To configure the yaSSL Embedded Web Server to process CGI scripts in a given language, the interpreter for that language must be installed on the server. As an example, we’ll walk through how you would enable PHP to be used with the yaSSL Embedded Web Server.
The first thing you would need to do would be to download PHP if it is not currently installed on your server. The PHP source can be downloaded from the following location: http://www.php.net/downloads.php. After it has been downloaded, it should be built and installed. From the php source directory, run the following commands:
./configure
make
sudo make install
On OS X, this will place the “php-cgi” program in the “/usr/local/bin” directory. Now that we have the PHP CGI interpreter, we need to let the yaSSL Web Server know where it is located. This can be done in two ways (as most options can) and be set at runtime using the -cgi_interp option, or by adding a similar line to the configuration file. We can also set the -cgi_ext option, which defines which extensions are treated as CGI scripts. Setting these option at runtime, you would start the yaSSL Embedded Web Server as follows:
./yasslEWS -cgi_ext cgi,php -cgi_interp /usr/local/bin/php-cgi
After starting the web server, you can test if PHP is working by browsing to any PHP file which is located under your web server root directory.
To download the yaSSL Embedded Web Server, or to learn more, check out http://www.yassl.com. If you have any questions, contact us at info@yassl.com.
yaSSL Embedded Web Server – Alias Support
The yaSSL Open Source Embedded Web Server supports directory aliases. Similar to Apache’s mod_alias, using aliases allows a mapping to be created between URLs and file system paths. This mapping allows content which is not under the web server Document Root to be served as part of the web document tree. In other words, URLs beginning with the url-path will be mapped to local files beginning with the directory-path.
In the yaSSL Embedded Web Server, this can be done two ways:
1) Aliases can be set at runtime by using the -aliases option
2) Aliases can be set in the config file
In the following examples, suppose we wanted to map our local video directory (/home/user/Videos) to the URL “/videos”, and we wanted to map our pictures directory (/home/user/Pictures) to the URL “/pictures”.
Using the first option (setting the aliases at runtime), would look similar to the following.
./yasslEWS -aliases /videos=/home/user/Videos,/pictures=/home/user/Pictures
Using the second option (setting the aliases through the config file), we would need to add a line to our config file, as follows:
aliases /videos=/home/user/Videos,/pictures=/home/user/Pictures
To test if the newly set-up aliases are working correctly, point your web browser to one of the two URLs, where you should see a directory listing of the local files.
http://
http://
If this doesn’t work, double check that your paths are correct in your alias definitions and that everything is spelled correctly. Aliases should be able to be created for any drive physically attached to your computer.
To download the yaSSL Embedded Web Server, or to learn more, check out http://www.yassl.com. If you have any questions, contact us at info@yassl.com.
yaSSL Embedded Web Server – ACL Support
The yaSSL Open Source Embedded Web Server supports Access Control Lists. An Access Control List (ACL) allows restrictions to be put on the list of IP addresses which have access to the web server. In the case of the yaSSL Embedded Web Server, the ACL is a comma separated list of IP subnets, where each subnet is prepended by either a ‘-’ or a ‘+’ sign. A plus sign means allow, where a minus sign means deny. If a subnet mask is omitted, such as “-1.2.3.4”, this means to deny only that single IP address.
Subnet masks may vary from 0 to 32, inclusive. The default setting is to allow all, and on each request the full list is traversed – where the last match wins.
The ACL can be specified either at runtime, using the -acl option, or by using “acl” in the config file. For example, to allow only the 192.168.0.0/16 subnet to connect, you would run the following command:
./yasslEWS -acl -0.0.0.0/0,+192.168.0.0/16
The ACL can also be set in the web server config file. Using the example above, the config file line would be:
# acl -0.0.0.0/0,+192.168.0.0/16
To learn more about subnet masks, see the Wikipedia page on Subnetwork (http://en.wikipedia.org/wiki/Subnetwork), or here (http://wiki.xtronics.com/index.php/IP_Subnet_Masks).
To download the yaSSL Embedded Web Server, or to learn more, check out http://www.yassl.com. If you have any questions, contact us at info@yassl.com.
yaSSL Embedded Web Server – SSI Support
One of the features of the yaSSL Embedded Web Server is support for Server Side Includes. Server Side Includes (SSI) is a simple interpreted server-side scripting language which is most commonly used to include the contents of a file into a web page. It can be useful when it is desirable to include a common piece of code throughout a website.
Some of the ways in which Sever Side Includes may be used include:
– Including the contents of a file (html, txt, etc) into a web page
– Include the result of running a CGI script
– Executing a program, script, or shell command on the server
– Displaying the contents of a HTTP environment variable
– Outputting a list of variables and their values (environment and user-defined)
For more information on Server Side Includes, take a look at the Wikipedia entry here: http://en.wikipedia.org/wiki/Server_Side_Includes, or a tutorial on Server Side Includes can be found here: http://http-server.carleton.ca/~dmcfet/html/ssi.html.
To download the yaSSL Embedded Web Server, or to learn more, check out http://www.yassl.com. If you have any questions, contact us at info@yassl.com.
Weekly updates
Archives
- September 2024 (5)
- August 2024 (24)
- July 2024 (27)
- June 2024 (22)
- May 2024 (28)
- April 2024 (29)
- March 2024 (21)
- February 2024 (18)
- January 2024 (21)
- December 2023 (20)
- November 2023 (20)
- October 2023 (23)
- September 2023 (17)
- August 2023 (25)
- July 2023 (39)
- June 2023 (13)
- May 2023 (11)
- April 2023 (6)
- March 2023 (23)
- February 2023 (7)
- January 2023 (7)
- December 2022 (15)
- November 2022 (11)
- October 2022 (8)
- September 2022 (7)
- August 2022 (12)
- July 2022 (7)
- June 2022 (14)
- May 2022 (10)
- April 2022 (11)
- March 2022 (12)
- February 2022 (22)
- January 2022 (12)
- December 2021 (13)
- November 2021 (27)
- October 2021 (11)
- September 2021 (14)
- August 2021 (10)
- July 2021 (16)
- June 2021 (13)
- May 2021 (9)
- April 2021 (13)
- March 2021 (24)
- February 2021 (22)
- January 2021 (18)
- December 2020 (19)
- November 2020 (11)
- October 2020 (3)
- September 2020 (20)
- August 2020 (11)
- July 2020 (7)
- June 2020 (14)
- May 2020 (13)
- April 2020 (14)
- March 2020 (4)
- February 2020 (21)
- January 2020 (18)
- December 2019 (7)
- November 2019 (16)
- October 2019 (14)
- September 2019 (18)
- August 2019 (16)
- July 2019 (8)
- June 2019 (9)
- May 2019 (28)
- April 2019 (27)
- March 2019 (15)
- February 2019 (10)
- January 2019 (16)
- December 2018 (24)
- November 2018 (9)
- October 2018 (15)
- September 2018 (15)
- August 2018 (5)
- July 2018 (15)
- June 2018 (29)
- May 2018 (12)
- April 2018 (6)
- March 2018 (18)
- February 2018 (6)
- January 2018 (11)
- December 2017 (5)
- November 2017 (12)
- October 2017 (5)
- September 2017 (7)
- August 2017 (6)
- July 2017 (11)
- June 2017 (7)
- May 2017 (9)
- April 2017 (5)
- March 2017 (6)
- January 2017 (8)
- December 2016 (2)
- November 2016 (1)
- October 2016 (15)
- September 2016 (6)
- August 2016 (5)
- July 2016 (4)
- June 2016 (9)
- May 2016 (4)
- April 2016 (4)
- March 2016 (4)
- February 2016 (9)
- January 2016 (6)
- December 2015 (4)
- November 2015 (6)
- October 2015 (5)
- September 2015 (5)
- August 2015 (8)
- July 2015 (7)
- June 2015 (9)
- May 2015 (1)
- April 2015 (4)
- March 2015 (12)
- January 2015 (4)
- December 2014 (6)
- November 2014 (3)
- October 2014 (1)
- September 2014 (11)
- August 2014 (5)
- July 2014 (9)
- June 2014 (10)
- May 2014 (5)
- April 2014 (9)
- February 2014 (3)
- January 2014 (5)
- December 2013 (7)
- November 2013 (4)
- October 2013 (7)
- September 2013 (3)
- August 2013 (9)
- July 2013 (7)
- June 2013 (4)
- May 2013 (7)
- April 2013 (4)
- March 2013 (2)
- February 2013 (3)
- January 2013 (8)
- December 2012 (12)
- November 2012 (5)
- October 2012 (7)
- September 2012 (3)
- August 2012 (6)
- July 2012 (4)
- June 2012 (3)
- May 2012 (4)
- April 2012 (6)
- March 2012 (2)
- February 2012 (5)
- January 2012 (7)
- December 2011 (5)
- November 2011 (7)
- October 2011 (5)
- September 2011 (6)
- August 2011 (5)
- July 2011 (2)
- June 2011 (7)
- May 2011 (11)
- April 2011 (4)
- March 2011 (12)
- February 2011 (7)
- January 2011 (11)
- December 2010 (17)
- November 2010 (12)
- October 2010 (11)
- September 2010 (9)
- August 2010 (20)
- July 2010 (12)
- June 2010 (7)
- May 2010 (1)
- January 2010 (2)
- November 2009 (2)
- October 2009 (1)
- September 2009 (1)
- May 2009 (1)
- February 2009 (1)
- January 2009 (1)
- December 2008 (1)