wolfssl-3.10.2-stable/000077500000000000000000000000001305024512300145315ustar00rootroot00000000000000wolfssl-3.10.2-stable/.cproject000066400000000000000000000621151305024512300163500ustar00rootroot00000000000000 <?xml version="1.0" encoding="UTF-8"?> <TargetConfig> <Properties property_0="" property_2="LPC18x7_43x7_2x512_BootA.cfx" property_3="NXP" property_4="LPC18S37" property_count="5" version="70200"/> <infoList vendor="NXP"><info chip="LPC18S37" flash_driver="LPC18x7_43x7_2x512_BootA.cfx" match_id="0x0" name="LPC18S37" resetscript="LPC18LPC43InternalFLASHBootResetscript.scp" stub="crt_emu_lpc18_43_nxp"><chip><name>LPC18S37</name> <family>LPC18xx</family> <vendor>NXP (formerly Philips)</vendor> <reset board="None" core="Real" sys="Real"/> <clock changeable="TRUE" freq="20MHz" is_accurate="TRUE"/> <memory can_program="true" id="Flash" is_ro="true" type="Flash"/> <memory id="RAM" type="RAM"/> <memory id="Periph" is_volatile="true" type="Peripheral"/> <memoryInstance derived_from="Flash" id="MFlashA512" location="0x1a000000" size="0x80000"/> <memoryInstance derived_from="Flash" id="MFlashB512" location="0x1b000000" size="0x80000"/> <memoryInstance derived_from="RAM" id="RamLoc32" location="0x10000000" size="0x8000"/> <memoryInstance derived_from="RAM" id="RamLoc40" location="0x10080000" size="0xa000"/> <memoryInstance derived_from="RAM" id="RamAHB32" location="0x20000000" size="0x8000"/> <memoryInstance derived_from="RAM" id="RamAHB16" location="0x20008000" size="0x4000"/> <memoryInstance derived_from="RAM" id="RamAHB_ETB16" location="0x2000c000" size="0x4000"/> <prog_flash blocksz="0x2000" location="0x1a000000" maxprgbuff="0x400" progwithcode="TRUE" size="0x10000"/> <prog_flash blocksz="0x10000" location="0x1a010000" maxprgbuff="0x400" progwithcode="TRUE" size="0x70000"/> <prog_flash blocksz="0x2000" location="0x1b000000" maxprgbuff="0x400" progwithcode="TRUE" size="0x10000"/> <prog_flash blocksz="0x10000" location="0x1b010000" maxprgbuff="0x400" progwithcode="TRUE" size="0x70000"/> <peripheralInstance derived_from="V7M_MPU" id="MPU" location="0xe000ed90"/> <peripheralInstance derived_from="V7M_NVIC" id="NVIC" location="0xe000e000"/> <peripheralInstance derived_from="V7M_DCR" id="DCR" location="0xe000edf0"/> <peripheralInstance derived_from="V7M_ITM" id="ITM" location="0xe0000000"/> <peripheralInstance derived_from="SCT" id="SCT" location="0x40000000"/> <peripheralInstance derived_from="GPDMA" id="GPDMA" location="0x40002000"/> <peripheralInstance derived_from="SPIFI" id="SPIFI" location="0x40003000"/> <peripheralInstance derived_from="SDMMC" id="SDMMC" location="0x40004000"/> <peripheralInstance derived_from="EMC" id="EMC" location="0x40005000"/> <peripheralInstance derived_from="USB0" id="USB0" location="0x40006000"/> <peripheralInstance derived_from="USB1" id="USB1" location="0x40007000"/> <peripheralInstance derived_from="EEPROM" id="EEPROM" location="0x4000e000"/> <peripheralInstance derived_from="ETHERNET" id="ETHERNET" location="0x40010000"/> <peripheralInstance derived_from="ATIMER" id="ATIMER" location="0x40040000"/> <peripheralInstance derived_from="REGFILE" id="REGFILE" location="0x40041000"/> <peripheralInstance derived_from="PMC" id="PMC" location="0x40042000"/> <peripheralInstance derived_from="CREG" id="CREG" location="0x40043000"/> <peripheralInstance derived_from="EVENTROUTER" id="EVENTROUTER" location="0x40044000"/> <peripheralInstance derived_from="RTC" id="RTC" location="0x40046000"/> <peripheralInstance derived_from="CGU" id="CGU" location="0x40050000"/> <peripheralInstance derived_from="CCU1" id="CCU1" location="0x40051000"/> <peripheralInstance derived_from="CCU2" id="CCU2" location="0x40052000"/> <peripheralInstance derived_from="RGU" id="RGU" location="0x40053000"/> <peripheralInstance derived_from="WWDT" id="WWDT" location="0x40080000"/> <peripheralInstance derived_from="USART0" id="USART0" location="0x40081000"/> <peripheralInstance derived_from="USART2" id="USART2" location="0x400c1000"/> <peripheralInstance derived_from="USART3" id="USART3" location="0x400c2000"/> <peripheralInstance derived_from="UART1" id="UART1" location="0x40082000"/> <peripheralInstance derived_from="SSP0" id="SSP0" location="0x40083000"/> <peripheralInstance derived_from="SSP1" id="SSP1" location="0x400c5000"/> <peripheralInstance derived_from="TIMER0" id="TIMER0" location="0x40084000"/> <peripheralInstance derived_from="TIMER1" id="TIMER1" location="0x40085000"/> <peripheralInstance derived_from="TIMER2" id="TIMER2" location="0x400c3000"/> <peripheralInstance derived_from="TIMER3" id="TIMER3" location="0x400c4000"/> <peripheralInstance derived_from="SCU" id="SCU" location="0x40086000"/> <peripheralInstance derived_from="GPIO-PIN-INT" id="GPIO-PIN-INT" location="0x40087000"/> <peripheralInstance derived_from="GPIO-GROUP-INT0" id="GPIO-GROUP-INT0" location="0x40088000"/> <peripheralInstance derived_from="GPIO-GROUP-INT1" id="GPIO-GROUP-INT1" location="0x40089000"/> <peripheralInstance derived_from="MCPWM" id="MCPWM" location="0x400a0000"/> <peripheralInstance derived_from="I2C0" id="I2C0" location="0x400a1000"/> <peripheralInstance derived_from="I2C1" id="I2C1" location="0x400e0000"/> <peripheralInstance derived_from="I2S0" id="I2S0" location="0x400a2000"/> <peripheralInstance derived_from="I2S1" id="I2S1" location="0x400a3000"/> <peripheralInstance derived_from="C-CAN1" id="C-CAN1" location="0x400a4000"/> <peripheralInstance derived_from="RITIMER" id="RITIMER" location="0x400c0000"/> <peripheralInstance derived_from="QEI" id="QEI" location="0x400c6000"/> <peripheralInstance derived_from="GIMA" id="GIMA" location="0x400c7000"/> <peripheralInstance derived_from="DAC" id="DAC" location="0x400e1000"/> <peripheralInstance derived_from="C-CAN0" id="C-CAN0" location="0x400e2000"/> <peripheralInstance derived_from="ADC0" id="ADC0" location="0x400e3000"/> <peripheralInstance derived_from="ADC1" id="ADC1" location="0x400e4000"/> <peripheralInstance derived_from="GPIO-PORT" id="GPIO-PORT" location="0x400f4000"/> </chip> <processor><name gcc_name="cortex-m3">Cortex-M3</name> <family>Cortex-M</family> </processor> <link href="nxp_lpc18xx_peripheral.xme" show="embed" type="simple"/> </info> </infoList> </TargetConfig> wolfssl-3.10.2-stable/.gitignore000066400000000000000000000072621305024512300165300ustar00rootroot00000000000000ctaocrypt/src/src/ *.swp *.lo *.la *.o *.patch *.deps *.libs *.cache .dirstamp *.user config* *Debug/ *Release/ *.ncb *.suo *.sdf *.opensdf ipch/ build-aux/ rpm/spec *.rpm stamp-h cyassl/options.h wolfssl/options.h libtool.m4 aclocal.m4 aminclude.am lt*.m4 Makefile.in Makefile depcomp missing libtool tags .tags* cyassl-config wolfssl-config cyassl.sublime* fips.c fips_test.c fips src/async.c wolfssl/async.h wolfcrypt/src/async.c wolfssl/wolfcrypt/async.h ctaocrypt/benchmark/benchmark ctaocrypt/test/testctaocrypt wolfcrypt/benchmark/benchmark wolfcrypt/test/testwolfcrypt examples/client/client examples/echoclient/echoclient examples/echoserver/echoserver examples/server/server examples/sctp/sctp-server examples/sctp/sctp-server-dtls examples/sctp/sctp-client examples/sctp/sctp-client-dtls server_ready snifftest output mcapi/test testsuite/testsuite tests/unit testsuite/testsuite.test tests/unit.test tests/bio_write_test.txt testsuite/*.der testsuite/*.pem testsuite/*.raw cert.der cert.pem certecc.der certecc.pem othercert.der othercert.pem ntru-cert.der ntru-cert.pem ntru-key.raw key.der key.pem ecc-public-key.der ecc-key.der ecc-key.pem certreq.der certreq.pem pkcs7cert.der pkcs7signedData.der pkcs7envelopedDataDES3.der pkcs7envelopedDataAES128CBC.der pkcs7envelopedDataAES192CBC.der pkcs7envelopedDataAES256CBC.der diff sslSniffer/sslSnifferTest/tracefile.txt tracefile.txt *.gz *.zip *.bak *.dummy *.xcworkspace xcuserdata compile NTRU_algorithm/ NTRU/ build-test/ build/ cyassl.xcodeproj/ cyassl*rc* autoscan.log TAGS .DS_Store support/cyassl.pc cyassl/ctaocrypt/stamp-h1 swig/_cyassl.so swig/_wolfssl.so swig/cyassl.py swig/wolfssl.py swig/cyassl.pyc swig/wolfssl.pyc swig/cyassl_wrap.c swig/wolfssl_wrap.c stamp-h1 clang_output_* internal.plist cov-int cyassl.tgz *.log *.trs IDE/MDK-ARM/Projects/ IDE/MDK-ARM/STM32F2xx_StdPeriph_Lib/inc IDE/MDK-ARM/STM32F2xx_StdPeriph_Lib/src IDE/MDK-ARM/LPC43xx/Drivers/ IDE/MDK-ARM/LPC43xx/LPC43xx/ *.gcno *.gcda *.gcov # MPLAB Generated Files (OS X) mcapi/wolfcrypt_mcapi.X/nbproject/Makefile-* mcapi/wolfcrypt_mcapi.X/nbproject/Package-default.bash mcapi/wolfcrypt_test.X/nbproject/Makefile-* mcapi/wolfcrypt_test.X/nbproject/Package-default.bash mcapi/wolfssl.X/nbproject/Makefile-* mcapi/wolfssl.X/nbproject/Package-default.bash mcapi/zlib.X/nbproject/Makefile-* mcapi/zlib.X/nbproject/Package-default.bash mplabx/wolfcrypt_benchmark.X/nbproject/Makefile-* mplabx/wolfcrypt_benchmark.X/nbproject/Package-default.bash mplabx/wolfcrypt_test.X/nbproject/Makefile-* mplabx/wolfcrypt_test.X/nbproject/Package-default.bash mplabx/wolfssl.X/nbproject/Makefile-* mplabx/wolfssl.X/nbproject/Package-default.bash *.dSYM # Vagrant folder .vagrant/ # CodeWarrior Generated Files (Windows) mqx/cyassl/.settings mqx/cyassl_client/.settings mqx/cyassl_client/.cwGeneratedFileSetLog mqx/cyassl_client/SaAnalysispointsManager.apconfig mqx/util_lib/.settings mqx/wolfcrypt_test/.settings mqx/wolfcrypt_test/.cwGeneratedFileSetLog mqx/wolfcrypt_test/SaAnalysispointsManager.apconfig mqx/wolfcrypt_benchmark/.settings mqx/wolfcrypt_benchmark/.cwGeneratedFileSetLog mqx/wolfcrypt_benchmark/SaAnalysispointsManager.apconfig # User Crypto example build wolfcrypt/user-crypto/aclocal.m4 wolfcrypt/user-crypto/config.guess wolfcrypt/user-crypto/autom4te.cache wolfcrypt/user-crypto/config.log wolfcrypt/user-crypto/config.status wolfcrypt/user-crypto/config.sub wolfcrypt/user-crypto/depcomp wolfcrypt/user-crypto/install-sh wolfcrypt/user-crypto/libtool wolfcrypt/user-crypto/ltmain.sh wolfcrypt/user-crypto/m4 wolfcrypt/user-crypto/missing wolfcrypt/user-crypto/Makefile.in wolfcrypt/user-crypto/lib/libusercrypto.* *.hzs # wolfSSL CSharp wrapper wrapper/CSharp/x64/ # Visual Studio Code Workspace Files *.vscode wolfssl-3.10.2-stable/.project000066400000000000000000000015151305024512300162020ustar00rootroot00000000000000 wolfssl lpc_board_nxp_lpcxpresso_1837 lpc_chip_18xx org.eclipse.cdt.managedbuilder.core.genmakebuilder clean,full,incremental, org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder full,incremental, org.eclipse.cdt.core.cnature org.eclipse.cdt.managedbuilder.core.managedBuildNature org.eclipse.cdt.managedbuilder.core.ScannerConfigNature wolfssl-3.10.2-stable/AUTHORS000066400000000000000000000000001305024512300155670ustar00rootroot00000000000000wolfssl-3.10.2-stable/COPYING000066400000000000000000000432541305024512300155740ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. wolfssl-3.10.2-stable/ChangeLog000066400000000000000000000000601305024512300162770ustar00rootroot00000000000000Please see the file 'README' in this directory. wolfssl-3.10.2-stable/INSTALL000066400000000000000000000027221305024512300155650ustar00rootroot000000000000000. Building on *nix from git repository Run the autogen script to generate configure, then proceed to step 1. Prerequisites: You'll need autoconf, automake and libtool installed. $ ./autogen.sh 1. Building on *nix from a release $ ./configure $ make $ make check # (optional, but highly recommended) $ sudo make install 2. Building on iOS Use on the xcode project in IDE/iOS/wolfssl.xcodeproj There is a README in IDE/iOS with more information 3. Building on Windows Use the 32bit Visual Studio Solution wolfssl.sln For a 64bit solution please use wolfssl64.sln 4. Building with IAR Please see the README in IDE/IAR-EWARM for detailed instructions 5. Building with Keil Please see the Keil Projects in IDE/MDK5-ARM/Projects 6. Building with Microchip tools Please see the README in mplabx 7. Building with Freescale MQX Please see the README in mqx 8. Building with Rowley CrossWorks for ARM Use the CrossWorks project in IDE/ROWLEY-CROSSWORKS-ARM/wolfssl.hzp There is a README.md in IDE/ROWLEY-CROSSWORKS-ARM with more information 9. Building with Arduino Use the script IDE/ARDUINO/wolfssl-arduino.sh to reformat the wolfSSL library for compatibility with the Arduino IDE. There is a README.md in IDE/ARDUINO for detailed instructions. 10. Porting to a new platform Please see section 2.4 in the manual: http://www.wolfssl.com/yaSSL/Docs-cyassl-manual-2-building-cyassl.html wolfssl-3.10.2-stable/IPP/000077500000000000000000000000001305024512300151615ustar00rootroot00000000000000wolfssl-3.10.2-stable/IPP/.gitkeep000066400000000000000000000000001305024512300166000ustar00rootroot00000000000000wolfssl-3.10.2-stable/LICENSING000066400000000000000000000006271305024512300157740ustar00rootroot00000000000000 wolfSSL (formerly known as CyaSSL) and wolfCrypt are either licensed for use under the GPLv2 or a standard commercial license. For our users who cannot use wolfSSL under GPLv2, a commercial license to wolfSSL and wolfCrypt is available. Please contact wolfSSL Inc. directly at: Email: licensing@wolfssl.com Phone: +1 425 245-8247 More information can be found on the wolfSSL website at www.wolfssl.com. wolfssl-3.10.2-stable/Makefile.am000066400000000000000000000123501305024512300165660ustar00rootroot00000000000000# includes append to these: SUFFIXES = TESTS = CLEANFILES = DISTCLEANFILES = bin_PROGRAMS = noinst_HEADERS = lib_LTLIBRARIES = man_MANS = noinst_LTLIBRARIES = noinst_PROGRAMS = include_HEADERS = nobase_include_HEADERS = check_PROGRAMS = EXTRA_HEADERS = BUILT_SOURCES= EXTRA_DIST= dist_doc_DATA= dist_noinst_SCRIPTS = noinst_SCRIPTS = check_SCRIPTS = #includes additional rules from aminclude.am @INC_AMINCLUDE@ DISTCLEANFILES+= aminclude.am CLEANFILES+= cert.der \ cert.pem \ certecc.der \ certecc.pem \ certreq.der \ certreq.pem \ key.der \ key.pem \ ntru-cert.der \ ntru-cert.pem \ ntru-key.raw \ othercert.der \ othercert.pem \ pkcs7cert.der \ pkcs7encryptedDataAES128CBC.der \ pkcs7encryptedDataAES192CBC.der \ pkcs7encryptedDataAES256CBC_attribs.der \ pkcs7encryptedDataAES256CBC.der \ pkcs7encryptedDataAES256CBC_multi_attribs.der \ pkcs7encryptedDataDES3.der \ pkcs7encryptedDataDES.der \ pkcs7envelopedDataAES256CBC_ECDH.der \ pkcs7envelopedDataAES128CBC_ECDH_SHA1KDF.der \ pkcs7envelopedDataAES256CBC_ECDH_SHA256KDF.der \ pkcs7envelopedDataAES256CBC_ECDH_SHA512KDF.der \ pkcs7envelopedDataAES256CBC_ECDH_SHA512KDF_ukm.der \ pkcs7envelopedDataDES3.der \ pkcs7envelopedDataAES128CBC.der \ pkcs7envelopedDataAES192CBC.der \ pkcs7envelopedDataAES256CBC.der \ pkcs7signedData.der exampledir = $(docdir)/example dist_example_DATA= ACLOCAL_AMFLAGS= -I m4 EXTRA_DIST+= lib/dummy EXTRA_DIST+= wolfssl-ntru.vcproj EXTRA_DIST+= wolfssl.vcproj EXTRA_DIST+= wolfssl.vcxproj EXTRA_DIST+= wolfssl-ntru.sln EXTRA_DIST+= wolfssl.sln EXTRA_DIST+= wolfssl64.sln EXTRA_DIST+= valgrind-error.sh EXTRA_DIST+= gencertbuf.pl EXTRA_DIST+= README.md EXTRA_DIST+= LICENSING EXTRA_DIST+= INSTALL EXTRA_DIST+= IPP EXTRA_DIST+= .cproject EXTRA_DIST+= .project include wrapper/include.am include cyassl/include.am include wolfssl/include.am include certs/include.am include certs/1024/include.am include certs/crl/include.am include certs/external/include.am include certs/ocsp/include.am include doc/include.am include swig/include.am include src/include.am include support/include.am include wolfcrypt/user-crypto/include.am include wolfcrypt/benchmark/include.am include wolfcrypt/src/include.am include wolfcrypt/test/include.am include examples/include.am include testsuite/include.am include tests/include.am include sslSniffer/sslSnifferTest/include.am include rpm/include.am # Exclude references to non-DFSG sources from build files if !BUILD_DISTRO include mqx/util_lib/Sources/include.am include mqx/wolfcrypt_benchmark/Sources/include.am include mqx/wolfcrypt_test/Sources/include.am include mqx/wolfssl/include.am include mqx/wolfssl_client/Sources/include.am include mplabx/include.am include mplabx/wolfcrypt_benchmark.X/nbproject/include.am include mplabx/wolfcrypt_test.X/nbproject/include.am include mplabx/wolfssl.X/nbproject/include.am include mcapi/include.am include mcapi/wolfcrypt_mcapi.X/nbproject/include.am include mcapi/wolfcrypt_test.X/nbproject/include.am include mcapi/wolfssl.X/nbproject/include.am include mcapi/zlib.X/nbproject/include.am include tirtos/include.am include IDE/include.am endif include scripts/include.am if USE_VALGRIND TESTS_ENVIRONMENT=./valgrind-error.sh endif TEST_EXTENSIONS=.test TESTS += $(check_PROGRAMS) check_SCRIPTS+= $(dist_noinst_SCRIPTS) TESTS += $(check_SCRIPTS) test: check tests/unit.log: testsuite/testsuite.log DISTCLEANFILES+= cyassl-config DISTCLEANFILES+= wolfssl-config maintainer-clean-local: -rm Makefile.in -rm aclocal.m4 -rm build-aux/compile -rm build-aux/config.guess -rm build-aux/config.sub -rm build-aux/depcomp -rm build-aux/install-sh -rm build-aux/ltmain.sh -rm build-aux/missing -rm cyassl-config -rmdir build-aux -rm configure -rm config.log -rm config.status -rm config.in -rm m4/libtool.m4 -rm m4/ltoptions.m4 -rm m4/ltsugar.m4 -rm m4/ltversion.m4 -rm m4/lt~obsolete.m4 -rm support/wolfssl.pc find . -type f -name '*~' -exec rm -f '{}' \; -rm -f @PACKAGE@-*.tar.gz -rm -f @PACKAGE@-*.rpm # !!!! first line of rule has to start with a hard (real) tab, not spaces egs: $(MAKE) examples/client/client; \ $(MAKE) examples/echoclient/echoclient;\ $(MAKE) examples/server/server; \ $(MAKE) examples/echoserver/echoserver; wc_egs: $(MAKE) wolfcrypt/test/testwolfcrypt; \ $(MAKE) wolfcrypt/benchmark/benchmark; install-exec-local: install-generic-config install-generic-config: $(mkinstalldirs) $(DESTDIR)$(bindir) $(INSTALL_SCRIPT) @GENERIC_CONFIG@ $(DESTDIR)$(bindir) uninstall-local: -rm -f $(DESTDIR)$(bindir)/@GENERIC_CONFIG@ merge-clean: @find ./ | $(GREP) \.gcda | xargs rm -f @find ./ | $(GREP) \.gcno | xargs rm -f @find ./ | $(GREP) \.gz | xargs rm -f @find ./ | $(GREP) \.orig | xargs rm -f @find ./ | $(GREP) \.rej | xargs rm -f @find ./ | $(GREP) \.rpm | xargs rm -f @find ./ | $(GREP) \.THIS | xargs rm -f @find ./ | $(GREP) \.OTHER | xargs rm -f @find ./ | $(GREP) \.BASE | xargs rm -f @find ./ | $(GREP) \~$$ | xargs rm -f wolfssl-3.10.2-stable/NEWS000066400000000000000000000000001305024512300152160ustar00rootroot00000000000000wolfssl-3.10.2-stable/README000066400000000000000000001663341305024512300154260ustar00rootroot00000000000000*** Notes, Please read *** Note 1) wolfSSL as of 3.6.6 no longer enables SSLv3 by default. wolfSSL also no longer supports static key cipher suites with PSK, RSA, or ECDH. This means if you plan to use TLS cipher suites you must enable DH (DH is on by default), or enable ECC (ECC is on by default on 64bit systems), or you must enable static key cipher suites with WOLFSSL_STATIC_DH WOLFSSL_STATIC_RSA or WOLFSSL_STATIC_PSK though static key cipher suites are deprecated and will be removed from future versions of TLS. They also lower your security by removing PFS. Since current NTRU suites available do not use ephemeral keys, WOLFSSL_STATIC_RSA needs to be used in order to build with NTRU suites. When compiling ssl.c wolfSSL will now issue a compiler error if no cipher suites are available. You can remove this error by defining WOLFSSL_ALLOW_NO_SUITES in the event that you desire that, i.e., you're not using TLS cipher suites. Note 2) wolfSSL takes a different approach to certificate verification than OpenSSL does. The default policy for the client is to verify the server, this means that if you don't load CAs to verify the server you'll get a connect error, no signer error to confirm failure (-188). If you want to mimic OpenSSL behavior of having SSL_connect succeed even if verifying the server fails and reducing security you can do this by calling: wolfSSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, 0); before calling wolfSSL_new(); Though it's not recommended. *** end Notes *** ********* wolfSSL (Formerly CyaSSL) Release 3.10.2 (2/10/2017) Release 3.10.2 of wolfSSL has bug fixes and new features including: - Poly1305 Windows macros fix. Thanks to GitHub user Jay Satiro - Compatibility layer expanded with multiple functions added - Improve fp_copy performance with ALT_ECC_SIZE - OCSP updates and improvements - Fixes for IAR EWARM 8 compiler warnings - Reduce stack usage with ECC_CACHE_CURVE disabled - Added ECC export raw for public and private key - Fix for NO_ASN_TIME build - Supported curves extensions now populated by default - Add DTLS build without big integer math - Fix for static memory feature with wc_ecc_verify_hash_ex and not SHAMIR - Added PSK interoperability testing to script bundled with wolfSSL - Fix for Python wrapper random number generation. Compiler optimizations with Python could place the random number in same buffer location each time. Thanks to GitHub user Erik Bray (embray) - Fix for tests on unaligned memory with static memory feature - Add macro WOLFSSL_NO_OCSP_OPTIONAL_CERTS to skip optional OCSP certificates - Sanity checks on NULL arguments added to wolfSSL_set_fd and wolfSSL_DTLS_SetCookieSecret - mp_jacobi stack use reduced, thanks to Szabi Tolnai for providing a solution to reduce stack usage This release of wolfSSL fixes 2 low and 1 medium level security vulnerability. Low level fix of buffer overflow for when loading in a malformed temporary DH file. Thanks to Yueh-Hsun Lin and Peng Li from KNOX Security, Samsung Research America for the report. Medium level fix for processing of OCSP response. If using OCSP without hard faults enforced and no alternate revocation checks like OCSP stapling then it is recommended to update. Low level fix for potential cache attack on RSA operations. If using wolfSSL RSA on a server that other users can have access to monitor the cache, then it is recommended to update wolfSSL. Thanks to Andreas Zankl, Johann Heyszl and Georg Sigl at Fraunhofer AISEC for the initial report. See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.10.0 (12/21/2016) Release 3.10.0 of wolfSSL has bug fixes and new features including: - Added support for SHA224 - Added scrypt feature - Build for Intel SGX use, added in directory IDE/WIN-SGX - Fix for ChaCha20-Poly1305 ECDSA certificate type request - Enhance PKCS#7 with ECC enveloped data and AES key wrap support - Added support for RIOT OS - Add support for parsing PKCS#12 files - ECC performance increased with custom curves - ARMv8 expanded to AArch32 and performance increased - Added ANSI-X9.63-KDF support - Port to STM32 F2/F4 CubeMX - Port to Atmel ATECC508A board - Removed fPIE by default when wolfSSL library is compiled - Update to Python wrapper, dropping DES and adding wc_RSASetRNG - Added support for NXP K82 hardware acceleration - Added SCR client and server verify check - Added a disable rng option with autoconf - Added more tests vectors to test.c with AES-CTR - Updated DTLS session export version number - Updated DTLS for 64 bit sequence numbers - Fix for memory management with TI and WOLFSSL_SMALL_STACK - Hardening RSA CRT to be constant time - Fix uninitialized warning with IAR compiler - Fix for C# wrapper example IO hang on unexpected connection termination This release of wolfSSL fixes a low level security vulnerability. The vulnerability reported was a potential cache attack on RSA operations. If using wolfSSL RSA on a server that other users can have access to monitor the cache, then it is recommended to update wolfSSL. Thanks to Andreas Zankl, Johann Heyszl and Georg Sigl at Fraunhofer AISEC for the report. More information will be available on our site: https://wolfssl.com/wolfSSL/security/vulnerabilities.php See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.9.10 (9/23/2016) Release 3.9.10 of wolfSSL has bug fixes and new features including: - Default configure option changes: 1. DES3 disabled by default 2. ECC Supported Curves Extension enabled by default 3. New option Extended Master Secret enabled by default - Added checking CA certificate path length, and new test certs - Fix to DSA pre padding and sanity check on R/S values - Added CTX level RNG for single-threaded builds - Intel RDSEED enhancements - ARMv8 hardware acceleration support for AES-CBC/CTR/GCM, SHA-256 - Arduino support updates - Added the Extended Master Secret TLS extension 1. Enabled by default in configure options, API to disable 2. Added support for Extended Master Secret to sniffer - OCSP fix with issuer key hash, lookup refactor - Added support for Frosted OS - Added support for DTLS over SCTP - Added support for static memory with wolfCrypt - Fix to ECC Custom Curve support - Support for asynchronous wolfCrypt RSA and TLS client - Added distribution build configure option - Update the test certificates This release of wolfSSL fixes medium level security vulnerabilities. Fixes for potential AES, RSA, and ECC side channel leaks is included that a local user monitoring the same CPU core cache could exploit. VM users, hyper-threading users, and users where potential attackers have access to the CPU cache will need to update if they utilize AES, RSA private keys, or ECC private keys. Thanks to Gorka Irazoqui Apecechea and Xiaofei Guo from Intel Corporation for the report. More information will be available on our site: https://wolfssl.com/wolfSSL/security/vulnerabilities.php See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.9.8 (7/29/2016) Release 3.9.8 of wolfSSL has bug fixes and new features including: - Add support for custom ECC curves. - Add cipher suite ECDHE-ECDSA-AES128-CCM. - Add compkey enable option. This option is for compressed ECC keys. - Add in the option to use test.h without gettimeofday function using the macro WOLFSSL_USER_CURRTIME. - Add RSA blinding for private key operations. Enable option of harden which is on by default. This negates timing attacks. - Add ECC and TLS support for all SECP, Koblitz and Brainpool curves. - Add helper functions for static memory option to allow getting optimum buffer sizes. - Update DTLS behavior on bad MAC. DTLS silently drops packets with bad MACs now. - Update fp_isprime function from libtom enchancement/cleanup repository. - Update sanity checks on inputs and return values for AES-CMAC. - Update wolfSSL for use with MYSQL v5.6.30. - Update LPCXpresso eclipse project to not include misc.c when not needed. - Fix retransmit of last DTLS flight with timeout notification. The last flight is no longer retransmitted on timeout. - Fixes to some code in math sections for compressed ECC keys. This includes edge cases for buffer size on allocation and adjustments for compressed curves build. The code and full list can be found on github with pull request #456. - Fix function argument mismatch for build with secure renegotiation. - X.509 bug fixes for reading in malformed certificates, reported by researchers at Columbia University - Fix GCC version 6 warning about hard tabs in poly1305.c. This was a warning produced by GCC 6 trying to determine the intent of code. - Fixes for static memory option. Including avoid potential race conditions with counters, decrement handshake counter correctly. - Fix anonymous cipher with Diffie Hellman on the server side. Was an issue of a possible buffer corruption. For information and code see pull request #481. - One high level security fix that requires an update for use with static RSA cipher suites was submitted. This fix was the addition of RSA blinding for private RSA operations. We recommend servers who allow static RSA cipher suites to also generate new private RSA keys. Static RSA cipher suites are turned off by default. See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/wolfSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.9.6 (6/14/2016) Release 3.9.6 of wolfSSL has bug fixes and new features including: - Add staticmemory feature - Add public wc_GetTime API with base64encode feature - Add AES CMAC algorithm - Add DTLS sessionexport feature - Add python wolfCrypt wrapper - Add ECC encrypt/decrypt benchmarks - Add dynamic session tickets - Add eccshamir option - Add Whitewood netRandom support --with-wnr - Add embOS port - Add minimum key size checks for RSA and ECC - Add STARTTLS support to examples - Add uTasker port - Add asynchronous crypto and wolf event support - Add compile check for misc.c with inline - Add RNG benchmark - Add reduction to stack usage with hash-based RNG - Update STM32F2_CRYPTO port with additional algorithms supported - Update MDK5 projects - Update AES-NI - Fix for STM32 with STM32F2_HASH defined - Fix for building with MinGw - Fix ECC math bugs with ALT_ECC_SIZE and key sizes over 256 bit (1) - Fix certificate buffers github issue #422 - Fix decrypt max size with RSA OAEP - Fix DTLS sanity check with DTLS timeout notification - Fix free of WOLFSSL_METHOD on failure to create CTX - Fix memory leak in failure case with wc_RsaFunction (2) - No high level security fixes that requires an update though we always recommend updating to the latest - (1) Code changes for ECC fix can be found at pull requests #411, #416, and #428 - (2) Builds using RSA with using normal math and not RSA_LOW_MEM should update - Tag 3.9.6w is for a Windows example echoserver fix See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/wolfSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.9.0 (3/18/2016) Release 3.9.0 of wolfSSL has bug fixes and new features including: - Add new leantls configuration - Add RSA OAEP padding at wolfCrypt level - Add Arduino port and example client - Add fixed point DH operation - Add CUSTOM_RAND_GENRATE_SEED_OS and CUSTOM_RAND_GENERATE_BLOCK - Add ECDHE-PSK cipher suites - Add PSK ChaCha20-Poly1305 cipher suites - Add option for fail on no peer cert except PSK suites - Add port for Nordic nRF51 - Add additional ECC NIST test vectors for 256, 384 and 521 - Add more granular ECC, Ed25519/Curve25519 and AES configs - Update to ChaCha20-Poly1305 - Update support for Freescale KSDK 1.3.0 - Update DER buffer handling code, refactoring and reducing memory - Fix to AESNI 192 bit key expansion - Fix to C# wrapper character encoding - Fix sequence number issue with DTLS epoch 0 messages - Fix RNGA with K64 build - Fix ASN.1 X509 V3 certificate policy extension parsing - Fix potential free of uninitialized RSA key in asn.c - Fix potential underflow when using ECC build with FP_ECC - Fixes for warnings in Visual Studio 2015 build - No high level security fixes that requires an update though we always recommend updating to the latest - FP_ECC is off by default, users with it enabled should update for the zero sized hash fix See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.8.0 (12/30/2015) Release 3.8.0 of wolfSSL has bug fixes and new features including: - Example client/server with VxWorks - AESNI use with AES-GCM - Stunnel compatibility enhancements - Single shot hash and signature/verify API added - Update cavium nitrox port - LPCXpresso IDE support added - C# wrapper to support wolfSSL use by a C# program - (BETA version)OCSP stapling added - Update OpenSSH compatibility - Improve DTLS handshake when retransmitting finished message - fix idea_mult() for 16 and 32bit systems - fix LowResTimer on Microchip ports - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.7.0 (10/26/2015) Release 3.7.0 of wolfSSL has bug fixes and new features including: - ALPN extension support added for HTTP2 connections with --enable-alpn - Change of example/client/client max fragment flag -L -> -F - Throughput benchmarking, added scripts/benchmark.test - Sniffer API ssl_FreeDecodeBuffer added - Addition of AES_GCM to Sniffer - Sniffer change to handle unlimited decrypt buffer size - New option for the sniffer where it will try to pick up decoding after a sequence number acknowldgement fault. Also includes some additional stats. - JNI API setter and getter function for jobject added - User RSA crypto plugin abstraction. An example placed in wolfcrypt/user-crypto - fix to asn configuration bug - AES-GCM/CCM fixes. - Port for Rowley added - Rowley Crossworks bare metal examples added - MDK5-ARM project update - FreeRTOS support updates. - VXWorks support updates. - Added the IDEA cipher and support in wolfSSL. - Update wolfSSL website CA. - CFLAGS is usable when configuring source. - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.6.8 (09/17/2015) Release 3.6.8 of wolfSSL fixes two high severity vulnerabilities. It also includes bug fixes and new features including: - Two High level security fixes, all users SHOULD update. a) If using wolfSSL for DTLS on the server side of a publicly accessible machine you MUST update. b) If using wolfSSL for TLS on the server side with private RSA keys allowing ephemeral key exchange without low memory optimizations you MUST update and regenerate the private RSA keys. Please see https://www.wolfssl.com/wolfSSL/Blog/Blog.html for more details - No filesystem build fixes for various configurations - Certificate generation now supports several extensions including KeyUsage, SKID, AKID, and Certificate Policies - CRLs can be loaded from buffers as well as files now - SHA-512 Certificate Signing generation - Fixes for sniffer reassembly processing See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html ********* wolfSSL (Formerly CyaSSL) Release 3.6.6 (08/20/2015) Release 3.6.6 of wolfSSL has bug fixes and new features including: - OpenSSH compatibility with --enable-openssh - stunnel compatibility with --enable-stunnel - lighttpd compatibility with --enable-lighty - SSLv3 is now disabled by default, can be enabled with --enable-sslv3 - Ephemeral key cipher suites only are now supported by default To enable static ECDH cipher suites define WOLFSSL_STATIC_DH To enable static RSA cipher suites define WOLFSSL_STATIC_RSA To enable static PSK cipher suites define WOLFSSL_STATIC_PSK - Added QSH (quantum-safe handshake) extension with --enable-ntru - SRP is now part of wolfCrypt, enable with --enabe-srp - Certificate handshake messages can now be sent fragmented if the record size is smaller than the total message size, no user action required. - DTLS duplicate message fixes - Visual Studio project files now support DLL and static builds for 32/64bit. - Support for new Freescale I/O - FreeRTOS FIPS support - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More information can be found on-line at //http://wolfssl.com/yaSSL/Docs.html **************** wolfSSL (Formerly CyaSSL) Release 3.6.0 (06/19/2015) Release 3.6.0 of wolfSSL has bug fixes and new features including: - Max Strength build that only allows TLSv1.2, AEAD ciphers, and PFS (Perfect Forward Secrecy). With --enable-maxstrength - Server side session ticket support, the example server and echoserver use the example callback myTicketEncCb(), see wolfSSL_CTX_set_TicketEncCb() - FIPS version submitted for iOS. - TI Crypto Hardware Acceleration - DTLS fragmentation fixes - ECC key check validation with wc_ecc_check_key() - 32bit code options to reduce memory for Curve25519 and Ed25519 - wolfSSL JNI build switch with --enable-jni - PicoTCP support improvements - DH min ephemeral key size enforcement with wolfSSL_CTX_SetMinDhKey_Sz() - KEEP_PEER_CERT and AltNames can now be used together - ChaCha20 big endian fix - SHA-512 signature algorithm support for key exchange and verify messages - ECC make key crash fix on RNG failure, ECC users must update. - Improvements to usage of time code. - Improvements to VS solution files. - GNU Binutils 2.24 (and late 2.23) ld has problems with some debug builds, to fix an ld error add C_EXTRA_FLAGS="-fdebug-types-section -g1". - No high level security fixes that requires an update though we always recommend updating to the latest (except note 14, ecc RNG failure) See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html *****************wolfSSL (Formerly CyaSSL) Release 3.4.6 (03/30/2015) Release 3.4.6 of wolfSSL has bug fixes and new features including: - Intel Assembly Speedups using instructions rdrand, rdseed, aesni, avx1/2, rorx, mulx, adox, adcx . They can be enabled with --enable-intelasm. These speedup the use of RNG, SHA2, and public key algorithms. - Ed25519 support at the crypto level. Turn on with --enable-ed25519. Examples in wolcrypt/test/test.c ed25519_test(). - Post Handshake Memory reductions. wolfSSL can now hold less than 1,000 bytes of memory per secure connection including cipher state. - wolfSSL API and wolfCrypt API fixes, you can still include the cyassl and ctaocrypt headers which will enable the compatibility APIs for the foreseeable future - INSTALL file to help direct users to build instructions for their environment - For ECC users with the normal math library a fix that prevents a crash when verify signature fails. Users of 3.4.0 with ECC and the normal math library must update - RC4 is now disabled by default in autoconf mode - AES-GCM and ChaCha20/Poly1305 are now enabled by default to make AEAD ciphers available without a switch - External ChaCha-Poly AEAD API, thanks to Andrew Burks for the contribution - DHE-PSK cipher suites can now be built without ASN or Cert support - Fix some NO MD5 build issues with optional features - Freescale CodeWarrior project updates - ECC curves can be individually turned on/off at build time. - Sniffer handles Cert Status message and other minor fixes - SetMinVersion() at the wolfSSL Context level instead of just SSL session level to allow minimum protocol version allowed at runtime - RNG failure resource cleanup fix - No high level security fixes that requires an update though we always recommend updating to the latest (except note 6 use case of ecc/normal math) See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html *****************wolfSSL (Formerly CyaSSL) Release 3.4.0 (02/23/2015) Release 3.4.0 wolfSSL has bug fixes and new features including: - wolfSSL API and wolfCrypt API, you can still include the cyassl and ctaocrypt headers which will enable the compatibility APIs for the foreseeable future - Example use of the wolfCrypt API can be found in wolfcrypt/test/test.c - Example use of the wolfSSL API can be found in examples/client/client.c - Curve25519 now supported at the wolfCrypt level, wolfSSL layer coming soon - Improvements in the build configuration under AIX - Microchip Pic32 MZ updates - TIRTOS updates - PowerPC updates - Xcode project update - Bidirectional shutdown examples in client/server with -w (wait for full shutdown) option - Cycle counts on benchmarks for x86_64, more coming soon - ALT_ECC_SIZE for reducing ecc heap use with fastmath when also using large RSA keys - Various compile warnings - Scan-build warning fixes - Changed a memcpy to memmove in the sniffer (if using sniffer please update) - No high level security fixes that requires an update though we always recommend updating to the latest ***********CyaSSL Release 3.3.0 (12/05/2014) - Countermeasuers for Handshake message duplicates, CHANGE CIPHER without FINISHED, and fast forward attempts. Thanks to Karthikeyan Bhargavan from the Prosecco team at INRIA Paris-Rocquencourt for the report. - FIPS version submitted - Removes SSLv2 Client Hello processing, can be enabled with OLD_HELLO_ALLOWED - User can set minimum downgrade version with CyaSSL_SetMinVersion() - Small stack improvements at TLS/SSL layer - TLS Master Secret generation and Key Expansion are now exposed - Adds client side Secure Renegotiation, * not recommended * - Client side session ticket support, not fully tested with Secure Renegotiation - Allows up to 4096bit DHE at TLS Key Exchange layer - Handles non standard SessionID sizes in Hello Messages - PicoTCP Support - Sniffer now supports SNI Virtual Hosts - Sniffer now handles non HTTPS protocols using STARTTLS - Sniffer can now parse records with multiple messages - TI-RTOS updates - Fix for ColdFire optimized fp_digit read only in explicit 32bit case - ADH Cipher Suite ADH-AES128-SHA for EAP-FAST The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ***********CyaSSL Release 3.2.0 (09/10/2014) Release 3.2.0 CyaSSL has bug fixes and new features including: - ChaCha20 and Poly1305 crypto and suites - Small stack improvements for OCSP, CRL, TLS, DTLS - NTRU Encrypt and Decrypt benchmarks - Updated Visual Studio project files - Updated Keil MDK5 project files - Fix for DTLS sequence numbers with GCM/CCM - Updated HashDRBG with more secure struct declaration - TI-RTOS support and example Code Composer Studio project files - Ability to get enabled cipher suites, CyaSSL_get_ciphers() - AES-GCM/CCM/Direct support for Freescale mmCAU and CAU - Sniffer improvement checking for decrypt key setup - Support for raw ECC key import - Ability to convert ecc_key to DER, EccKeyToDer() - Security fix for RSA Padding check vulnerability reported by Intel Security Advanced Threat Research team The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************ CyaSSL Release 3.1.0 (07/14/2014) Release 3.1.0 CyaSSL has bug fixes and new features including: - Fix for older versions of icc without 128-bit type - Intel ASM syntax for AES-NI - Updated NTRU support, keygen benchmark - FIPS check for minimum required HMAC key length - Small stack (--enable-smallstack) improvements for PKCS#7, ASN - TLS extension support for DTLS - Default I/O callbacks external to user - Updated example client with bad clock test - Ability to set optional ECC context info - Ability to enable/disable DH separate from opensslextra - Additional test key/cert buffers for CA and server - Updated example certificates The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************ CyaSSL Release 3.0.2 (05/30/2014) Release 3.0.2 CyaSSL has bug fixes and new features including: - Added the following cipher suites: * TLS_PSK_WITH_AES_128_GCM_SHA256 * TLS_PSK_WITH_AES_256_GCM_SHA384 * TLS_PSK_WITH_AES_256_CBC_SHA384 * TLS_PSK_WITH_NULL_SHA384 * TLS_DHE_PSK_WITH_AES_128_GCM_SHA256 * TLS_DHE_PSK_WITH_AES_256_GCM_SHA384 * TLS_DHE_PSK_WITH_AES_128_CBC_SHA256 * TLS_DHE_PSK_WITH_AES_256_CBC_SHA384 * TLS_DHE_PSK_WITH_NULL_SHA256 * TLS_DHE_PSK_WITH_NULL_SHA384 * TLS_DHE_PSK_WITH_AES_128_CCM * TLS_DHE_PSK_WITH_AES_256_CCM - Added AES-NI support for Microsoft Visual Studio builds. - Changed small stack build to be disabled by default. - Updated the Hash DRBG and provided a configure option to enable. The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************ CyaSSL Release 3.0.0 (04/29/2014) Release 3.0.0 CyaSSL has bug fixes and new features including: - FIPS release candidate - X.509 improvements that address items reported by Suman Jana with security researchers at UT Austin and UC Davis - Small stack size improvements, --enable-smallstack. Offloads large local variables to the heap. (Note this is not complete.) - Updated AES-CCM-8 cipher suites to use approved suite numbers. The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************ CyaSSL Release 2.9.4 (04/09/2014) Release 2.9.4 CyaSSL has bug fixes and new features including: - Security fixes that address items reported by Ivan Fratric of the Google Security Team - X.509 Unknown critical extensions treated as errors, report by Suman Jana with security researchers at UT Austin and UC Davis - Sniffer fixes for corrupted packet length and Jumbo frames - ARM thumb mode assembly fixes - Xcode 5.1 support including new clang - PIC32 MZ hardware support - CyaSSL Object has enough room to read the Record Header now w/o allocs - FIPS wrappers for AES, 3DES, SHA1, SHA256, SHA384, HMAC, and RSA. - A sample I/O pool is demonstrated with --enable-iopool to overtake memory handling and reduce memory fragmentation on I/O large sizes The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************ CyaSSL Release 2.9.0 (02/07/2014) Release 2.9.0 CyaSSL has bug fixes and new features including: - Freescale Kinetis RNGB support - Freescale Kinetis mmCAU support - TLS Hello extensions - ECC - Secure Renegotiation (null) - Truncated HMAC - SCEP support - PKCS #7 Enveloped data and signed data - PKCS #10 Certificate Signing Request generation - DTLS sliding window - OCSP Improvements - API change to integrate into Certificate Manager - IPv4/IPv6 agnostic - example client/server support for OCSP - OCSP nonces are optional - GMAC hashing - Windows build additions - Windows CYGWIN build fixes - Updated test certificates - Microchip MPLAB Harmony support - Update autoconf scripts - Additional X.509 inspection functions - ECC encrypt/decrypt primitives - ECC Certificate generation The Freescale Kinetis K53 RNGB documentation can be found in Chapter 33 of the K53 Sub-Family Reference Manual: http://cache.freescale.com/files/32bit/doc/ref_manual/K53P144M100SF2RM.pdf Freescale Kinetis K60 mmCAU (AES, DES, 3DES, MD5, SHA, SHA256) documentation can be found in the "ColdFire/ColdFire+ CAU and Kinetis mmCAU Software Library User Guide": http://cache.freescale.com/files/32bit/doc/user_guide/CAUAPIUG.pdf *****************CyaSSL Release 2.8.0 (8/30/2013) Release 2.8.0 CyaSSL has bug fixes and new features including: - AES-GCM and AES-CCM use AES-NI - NetX default IO callback handlers - IPv6 fixes for DTLS Hello Cookies - The ability to unload Certs/Keys after the handshake, CyaSSL_UnloadCertsKeys() - SEP certificate extensions - Callback getters for easier resource freeing - External CYASSL_MAX_ERROR_SZ for correct error buffer sizing - MacEncrypt and DecryptVerify Callbacks for User Atomic Record Layer Processing - Public Key Callbacks for ECC and RSA - Client now sends blank cert upon request if doesn't have one with TLS <= 1.2 The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. *****************CyaSSL Release 2.7.0 (6/17/2013) Release 2.7.0 CyaSSL has bug fixes and new features including: - SNI support for client and server - KEIL MDK-ARM projects - Wildcard check to domain name match, and Subject altnames are checked too - Better error messages for certificate verification errors - Ability to discard session during handshake verify - More consistent error returns across all APIs - Ability to unload CAs at the CTX or CertManager level - Authority subject id support for Certificate matching - Persistent session cache functionality - Persistent CA cache functionality - Client session table lookups to push serverID table to library level - Camellia support to sniffer - User controllable settings for DTLS timeout values - Sniffer fixes for caching long lived sessions - DTLS reliability enhancements for the handshake - Better ThreadX support When compiling with Mingw, libtool may give the following warning due to path conversion errors: libtool: link: Could not determine host file name corresponding to ** libtool: link: Continuing, but uninstalled executables may not work. If so, examples and testsuite will have problems when run, showing an error while loading shared libraries. To resolve, please run "make install". The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************** CyaSSL Release 2.6.0 (04/15/2013) Release 2.6.0 CyaSSL has bug fixes and new features including: - DTLS 1.2 support including AEAD ciphers - SHA-3 finalist Blake2 support, it's fast and uses little resources - SHA-384 cipher suites including ECC ones - HMAC now supports SHA-512 - Track memory use for example client/server with -t option - Better IPv6 examples with --enable-ipv6, before if ipv6 examples/tests were turned on, localhost only was used. Now link-local (with scope ids) and ipv6 hosts can be used as well. - Xcode v4.6 project for iOS v6.1 update - settings.h is now checked in all *.c files for true one file setting detection - Better alignment at SSL layer for hardware crypto alignment needs * Note, SSL itself isn't friendly to alignment with 5 byte TLS headers and 13 bytes DTLS headers, but every effort is now made to align with the CYASSL_GENERAL_ALIGNMENT flag which sets desired alignment requirement - NO_64BIT flag to turn off 64bit data type accumulators in public key code * Note, some systems are faster with 32bit accumulators - --enable-stacksize for example client/server stack use * Note, modern desktop Operating Systems may add bytes to each stack frame - Updated compression/decompression with direct crypto access - All ./configure options are now lowercase only for consistency - ./configure builds default to fastmath option * Note, if on ia32 and building in shared mode this may produce a problem with a missing register being available because of PIC, there are at least 6 solutions to this: 1) --disable-fastmath , don't use fastmath 2) --disable-shared, don't build a shared library 3) C_EXTRA_FLAGS=-DTFM_NO_ASM , turn off assembly use 4) use clang, it just seems to work 5) play around with no PIC options to force all registers being open, e.g, --without-pic 6) if static lib is still a problem try removing fPIE - Many new ./configure switches for option enable/disable for example * rsa * dh * dsa * md5 * sha * arc4 * null (allow NULL ciphers) * oldtls (only use TLS 1.2) * asn (no certs or public keys allowed) - ./configure generates cyassl/options.h which allows a header the user can include in their app to make sure the same options are set at the app and CyaSSL level. - autoconf no longer needs serial-tests which lowers version requirements of automake to 1.11 and autoconf to 2.63 The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************** CyaSSL Release 2.5.0 (02/04/2013) Release 2.5.0 CyaSSL has bug fixes and new features including: - Fix for TLS CBC padding timing attack identified by Nadhem Alfardan and Kenny Paterson: http://www.isg.rhul.ac.uk/tls/ - Microchip PIC32 (MIPS16, MIPS32) support - Microchip MPLAB X example projects for PIC32 Ethernet Starter Kit - Updated CTaoCrypt benchmark app for embedded systems - 1024-bit test certs/keys and cert/key buffers - AES-CCM-8 crypto and cipher suites - Camellia crypto and cipher suites - Bumped minimum autoconf version to 2.65, automake version to 1.12 - Addition of OCSP callbacks - STM32F2 support with hardware crypto and RNG - Cavium NITROX support CTaoCrypt now has support for the Microchip PIC32 and has been tested with the Microchip PIC32 Ethernet Starter Kit, the XC32 compiler and MPLAB X IDE in both MIPS16 and MIPS32 instruction set modes. See the README located under the /mplabx directory for more details. To add Cavium NITROX support do: ./configure --with-cavium=/home/user/cavium/software pointing to your licensed cavium/software directory. Since Cavium doesn't build a library we pull in the cavium_common.o file which gives a libtool warning about the portability of this. Also, if you're using the github source tree you'll need to remove the -Wredundant-decls warning from the generated Makefile because the cavium headers don't conform to this warning. Currently CyaSSL supports Cavium RNG, AES, 3DES, RC4, HMAC, and RSA directly at the crypto layer. Support at the SSL level is partial and currently just does AES, 3DES, and RC4. RSA and HMAC are slower until the Cavium calls can be utilized in non blocking mode. The example client turns on cavium support as does the crypto test and benchmark. Please see the HAVE_CAVIUM define. CyaSSL is able to use the STM32F2 hardware-based cryptography and random number generator through the STM32F2 Standard Peripheral Library. For necessary defines, see the CYASSL_STM32F2 define in settings.h. Documentation for the STM32F2 Standard Peripheral Library can be found in the following document: http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/USER_MANUAL/DM00023896.pdf The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. *************** CyaSSL Release 2.4.6 (12/20/2012) Release 2.4.6 CyaSSL has bug fixes and a few new features including: - ECC into main version - Lean PSK build (reduced code size, RAM usage, and stack usage) - FreeBSD CRL monitor support - CyaSSL_peek() - CyaSSL_send() and CyaSSL_recv() for I/O flag setting - CodeWarrior Support - MQX Support - Freescale Kinetis support including Hardware RNG - autoconf builds use jobserver - cyassl-config - Sniffer memory reductions Thanks to Brian Aker for the improved autoconf system, make rpm, cyassl-config, warning system, and general good ideas for improving CyaSSL! The Freescale Kinetis K70 RNGA documentation can be found in Chapter 37 of the K70 Sub-Family Reference Manual: http://cache.freescale.com/files/microcontrollers/doc/ref_manual/K70P256M150SF3RM.pdf The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. *************** CyaSSL Release 2.4.0 (10/10/2012) Release 2.4.0 CyaSSL has bug fixes and a few new features including: - DTLS reliability - Reduced memory usage after handshake - Updated build process The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. *************** CyaSSL Release 2.3.0 (8/10/2012) Release 2.3.0 CyaSSL has bug fixes and a few new features including: - AES-GCM crypto and cipher suites - make test cipher suite checks - Subject AltName processing - Command line support for client/server examples - Sniffer SessionTicket support - SHA-384 cipher suites - Verify cipher suite validity when user overrides - CRL dir monitoring - DTLS Cookie support, reliability coming soon The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ***************CyaSSL Release 2.2.0 (5/18/2012) Release 2.2.0 CyaSSL has bug fixes and a few new features including: - Initial CRL support (--enable-crl) - Initial OCSP support (--enable-ocsp) - Add static ECDH suites - SHA-384 support - ECC client certificate support - Add medium session cache size (1055 sessions) - Updated unit tests - Protection against mutex reinitialization The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ***************CyaSSL Release 2.0.8 (2/24/2012) Release 2.0.8 CyaSSL has bug fixes and a few new features including: - A fix for malicious certificates pointed out by Remi Gacogne (thanks) resulting in NULL pointer use. - Respond to renegotiation attempt with no_renegoatation alert - Add basic path support for load_verify_locations() - Add set Temp EC-DHE key size - Extra checks on rsa test when porting into The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************* CyaSSL Release 2.0.6 (1/27/2012) Release 2.0.6 CyaSSL has bug fixes and a few new features including: - Fixes for CA basis constraint check - CTX reference counting - Initial unit test additions - Lean and Mean Windows fix - ECC benchmarking - SSMTP build support - Ability to group handshake messages with set_group_messages(ctx/ssl) - CA cache addition callback - Export Base64_Encode for general use The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************* CyaSSL Release 2.0.2 (12/05/2011) Release 2.0.2 CyaSSL has bug fixes and a few new features including: - CTaoCrypt Runtime library detection settings when directly using the crypto library - Default certificate generation now uses SHAwRSA and adds SHA256wRSA generation - All test certificates now use 2048bit and SHA-1 for better modern browser support - Direct AES block access and AES-CTR (counter) mode - Microchip pic32 support The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************* CyaSSL Release 2.0.0rc3 (9/28/2011) Release 2.0.0rc3 for CyaSSL has bug fixes and a few new features including: - updated autoconf support - better make install and uninstall (uses system directories) - make test / make check - CyaSSL headers now in - CTaocrypt headers now in - OpenSSL compatibility headers now in - examples and tests all run from home directory so can use certs in ./certs (see note 1) So previous applications that used the OpenSSL compatibility header now need to include instead, no other changes are required. Special Thanks to Brian Aker for his autoconf, install, and header patches. The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ************CyaSSL Release 2.0.0rc2 (6/6/2011) Release 2.0.0rc2 for CyaSSL has bug fixes and a few new features including: - bug fixes (Alerts, DTLS with DHE) - FreeRTOS support - lwIP support - Wshadow warnings removed - asn public header - CTaoCrypt public headers now all have ctc_ prefix (the manual is still being updated to reflect this change) - and more. This is the 2nd and perhaps final release candidate for version 2. Please send any comments or questions to support@wolfssl.com. The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ***********CyaSSL Release 2.0.0rc1 (5/2/2011) Release 2.0.0rc1 for CyaSSL has many new features including: - bug fixes - SHA-256 cipher suites - Root Certificate Verification (instead of needing all certs in the chain) - PKCS #8 private key encryption (supports PKCS #5 v1-v2 and PKCS #12) - Serial number retrieval for x509 - PBKDF2 and PKCS #12 PBKDF - UID parsing for x509 - SHA-256 certificate signatures - Client and server can send chains (SSL_CTX_use_certificate_chain_file) - CA loading can now parse multiple certificates per file - Dynamic memory runtime hooks - Runtime hooks for logging - EDH on server side - More informative error codes - More informative logging messages - Version downgrade more robust (use SSL_v23*) - Shared build only by default through ./configure - Compiler visibility is now used, internal functions not polluting namespace - Single Makefile, no recursion, for faster and simpler building - Turn on all warnings possible build option, warning fixes - and more. Because of all the new features and the multiple OS, compiler, feature-set options that CyaSSL allows, there may be some configuration fixes needed. Please send any comments or questions to support@wolfssl.com. The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. ****************** CyaSSL Release 1.9.0 (3/2/2011) Release 1.9.0 for CyaSSL adds bug fixes, improved TLSv1.2 through testing and better hash/sig algo ids, --enable-webServer for the yaSSL embedded web server, improper AES key setup detection, user cert verify callback improvements, and more. The CyaSSL manual offering is included in the doc/ directory. For build instructions and comments about the new features please check the manual. Please send any comments or questions to support@wolfssl.com. ****************** CyaSSL Release 1.8.0 (12/23/2010) Release 1.8.0 for CyaSSL adds bug fixes, x509 v3 CA signed certificate generation, a C standard library abstraction layer, lower memory use, increased portability through the os_settings.h file, and the ability to use NTRU cipher suites when used in conjunction with an NTRU license and library. The initial CyaSSL manual offering is included in the doc/ directory. For build instructions and comments about the new features please check the manual. Please send any comments or questions to support@wolfssl.com. Happy Holidays. ********************* CyaSSL Release 1.6.5 (9/9/2010) Release 1.6.5 for CyaSSL adds bug fixes and x509 v3 self signed certificate generation. For general build instructions see doc/Building_CyaSSL.pdf. To enable certificate generation support add this option to ./configure ./configure --enable-certgen An example is included in ctaocrypt/test/test.c and documentation is provided in doc/CyaSSL_Extensions_Reference.pdf item 11. ********************** CyaSSL Release 1.6.0 (8/27/2010) Release 1.6.0 for CyaSSL adds bug fixes, RIPEMD-160, SHA-512, and RSA key generation. For general build instructions see doc/Building_CyaSSL.pdf. To add RIPEMD-160 support add this option to ./configure ./configure --enable-ripemd To add SHA-512 support add this option to ./configure ./configure --enable-sha512 To add RSA key generation support add this option to ./configure ./configure --enable-keygen Please see ctaocrypt/test/test.c for examples and usage. For Windows, RIPEMD-160 and SHA-512 are enabled by default but key generation is off by default. To turn key generation on add the define CYASSL_KEY_GEN to CyaSSL. ************* CyaSSL Release 1.5.6 (7/28/2010) Release 1.5.6 for CyaSSL adds bug fixes, compatibility for our JSSE provider, and a fix for GCC builds on some systems. For general build instructions see doc/Building_CyaSSL.pdf. To add AES-NI support add this option to ./configure ./configure --enable-aesni You'll need GCC 4.4.3 or later to make use of the assembly. ************** CyaSSL Release 1.5.4 (7/7/2010) Release 1.5.4 for CyaSSL adds bug fixes, support for AES-NI, SHA1 speed improvements from loop unrolling, and support for the Mongoose Web Server. For general build instructions see doc/Building_CyaSSL.pdf. To add AES-NI support add this option to ./configure ./configure --enable-aesni You'll need GCC 4.4.3 or later to make use of the assembly. *************** CyaSSL Release 1.5.0 (5/11/2010) Release 1.5.0 for CyaSSL adds bug fixes, GoAhead WebServer support, sniffer support, and initial swig interface support. For general build instructions see doc/Building_CyaSSL.pdf. To add support for GoAhead WebServer either --enable-opensslExtra or if you don't want all the features of opensslExtra you can just define GOAHEAD_WS instead. GOAHEAD_WS can be added to ./configure with CFLAGS=-DGOAHEAD_WS or you can define it yourself. To look at the sniffer support please see the sniffertest app in sslSniffer/sslSnifferTest. Build with --enable-sniffer on *nix or use the vcproj files on windows. You'll need to have pcap installed on *nix and WinPcap on windows. A swig interface file is now located in the swig directory for using Python, Java, Perl, and others with CyaSSL. This is initial support and experimental, please send questions or comments to support@wolfssl.com. When doing load testing with CyaSSL, on the echoserver example say, the client machine may run out of tcp ephemeral ports, they will end up in the TIME_WAIT queue, and can't be reused by default. There are generally two ways to fix this. 1) Reduce the length sockets remain on the TIME_WAIT queue or 2) Allow items on the TIME_WAIT queue to be reused. To reduce the TIME_WAIT length in OS X to 3 seconds (3000 milliseconds) sudo sysctl -w net.inet.tcp.msl=3000 In Linux sudo sysctl -w net.ipv4.tcp_tw_reuse=1 allows reuse of sockets in TIME_WAIT sudo sysctl -w net.ipv4.tcp_tw_recycle=1 works but seems to remove sockets from TIME_WAIT entirely? sudo sysctl -w net.ipv4.tcp_fin_timeout=1 doen't control TIME_WAIT, it controls FIN_WAIT(2) contrary to some posts ******************** CyaSSL Release 1.4.0 (2/18/2010) Release 1.3.0 for CyaSSL adds bug fixes, better multi TLS/SSL version support through SSLv23_server_method(), and improved documentation in the doc/ folder. For general build instructions doc/Building_CyaSSL.pdf. ******************** CyaSSL Release 1.3.0 (1/21/2010) Release 1.3.0 for CyaSSL adds bug fixes, a potential security problem fix, better porting support, removal of assert()s, and a complete THREADX port. For general build instructions see rc1 below. ******************** CyaSSL Release 1.2.0 (11/2/2009) Release 1.2.0 for CyaSSL adds bug fixes and session negotiation if first use is read or write. For general build instructions see rc1 below. ******************** CyaSSL Release 1.1.0 (9/2/2009) Release 1.1.0 for CyaSSL adds bug fixes, a check against malicious session cache use, support for lighttpd, and TLS 1.2. To get TLS 1.2 support please use the client and server functions: SSL_METHOD *TLSv1_2_server_method(void); SSL_METHOD *TLSv1_2_client_method(void); CyaSSL was tested against lighttpd 1.4.23. To build CyaSSL for use with lighttpd use the following commands from the CyaSSL install dir : ./configure --disable-shared --enable-opensslExtra --enable-fastmath --without-zlib make make openssl-links Then to build lighttpd with CyaSSL use the following commands from the lighttpd install dir: ./configure --with-openssl --with-openssl-includes=/include --with-openssl-libs=/lib LDFLAGS=-lm make On some systems you may get a linker error about a duplicate symbol for MD5_Init or other MD5 calls. This seems to be caused by the lighttpd src file md5.c, which defines MD5_Init(), and is included in liblightcomp_la-md5.o. When liblightcomp is linked with the SSL_LIBs the linker may complain about the duplicate symbol. This can be fixed by editing the lighttpd src file md5.c and adding this line to the beginning of the file: #if 0 and this line to the end of the file #endif Then from the lighttpd src dir do a: make clean make If you get link errors about undefined symbols more than likely the actual OpenSSL libraries are found by the linker before the CyaSSL openssl-links that point to the CyaSSL library, causing the linker confusion. This can be fixed by editing the Makefile in the lighttpd src directory and changing the line: SSL_LIB = -lssl -lcrypto to SSL_LIB = -lcyassl Then from the lighttpd src dir do a: make clean make This should remove any confusion the linker may be having with missing symbols. For any questions or concerns please contact support@wolfssl.com . For general build instructions see rc1 below. ******************CyaSSL Release 1.0.6 (8/03/2009) Release 1.0.6 for CyaSSL adds bug fixes, an improved session cache, and faster math with a huge code option. The session cache now defaults to a client mode, also good for embedded servers. For servers not under heavy load (less than 200 new sessions per minute), define BIG_SESSION_CACHE. If the server will be under heavy load, define HUGE_SESSION_CACHE. There is now a fasthugemath option for configure. This enables fastmath plus even faster math by greatly increasing the code size of the math library. Use the benchmark utility to compare public key operations. For general build instructions see rc1 below. ******************CyaSSL Release 1.0.3 (5/10/2009) Release 1.0.3 for CyaSSL adds bug fixes and add increased support for OpenSSL compatibility when building other applications. Release 1.0.3 includes an alpha release of DTLS for both client and servers. This is only for testing purposes at this time. Rebroadcast and reordering aren't fully implemented at this time but will be for the next release. For general build instructions see rc1 below. ******************CyaSSL Release 1.0.2 (4/3/2009) Release 1.0.2 for CyaSSL adds bug fixes for a couple I/O issues. Some systems will send a SIGPIPE on socket recv() at any time and this should be handled by the application by turning off SIGPIPE through setsockopt() or returning from the handler. Release 1.0.2 includes an alpha release of DTLS for both client and servers. This is only for testing purposes at this time. Rebroadcast and reordering aren't fully implemented at this time but will be for the next release. For general build instructions see rc1 below. *****************CyaSSL Release Candidate 3 rc3-1.0.0 (2/25/2009) Release Candidate 3 for CyaSSL 1.0.0 adds bug fixes and adds a project file for iPhone development with Xcode. cyassl-iphone.xcodeproj is located in the root directory. This release also includes a fix for supporting other implementations that bundle multiple messages at the record layer, this was lost when cyassl i/o was re-implemented but is now fixed. For general build instructions see rc1 below. *****************CyaSSL Release Candidate 2 rc2-1.0.0 (1/21/2009) Release Candidate 2 for CyaSSL 1.0.0 adds bug fixes and adds two new stream ciphers along with their respective cipher suites. CyaSSL adds support for HC-128 and RABBIT stream ciphers. The new suites are: TLS_RSA_WITH_HC_128_SHA TLS_RSA_WITH_RABBIT_SHA And the corresponding cipher names are HC128-SHA RABBIT-SHA CyaSSL also adds support for building with devkitPro for PPC by changing the library proper to use libogc. The examples haven't been changed yet but if there's interest they can be. Here's an example ./configure to build CyaSSL for devkitPro: ./configure --disable-shared CC=/pathTo/devkitpro/devkitPPC/bin/powerpc-gekko-gcc --host=ppc --without-zlib --enable-singleThreaded RANLIB=/pathTo/devkitpro/devkitPPC/bin/powerpc-gekko-ranlib CFLAGS="-DDEVKITPRO -DGEKKO" For linking purposes you'll need LDFLAGS="-g -mrvl -mcpu=750 -meabi -mhard-float -Wl,-Map,$(notdir $@).map" For general build instructions see rc1 below. ********************CyaSSL Release Candidate 1 rc1-1.0.0 (12/17/2008) Release Candidate 1 for CyaSSL 1.0.0 contains major internal changes. Several areas have optimization improvements, less dynamic memory use, and the I/O strategy has been refactored to allow alternate I/O handling or Library use. Many thanks to Thierry Fournier for providing these ideas and most of the work. Because of these changes, this release is only a candidate since some problems are probably inevitable on some platform with some I/O use. Please report any problems and we'll try to resolve them as soon as possible. You can contact us at support@wolfssl.com or todd@wolfssl.com. Using TomsFastMath by passing --enable-fastmath to ./configure now uses assembly on some platforms. This is new so please report any problems as every compiler, mode, OS combination hasn't been tested. On ia32 all of the registers need to be available so be sure to pass these options to CFLAGS: CFLAGS="-O3 -fomit-frame-pointer" OS X will also need -mdynamic-no-pic added to CFLAGS Also if you're building in shared mode for ia32 you'll need to pass options to LDFLAGS as well on OS X: LDFLAGS=-Wl,-read_only_relocs,warning This gives warnings for some symbols but seems to work. --To build on Linux, Solaris, *BSD, Mac OS X, or Cygwin: ./configure make from the ./testsuite/ directory run ./testsuite to make a debug build: ./configure --enable-debug --disable-shared make --To build on Win32 Choose (Re)Build All from the project workspace Run the testsuite program *************************CyaSSL version 0.9.9 (7/25/2008) This release of CyaSSL adds bug fixes, Pre-Shared Keys, over-rideable memory handling, and optionally TomsFastMath. Thanks to Moisés Guimarães for the work on TomsFastMath. To optionally use TomsFastMath pass --enable-fastmath to ./configure Or define USE_FAST_MATH in each project from CyaSSL for MSVC. Please use the benchmark routine before and after to see the performance difference, on some platforms the gains will be little but RSA encryption always seems to be faster. On x86-64 machines with GCC the normal math library may outperform the fast one when using CFLAGS=-m64 because TomsFastMath can't yet use -m64 because of GCCs inability to do 128bit division. **** UPDATE GCC 4.2.1 can now do 128bit division *** See notes below (0.2.0) for complete build instructions. ****************CyaSSL version 0.9.8 (5/7/2008) This release of CyaSSL adds bug fixes, client side Diffie-Hellman, and better socket handling. See notes below (0.2.0) for complete build instructions. ****************CyaSSL version 0.9.6 (1/31/2008) This release of CyaSSL adds bug fixes, increased session management, and a fix for gnutls. See notes below (0.2.0) for complete build instructions. ****************CyaSSL version 0.9.0 (10/15/2007) This release of CyaSSL adds bug fixes, MSVC 2005 support, GCC 4.2 support, IPV6 support and test, and new test certificates. See notes below (0.2.0) for complete build instructions. ****************CyaSSL version 0.8.0 (1/10/2007) This release of CyaSSL adds increased socket support, for non-blocking writes, connects, and interrupted system calls. See notes below (0.2.0) for complete build instructions. ****************CyaSSL version 0.6.3 (10/30/2006) This release of CyaSSL adds debug logging to stderr to aid in the debugging of CyaSSL on systems that may not provide the best support. If CyaSSL is built with debugging support then you need to call CyaSSL_Debugging_ON() to turn logging on. On Unix use ./configure --enable-debug On Windows define DEBUG_CYASSL when building CyaSSL To turn logging back off call CyaSSL_Debugging_OFF() See notes below (0.2.0) for complete build instructions. *****************CyaSSL version 0.6.2 (10/29/2006) This release of CyaSSL adds TLS 1.1. Note that CyaSSL has certificate verification on by default, unlike OpenSSL. To emulate OpenSSL behavior, you must call SSL_CTX_set_verify() with SSL_VERIFY_NONE. In order to have full security you should never do this, provide CyaSSL with the proper certificates to eliminate impostors and call CyaSSL_check_domain_name() to prevent man in the middle attacks. See notes below (0.2.0) for build instructions. *****************CyaSSL version 0.6.0 (10/25/2006) This release of CyaSSL adds more SSL functions, better autoconf, nonblocking I/O for accept, connect, and read. There is now an --enable-small configure option that turns off TLS, AES, DES3, HMAC, and ERROR_STRINGS, see configure.in for the defines. Note that TLS requires HMAC and AES requires TLS. See notes below (0.2.0) for build instructions. *****************CyaSSL version 0.5.5 (09/27/2006) This mini release of CyaSSL adds better input processing through buffered input and big message support. Added SSL_pending() and some sanity checks on user settings. See notes below (0.2.0) for build instructions. *****************CyaSSL version 0.5.0 (03/27/2006) This release of CyaSSL adds AES support and minor bug fixes. See notes below (0.2.0) for build instructions. *****************CyaSSL version 0.4.0 (03/15/2006) This release of CyaSSL adds TLSv1 client/server support and libtool. See notes below for build instructions. *****************CyaSSL version 0.3.0 (02/26/2006) This release of CyaSSL adds SSLv3 server support and session resumption. See notes below for build instructions. *****************CyaSSL version 0.2.0 (02/19/2006) This is the first release of CyaSSL and its crypt brother, CTaoCrypt. CyaSSL is written in ANSI C with the idea of a small code size, footprint, and memory usage in mind. CTaoCrypt can be as small as 32K, and the current client version of CyaSSL can be as small as 12K. The first release of CTaoCrypt supports MD5, SHA-1, 3DES, ARC4, Big Integer Support, RSA, ASN parsing, and basic x509 (en/de)coding. The first release of CyaSSL supports normal client RSA mode SSLv3 connections with support for SHA-1 and MD5 digests. Ciphers include 3DES and RC4. --To build on Linux, Solaris, *BSD, Mac OS X, or Cygwin: ./configure make from the ./testsuite/ directory run ./testsuite to make a debug build: ./configure --enable-debug --disable-shared make --To build on Win32 Choose (Re)Build All from the project workspace Run the testsuite program *** The next release of CyaSSL will support a server and more OpenSSL compatibility functions. Please send questions or comments to todd@wolfssl.com wolfssl-3.10.2-stable/README.md000066400000000000000000001656041305024512300160240ustar00rootroot00000000000000# Notes - Please read ## Note 1 ``` wolfSSL as of 3.6.6 no longer enables SSLv3 by default. wolfSSL also no longer supports static key cipher suites with PSK, RSA, or ECDH. This means if you plan to use TLS cipher suites you must enable DH (DH is on by default), or enable ECC (ECC is on by default on 64bit systems), or you must enable static key cipher suites with WOLFSSL_STATIC_DH WOLFSSL_STATIC_RSA or WOLFSSL_STATIC_PSK though static key cipher suites are deprecated and will be removed from future versions of TLS. They also lower your security by removing PFS. Since current NTRU suites available do not use ephemeral keys, WOLFSSL_STATIC_RSA needs to be used in order to build with NTRU suites. When compiling ssl.c wolfSSL will now issue a compiler error if no cipher suites are available. You can remove this error by defining WOLFSSL_ALLOW_NO_SUITES in the event that you desire that, i.e., you're not using TLS cipher suites. ``` ## Note 2 ``` wolfSSL takes a different approach to certificate verification than OpenSSL does. The default policy for the client is to verify the server, this means that if you don't load CAs to verify the server you'll get a connect error, no signer error to confirm failure (-188). If you want to mimic OpenSSL behavior of having SSL_connect succeed even if verifying the server fails and reducing security you can do this by calling: wolfSSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, 0); before calling wolfSSL_new(); Though it's not recommended. ``` # wolfSSL (Formerly CyaSSL) Release 3.10.2 (2/10/2017) ## Release 3.10.2 of wolfSSL has bug fixes and new features including: - Poly1305 Windows macros fix. Thanks to GitHub user Jay Satiro - Compatibility layer expanded with multiple functions added - Improve fp_copy performance with ALT_ECC_SIZE - OCSP updates and improvements - Fixes for IAR EWARM 8 compiler warnings - Reduce stack usage with ECC_CACHE_CURVE disabled - Added ECC export raw for public and private key - Fix for NO_ASN_TIME build - Supported curves extensions now populated by default - Add DTLS build without big integer math - Fix for static memory feature with wc_ecc_verify_hash_ex and not SHAMIR - Added PSK interoperability testing to script bundled with wolfSSL - Fix for Python wrapper random number generation. Compiler optimizations with Python could place the random number in same buffer location each time. Thanks to GitHub user Erik Bray (embray) - Fix for tests on unaligned memory with static memory feature - Add macro WOLFSSL_NO_OCSP_OPTIONAL_CERTS to skip optional OCSP certificates - Sanity checks on NULL arguments added to wolfSSL_set_fd and wolfSSL_DTLS_SetCookieSecret - mp_jacobi stack use reduced, thanks to Szabi Tolnai for providing a solution to reduce stack usage This release of wolfSSL fixes 2 low and 1 medium level security vulnerability. Low level fix of buffer overflow for when loading in a malformed temporary DH file. Thanks to Yueh-Hsun Lin and Peng Li from KNOX Security, Samsung Research America for the report. Medium level fix for processing of OCSP response. If using OCSP without hard faults enforced and no alternate revocation checks like OCSP stapling then it is recommended to update. Low level fix for potential cache attack on RSA operations. If using wolfSSL RSA on a server that other users can have access to monitor the cache, then it is recommended to update wolfSSL. Thanks to Andreas Zankl, Johann Heyszl and Georg Sigl at Fraunhofer AISEC for the initial report. See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.10.0 (12/21/2016) ## Release 3.10.0 of wolfSSL has bug fixes and new features including: - Added support for SHA224 - Added scrypt feature - Build for Intel SGX use, added in directory IDE/WIN-SGX - Fix for ChaCha20-Poly1305 ECDSA certificate type request - Enhance PKCS#7 with ECC enveloped data and AES key wrap support - Added support for RIOT OS - Add support for parsing PKCS#12 files - ECC performance increased with custom curves - ARMv8 expanded to AArch32 and performance increased - Added ANSI-X9.63-KDF support - Port to STM32 F2/F4 CubeMX - Port to Atmel ATECC508A board - Removed fPIE by default when wolfSSL library is compiled - Update to Python wrapper, dropping DES and adding wc_RSASetRNG - Added support for NXP K82 hardware acceleration - Added SCR client and server verify check - Added a disable rng option with autoconf - Added more tests vectors to test.c with AES-CTR - Updated DTLS session export version number - Updated DTLS for 64 bit sequence numbers - Fix for memory management with TI and WOLFSSL_SMALL_STACK - Hardening RSA CRT to be constant time - Fix uninitialized warning with IAR compiler - Fix for C# wrapper example IO hang on unexpected connection termination This release of wolfSSL fixes a low level security vulnerability. The vulnerability reported was a potential cache attack on RSA operations. If using wolfSSL RSA on a server that other users can have access to monitor the cache, then it is recommended to update wolfSSL. Thanks to Andreas Zankl, Johann Heyszl and Georg Sigl at Fraunhofer AISEC for the report. More information will be available on our site: https://wolfssl.com/wolfSSL/security/vulnerabilities.php See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.9.10 (9/23/2016) ## Release 3.9.10 of wolfSSL has bug fixes and new features including: - Default configure option changes: 1. DES3 disabled by default 2. ECC Supported Curves Extension enabled by default 3. New option Extended Master Secret enabled by default - Added checking CA certificate path length, and new test certs - Fix to DSA pre padding and sanity check on R/S values - Added CTX level RNG for single-threaded builds - Intel RDSEED enhancements - ARMv8 hardware acceleration support for AES-CBC/CTR/GCM, SHA-256 - Arduino support updates - Added the Extended Master Secret TLS extension 1. Enabled by default in configure options, API to disable 2. Added support for Extended Master Secret to sniffer - OCSP fix with issuer key hash, lookup refactor - Added support for Frosted OS - Added support for DTLS over SCTP - Added support for static memory with wolfCrypt - Fix to ECC Custom Curve support - Support for asynchronous wolfCrypt RSA and TLS client - Added distribution build configure option - Update the test certificates This release of wolfSSL fixes medium level security vulnerabilities. Fixes for potential AES, RSA, and ECC side channel leaks is included that a local user monitoring the same CPU core cache could exploit. VM users, hyper-threading users, and users where potential attackers have access to the CPU cache will need to update if they utilize AES, RSA private keys, or ECC private keys. Thanks to Gorka Irazoqui Apecechea and Xiaofei Guo from Intel Corporation for the report. More information will be available on our site: https://wolfssl.com/wolfSSL/security/vulnerabilities.php See INSTALL file for build instructions. More info can be found on-line at https://wolfssl.com/wolfSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.9.8 (7/29/2016) ##Release 3.9.8 of wolfSSL has bug fixes and new features including: - Add support for custom ECC curves. - Add cipher suite ECDHE-ECDSA-AES128-CCM. - Add compkey enable option. This option is for compressed ECC keys. - Add in the option to use test.h without gettimeofday function using the macro WOLFSSL_USER_CURRTIME. - Add RSA blinding for private key operations. Enable option of harden which is on by default. This negates timing attacks. - Add ECC and TLS support for all SECP, Koblitz and Brainpool curves. - Add helper functions for static memory option to allow getting optimum buffer sizes. - Update DTLS behavior on bad MAC. DTLS silently drops packets with bad MACs now. - Update fp_isprime function from libtom enchancement/cleanup repository. - Update sanity checks on inputs and return values for AES-CMAC. - Update wolfSSL for use with MYSQL v5.6.30. - Update LPCXpresso eclipse project to not include misc.c when not needed. - Fix retransmit of last DTLS flight with timeout notification. The last flight is no longer retransmitted on timeout. - Fixes to some code in math sections for compressed ECC keys. This includes edge cases for buffer size on allocation and adjustments for compressed curves build. The code and full list can be found on github with pull request #456. - Fix function argument mismatch for build with secure renegotiation. - X.509 bug fixes for reading in malformed certificates, reported by researchers at Columbia University - Fix GCC version 6 warning about hard tabs in poly1305.c. This was a warning produced by GCC 6 trying to determine the intent of code. - Fixes for static memory option. Including avoid potential race conditions with counters, decrement handshake counter correctly. - Fix anonymous cipher with Diffie Hellman on the server side. Was an issue of a possible buffer corruption. For information and code see pull request #481. - One high level security fix that requires an update for use with static RSA cipher suites was submitted. This fix was the addition of RSA blinding for private RSA operations. We recommend servers who allow static RSA cipher suites to also generate new private RSA keys. Static RSA cipher suites are turned off by default. See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/wolfSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.9.6 (6/14/2016) ##Release 3.9.6 of wolfSSL has bug fixes and new features including: - Add staticmemory feature - Add public wc_GetTime API with base64encode feature - Add AES CMAC algorithm - Add DTLS sessionexport feature - Add python wolfCrypt wrapper - Add ECC encrypt/decrypt benchmarks - Add dynamic session tickets - Add eccshamir option - Add Whitewood netRandom support --with-wnr - Add embOS port - Add minimum key size checks for RSA and ECC - Add STARTTLS support to examples - Add uTasker port - Add asynchronous crypto and wolf event support - Add compile check for misc.c with inline - Add RNG benchmark - Add reduction to stack usage with hash-based RNG - Update STM32F2_CRYPTO port with additional algorithms supported - Update MDK5 projects - Update AES-NI - Fix for STM32 with STM32F2_HASH defined - Fix for building with MinGw - Fix ECC math bugs with ALT_ECC_SIZE and key sizes over 256 bit (1) - Fix certificate buffers github issue #422 - Fix decrypt max size with RSA OAEP - Fix DTLS sanity check with DTLS timeout notification - Fix free of WOLFSSL_METHOD on failure to create CTX - Fix memory leak in failure case with wc_RsaFunction (2) - No high level security fixes that requires an update though we always recommend updating to the latest - (1) Code changes for ECC fix can be found at pull requests #411, #416, and #428 - (2) Builds using RSA with using normal math and not RSA_LOW_MEM should update See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/wolfSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.9.0 (03/18/2016) ##Release 3.9.0 of wolfSSL has bug fixes and new features including: - Add new leantls configuration - Add RSA OAEP padding at wolfCrypt level - Add Arduino port and example client - Add fixed point DH operation - Add CUSTOM_RAND_GENRATE_SEED_OS and CUSTOM_RAND_GENERATE_BLOCK - Add ECDHE-PSK cipher suites - Add PSK ChaCha20-Poly1305 cipher suites - Add option for fail on no peer cert except PSK suites - Add port for Nordic nRF51 - Add additional ECC NIST test vectors for 256, 384 and 521 - Add more granular ECC, Ed25519/Curve25519 and AES configs - Update to ChaCha20-Poly1305 - Update support for Freescale KSDK 1.3.0 - Update DER buffer handling code, refactoring and reducing memory - Fix to AESNI 192 bit key expansion - Fix to C# wrapper character encoding - Fix sequence number issue with DTLS epoch 0 messages - Fix RNGA with K64 build - Fix ASN.1 X509 V3 certificate policy extension parsing - Fix potential free of uninitialized RSA key in asn.c - Fix potential underflow when using ECC build with FP_ECC - Fixes for warnings in Visual Studio 2015 build - No high level security fixes that requires an update though we always recommend updating to the latest - FP_ECC is off by default, users with it enabled should update for the zero sized hash fix See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.8.0 (12/30/2015) ##Release 3.8.0 of wolfSSL has bug fixes and new features including: - Example client/server with VxWorks - AESNI use with AES-GCM - Stunnel compatibility enhancements - Single shot hash and signature/verify API added - Update cavium nitrox port - LPCXpresso IDE support added - C# wrapper to support wolfSSL use by a C# program - (BETA version)OCSP stapling added - Update OpenSSH compatibility - Improve DTLS handshake when retransmitting finished message - fix idea_mult() for 16 and 32bit systems - fix LowResTimer on Microchip ports - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html # wolfSSL (Formerly CyaSSL) Release 3.7.0 (10/26/2015) ##Release 3.7.0 of wolfSSL has bug fixes and new features including: - ALPN extension support added for HTTP2 connections with --enable-alpn - Change of example/client/client max fragment flag -L -> -F - Throughput benchmarking, added scripts/benchmark.test - Sniffer API ssl_FreeDecodeBuffer added - Addition of AES_GCM to Sniffer - Sniffer change to handle unlimited decrypt buffer size - New option for the sniffer where it will try to pick up decoding after a sequence number acknowldgement fault. Also includes some additional stats. - JNI API setter and getter function for jobject added - User RSA crypto plugin abstraction. An example placed in wolfcrypt/user-crypto - fix to asn configuration bug - AES-GCM/CCM fixes. - Port for Rowley added - Rowley Crossworks bare metal examples added - MDK5-ARM project update - FreeRTOS support updates. - VXWorks support updates. - Added the IDEA cipher and support in wolfSSL. - Update wolfSSL website CA. - CFLAGS is usable when configuring source. - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.6.8 (09/17/2015) ##Release 3.6.8 of wolfSSL fixes two high severity vulnerabilities. ##It also includes bug fixes and new features including: - Two High level security fixes, all users SHOULD update. a) If using wolfSSL for DTLS on the server side of a publicly accessible machine you MUST update. b) If using wolfSSL for TLS on the server side with private RSA keys allowing ephemeral key exchange without low memory optimziations you MUST update and regenerate the private RSA keys. Please see https://www.wolfssl.com/wolfSSL/Blog/Blog.html for more details - No filesystem build fixes for various configurations - Certificate generation now supports several extensions including KeyUsage, SKID, AKID, and Ceritifcate Policies - CRLs can be loaded from buffers as well as files now - SHA-512 Ceritifcate Signing generation - Fixes for sniffer reassembly processing See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.6.6 (08/20/2015) ##Release 3.6.6 of wolfSSL has bug fixes and new features including: - OpenSSH compatibility with --enable-openssh - stunnel compatibility with --enable-stunnel - lighttpd compatibility with --enable-lighty - SSLv3 is now disabled by default, can be enabled with --enable-sslv3 - Ephemeral key cipher suites only are now supported by default To enable static ECDH cipher suites define WOLFSSL_STATIC_DH To enable static RSA cipher suites define WOLFSSL_STATIC_RSA To enable static PSK cipher suites define WOLFSSL_STATIC_PSK - Added QSH (quantum-safe handshake) extension with --enable-ntru - SRP is now part of wolfCrypt, enable with --enabe-srp - Certificate handshake messages can now be sent fragmented if the record size is smaller than the total message size, no user action required. - DTLS duplicate message fixes - Visual Studio project files now support DLL and static builds for 32/64bit. - Support for new Freesacle I/O - FreeRTOS FIPS support - No high level security fixes that requires an update though we always recommend updating to the latest See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.6.0 (06/19/2015) ##Release 3.6.0 of wolfSSL has bug fixes and new features including: - Max Strength build that only allows TLSv1.2, AEAD ciphers, and PFS (Perfect Forward Secrecy). With --enable-maxstrength - Server side session ticket support, the example server and echosever use the example callback myTicketEncCb(), see wolfSSL_CTX_set_TicketEncCb() - FIPS version submitted for iOS. - TI Crypto Hardware Acceleration - DTLS fragmentation fixes - ECC key check validation with wc_ecc_check_key() - 32bit code options to reduce memory for Curve25519 and Ed25519 - wolfSSL JNI build switch with --enable-jni - PicoTCP support improvements - DH min ephemeral key size enforcement with wolfSSL_CTX_SetMinDhKey_Sz() - KEEP_PEER_CERT and AltNames can now be used together - ChaCha20 big endian fix - SHA-512 signature algorithm support for key exchange and verify messages - ECC make key crash fix on RNG failure, ECC users must update. - Improvements to usage of time code. - Improvements to VS solution files. - GNU Binutils 2.24 ld has problems with some debug builds, to fix an ld error add -fdebug-types-section to C_EXTRA_FLAGS - No high level security fixes that requires an update though we always recommend updating to the latest (except note 14, ecc RNG failure) See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.4.8 (04/06/2015) ##Release 3.4.8 of wolfSSL has bug fixes and new features including: - FIPS version submitted for iOS. - Max Strength build that only allows TLSv1.2, AEAD ciphers, and PFS. - Improvements to usage of time code. - Improvements to VS solution files. See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.4.6 (03/30/2015) ##Release 3.4.6 of wolfSSL has bug fixes and new features including: - Intel Assembly Speedups using instructions rdrand, rdseed, aesni, avx1/2, rorx, mulx, adox, adcx . They can be enabled with --enable-intelasm. These speedup the use of RNG, SHA2, and public key algorithms. - Ed25519 support at the crypto level. Turn on with --enable-ed25519. Examples in wolcrypt/test/test.c ed25519_test(). - Post Handshake Memory reductions. wolfSSL can now hold less than 1,000 bytes of memory per secure connection including cipher state. - wolfSSL API and wolfCrypt API fixes, you can still include the cyassl and ctaocrypt headers which will enable the compatibility APIs for the foreseeable future - INSTALL file to help direct users to build instructions for their environment - For ECC users with the normal math library a fix that prevents a crash when verify signature fails. Users of 3.4.0 with ECC and the normal math library must update - RC4 is now disabled by default in autoconf mode - AES-GCM and ChaCha20/Poly1305 are now enabled by default to make AEAD ciphers available without a switch - External ChaCha-Poly AEAD API, thanks to Andrew Burks for the contribution - DHE-PSK cipher suites can now be built without ASN or Cert support - Fix some NO MD5 build issues with optional features - Freescale CodeWarrior project updates - ECC curves can be individually turned on/off at build time. - Sniffer handles Cert Status message and other minor fixes - SetMinVersion() at the wolfSSL Context level instead of just SSL session level to allow minimum protocol version allowed at runtime - RNG failure resource cleanup fix - No high level security fixes that requires an update though we always recommend updating to the latest (except note 6 use case of ecc/normal math) See INSTALL file for build instructions. More info can be found on-line at //http://wolfssl.com/yaSSL/Docs.html #wolfSSL (Formerly CyaSSL) Release 3.4.0 (02/23/2015) ## Release 3.4.0 wolfSSL has bug fixes and new features including: - wolfSSL API and wolfCrypt API, you can still include the cyassl and ctaocrypt headers which will enable the compatibility APIs for the foreseeable future - Example use of the wolfCrypt API can be found in wolfcrypt/test/test.c - Example use of the wolfSSL API can be found in examples/client/client.c - Curve25519 now supported at the wolfCrypt level, wolfSSL layer coming soon - Improvements in the build configuration under AIX - Microchip Pic32 MZ updates - TIRTOS updates - PowerPC updates - Xcode project update - Bidirectional shutdown examples in client/server with -w (wait for full shutdown) option - Cycle counts on benchmarks for x86_64, more coming soon - ALT_ECC_SIZE for reducing ecc heap use with fastmath when also using large RSA keys - Various compile warnings - Scan-build warning fixes - Changed a memcpy to memmove in the sniffer (if using sniffer please update) - No high level security fixes that requires an update though we always recommend updating to the latest # CyaSSL Release 3.3.0 (12/05/2014) - Countermeasuers for Handshake message duplicates, CHANGE CIPHER without FINISHED, and fast forward attempts. Thanks to Karthikeyan Bhargavan from the Prosecco team at INRIA Paris-Rocquencourt for the report. - FIPS version submitted - Removes SSLv2 Client Hello processing, can be enabled with OLD_HELLO_ALLOWED - User can set mimimum downgrade version with CyaSSL_SetMinVersion() - Small stack improvements at TLS/SSL layer - TLS Master Secret generation and Key Expansion are now exposed - Adds client side Secure Renegotiation, * not recommended * - Client side session ticket support, not fully tested with Secure Renegotiation - Allows up to 4096bit DHE at TLS Key Exchange layer - Handles non standard SessionID sizes in Hello Messages - PicoTCP Support - Sniffer now supports SNI Virtual Hosts - Sniffer now handles non HTTPS protocols using STARTTLS - Sniffer can now parse records with multiple messages - TI-RTOS updates - Fix for ColdFire optimized fp_digit read only in explicit 32bit case - ADH Cipher Suite ADH-AES128-SHA for EAP-FAST The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 3.2.0 (09/10/2014) #### Release 3.2.0 CyaSSL has bug fixes and new features including: - ChaCha20 and Poly1305 crypto and suites - Small stack improvements for OCSP, CRL, TLS, DTLS - NTRU Encrypt and Decrypt benchmarks - Updated Visual Studio project files - Updated Keil MDK5 project files - Fix for DTLS sequence numbers with GCM/CCM - Updated HashDRBG with more secure struct declaration - TI-RTOS support and example Code Composer Studio project files - Ability to get enabled cipher suites, CyaSSL_get_ciphers() - AES-GCM/CCM/Direct support for Freescale mmCAU and CAU - Sniffer improvement checking for decrypt key setup - Support for raw ECC key import - Ability to convert ecc_key to DER, EccKeyToDer() - Security fix for RSA Padding check vulnerability reported by Intel Security Advanced Threat Research team The CyaSSL manual is available at: http://www.wolfssl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 3.1.0 (07/14/2014) #### Release 3.1.0 CyaSSL has bug fixes and new features including: - Fix for older versions of icc without 128-bit type - Intel ASM syntax for AES-NI - Updated NTRU support, keygen benchmark - FIPS check for minimum required HMAC key length - Small stack (--enable-smallstack) improvements for PKCS#7, ASN - TLS extension support for DTLS - Default I/O callbacks external to user - Updated example client with bad clock test - Ability to set optional ECC context info - Ability to enable/disable DH separate from opensslextra - Additional test key/cert buffers for CA and server - Updated example certificates The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 3.0.2 (05/30/2014) #### Release 3.0.2 CyaSSL has bug fixes and new features including: - Added the following cipher suites: * TLS_PSK_WITH_AES_128_GCM_SHA256 * TLS_PSK_WITH_AES_256_GCM_SHA384 * TLS_PSK_WITH_AES_256_CBC_SHA384 * TLS_PSK_WITH_NULL_SHA384 * TLS_DHE_PSK_WITH_AES_128_GCM_SHA256 * TLS_DHE_PSK_WITH_AES_256_GCM_SHA384 * TLS_DHE_PSK_WITH_AES_128_CBC_SHA256 * TLS_DHE_PSK_WITH_AES_256_CBC_SHA384 * TLS_DHE_PSK_WITH_NULL_SHA256 * TLS_DHE_PSK_WITH_NULL_SHA384 * TLS_DHE_PSK_WITH_AES_128_CCM * TLS_DHE_PSK_WITH_AES_256_CCM - Added AES-NI support for Microsoft Visual Studio builds. - Changed small stack build to be disabled by default. - Updated the Hash DRBG and provided a configure option to enable. The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 3.0.0 (04/29/2014) #### Release 3.0.0 CyaSSL has bug fixes and new features including: - FIPS release candidate - X.509 improvements that address items reported by Suman Jana with security researchers at UT Austin and UC Davis - Small stack size improvements, --enable-smallstack. Offloads large local variables to the heap. (Note this is not complete.) - Updated AES-CCM-8 cipher suites to use approved suite numbers. The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.9.4 (04/09/2014) #### Release 2.9.4 CyaSSL has bug fixes and new features including: - Security fixes that address items reported by Ivan Fratric of the Google Security Team - X.509 Unknown critical extensions treated as errors, report by Suman Jana with security researchers at UT Austin and UC Davis - Sniffer fixes for corrupted packet length and Jumbo frames - ARM thumb mode assembly fixes - Xcode 5.1 support including new clang - PIC32 MZ hardware support - CyaSSL Object has enough room to read the Record Header now w/o allocs - FIPS wrappers for AES, 3DES, SHA1, SHA256, SHA384, HMAC, and RSA. - A sample I/O pool is demonstrated with --enable-iopool to overtake memory handling and reduce memory fragmentation on I/O large sizes The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.9.0 (02/07/2014) #### Release 2.9.0 CyaSSL has bug fixes and new features including: - Freescale Kinetis RNGB support - Freescale Kinetis mmCAU support - TLS Hello extensions - ECC - Secure Renegotiation (null) - Truncated HMAC - SCEP support - PKCS #7 Enveloped data and signed data - PKCS #10 Certificate Signing Request generation - DTLS sliding window - OCSP Improvements - API change to integrate into Certificate Manager - IPv4/IPv6 agnostic - example client/server support for OCSP - OCSP nonces are optional - GMAC hashing - Windows build additions - Windows CYGWIN build fixes - Updated test certificates - Microchip MPLAB Harmony support - Update autoconf scripts - Additional X.509 inspection functions - ECC encrypt/decrypt primitives - ECC Certificate generation The Freescale Kinetis K53 RNGB documentation can be found in Chapter 33 of the K53 Sub-Family Reference Manual: http://cache.freescale.com/files/32bit/doc/ref_manual/K53P144M100SF2RM.pdf Freescale Kinetis K60 mmCAU (AES, DES, 3DES, MD5, SHA, SHA256) documentation can be found in the "ColdFire/ColdFire+ CAU and Kinetis mmCAU Software Library User Guide": http://cache.freescale.com/files/32bit/doc/user_guide/CAUAPIUG.pdf # CyaSSL Release 2.8.0 (8/30/2013) #### Release 2.8.0 CyaSSL has bug fixes and new features including: - AES-GCM and AES-CCM use AES-NI - NetX default IO callback handlers - IPv6 fixes for DTLS Hello Cookies - The ability to unload Certs/Keys after the handshake, CyaSSL_UnloadCertsKeys() - SEP certificate extensions - Callback getters for easier resource freeing - External CYASSL_MAX_ERROR_SZ for correct error buffer sizing - MacEncrypt and DecryptVerify Callbacks for User Atomic Record Layer Processing - Public Key Callbacks for ECC and RSA - Client now sends blank cert upon request if doesn't have one with TLS <= 1.2 The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.7.0 (6/17/2013) #### Release 2.7.0 CyaSSL has bug fixes and new features including: - SNI support for client and server - KEIL MDK-ARM projects - Wildcard check to domain name match, and Subject altnames are checked too - Better error messages for certificate verification errors - Ability to discard session during handshake verify - More consistent error returns across all APIs - Ability to unload CAs at the CTX or CertManager level - Authority subject id support for Certificate matching - Persistent session cache functionality - Persistent CA cache functionality - Client session table lookups to push serverID table to library level - Camellia support to sniffer - User controllable settings for DTLS timeout values - Sniffer fixes for caching long lived sessions - DTLS reliability enhancements for the handshake - Better ThreadX support When compiling with Mingw, libtool may give the following warning due to path conversion errors: ``` libtool: link: Could not determine host file name corresponding to ** libtool: link: Continuing, but uninstalled executables may not work. ``` If so, examples and testsuite will have problems when run, showing an error while loading shared libraries. To resolve, please run "make install". The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.6.0 (04/15/2013) #### Release 2.6.0 CyaSSL has bug fixes and new features including: - DTLS 1.2 support including AEAD ciphers - SHA-3 finalist Blake2 support, it's fast and uses little resources - SHA-384 cipher suites including ECC ones - HMAC now supports SHA-512 - Track memory use for example client/server with -t option - Better IPv6 examples with --enable-ipv6, before if ipv6 examples/tests were turned on, localhost only was used. Now link-local (with scope ids) and ipv6 hosts can be used as well. - Xcode v4.6 project for iOS v6.1 update - settings.h is now checked in all *.c files for true one file setting detection - Better alignment at SSL layer for hardware crypto alignment needs * Note, SSL itself isn't friendly to alignment with 5 byte TLS headers and 13 bytes DTLS headers, but every effort is now made to align with the CYASSL_GENERAL_ALIGNMENT flag which sets desired alignment requirement - NO_64BIT flag to turn off 64bit data type accumulators in public key code * Note, some systems are faster with 32bit accumulators - --enable-stacksize for example client/server stack use * Note, modern desktop Operating Systems may add bytes to each stack frame - Updated compression/decompression with direct crypto access - All ./configure options are now lowercase only for consistency - ./configure builds default to fastmath option * Note, if on ia32 and building in shared mode this may produce a problem with a missing register being available because of PIC, there are at least 6 solutions to this: 1) --disable-fastmath , don't use fastmath 2) --disable-shared, don't build a shared library 3) C_EXTRA_FLAGS=-DTFM_NO_ASM , turn off assembly use 4) use clang, it just seems to work 5) play around with no PIC options to force all registers being open, e.g., --without-pic 6) if static lib is still a problem try removing fPIE - Many new ./configure switches for option enable/disable for example * rsa * dh * dsa * md5 * sha * arc4 * null (allow NULL ciphers) * oldtls (only use TLS 1.2) * asn (no certs or public keys allowed) - ./configure generates cyassl/options.h which allows a header the user can include in their app to make sure the same options are set at the app and CyaSSL level. - autoconf no longer needs serial-tests which lowers version requirements of automake to 1.11 and autoconf to 2.63 The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.5.0 (02/04/2013) #### Release 2.5.0 CyaSSL has bug fixes and new features including: - Fix for TLS CBC padding timing attack identified by Nadhem Alfardan and Kenny Paterson: http://www.isg.rhul.ac.uk/tls/ - Microchip PIC32 (MIPS16, MIPS32) support - Microchip MPLAB X example projects for PIC32 Ethernet Starter Kit - Updated CTaoCrypt benchmark app for embedded systems - 1024-bit test certs/keys and cert/key buffers - AES-CCM-8 crypto and cipher suites - Camellia crypto and cipher suites - Bumped minimum autoconf version to 2.65, automake version to 1.12 - Addition of OCSP callbacks - STM32F2 support with hardware crypto and RNG - Cavium NITROX support CTaoCrypt now has support for the Microchip PIC32 and has been tested with the Microchip PIC32 Ethernet Starter Kit, the XC32 compiler and MPLAB X IDE in both MIPS16 and MIPS32 instruction set modes. See the README located under the /mplabx directory for more details. To add Cavium NITROX support do: ./configure --with-cavium=/home/user/cavium/software pointing to your licensed cavium/software directory. Since Cavium doesn't build a library we pull in the cavium_common.o file which gives a libtool warning about the portability of this. Also, if you're using the github source tree you'll need to remove the -Wredundant-decls warning from the generated Makefile because the cavium headers don't conform to this warning. Currently CyaSSL supports Cavium RNG, AES, 3DES, RC4, HMAC, and RSA directly at the crypto layer. Support at the SSL level is partial and currently just does AES, 3DES, and RC4. RSA and HMAC are slower until the Cavium calls can be utilized in non blocking mode. The example client turns on cavium support as does the crypto test and benchmark. Please see the HAVE_CAVIUM define. CyaSSL is able to use the STM32F2 hardware-based cryptography and random number generator through the STM32F2 Standard Peripheral Library. For necessary defines, see the CYASSL_STM32F2 define in settings.h. Documentation for the STM32F2 Standard Peripheral Library can be found in the following document: http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/USER_MANUAL/DM00023896.pdf The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.4.6 (12/20/2012) #### Release 2.4.6 CyaSSL has bug fixes and a few new features including: - ECC into main version - Lean PSK build (reduced code size, RAM usage, and stack usage) - FreeBSD CRL monitor support - CyaSSL_peek() - CyaSSL_send() and CyaSSL_recv() for I/O flag setting - CodeWarrior Support - MQX Support - Freescale Kinetis support including Hardware RNG - autoconf builds use jobserver - cyassl-config - Sniffer memory reductions Thanks to Brian Aker for the improved autoconf system, make rpm, cyassl-config, warning system, and general good ideas for improving CyaSSL! The Freescale Kinetis K70 RNGA documentation can be found in Chapter 37 of the K70 Sub-Family Reference Manual: http://cache.freescale.com/files/microcontrollers/doc/ref_manual/K70P256M150SF3RM.pdf The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.4.0 (10/10/2012) #### Release 2.4.0 CyaSSL has bug fixes and a few new features including: - DTLS reliability - Reduced memory usage after handshake - Updated build process The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.3.0 (8/10/2012) #### Release 2.3.0 CyaSSL has bug fixes and a few new features including: - AES-GCM crypto and cipher suites - make test cipher suite checks - Subject AltName processing - Command line support for client/server examples - Sniffer SessionTicket support - SHA-384 cipher suites - Verify cipher suite validity when user overrides - CRL dir monitoring - DTLS Cookie support, reliability coming soon The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.2.0 (5/18/2012) #### Release 2.2.0 CyaSSL has bug fixes and a few new features including: - Initial CRL support (--enable-crl) - Initial OCSP support (--enable-ocsp) - Add static ECDH suites - SHA-384 support - ECC client certificate support - Add medium session cache size (1055 sessions) - Updated unit tests - Protection against mutex reinitialization The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.8 (2/24/2012) #### Release 2.0.8 CyaSSL has bug fixes and a few new features including: - A fix for malicious certificates pointed out by Remi Gacogne (thanks) resulting in NULL pointer use. - Respond to renegotiation attempt with no_renegoatation alert - Add basic path support for load_verify_locations() - Add set Temp EC-DHE key size - Extra checks on rsa test when porting into The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.6 (1/27/2012) #### Release 2.0.6 CyaSSL has bug fixes and a few new features including: - Fixes for CA basis constraint check - CTX reference counting - Initial unit test additions - Lean and Mean Windows fix - ECC benchmarking - SSMTP build support - Ability to group handshake messages with set_group_messages(ctx/ssl) - CA cache addition callback - Export Base64_Encode for general use The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.2 (12/05/2011) #### Release 2.0.2 CyaSSL has bug fixes and a few new features including: - CTaoCrypt Runtime library detection settings when directly using the crypto library - Default certificate generation now uses SHAwRSA and adds SHA256wRSA generation - All test certificates now use 2048bit and SHA-1 for better modern browser support - Direct AES block access and AES-CTR (counter) mode - Microchip pic32 support The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.0rc3 (9/28/2011) #### Release 2.0.0rc3 for CyaSSL has bug fixes and a few new features including: - updated autoconf support - better make install and uninstall (uses system directories) - make test / make check - CyaSSL headers now in - CTaocrypt headers now in - OpenSSL compatibility headers now in - examples and tests all run from home directory so can use certs in ./certs (see note 1) So previous applications that used the OpenSSL compatibility header now need to include instead, no other changes are required. Special Thanks to Brian Aker for his autoconf, install, and header patches. The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.0rc2 (6/6/2011) #### Release 2.0.0rc2 for CyaSSL has bug fixes and a few new features including: - bug fixes (Alerts, DTLS with DHE) - FreeRTOS support - lwIP support - Wshadow warnings removed - asn public header - CTaoCrypt public headers now all have ctc_ prefix (the manual is still being updated to reflect this change) - and more. This is the 2nd and perhaps final release candidate for version 2. Please send any comments or questions to support@yassl.com. The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 2.0.0rc1 (5/2/2011) #### Release 2.0.0rc1 for CyaSSL has many new features including: - bug fixes - SHA-256 cipher suites - Root Certificate Verification (instead of needing all certs in the chain) - PKCS #8 private key encryption (supports PKCS #5 v1-v2 and PKCS #12) - Serial number retrieval for x509 - PBKDF2 and PKCS #12 PBKDF - UID parsing for x509 - SHA-256 certificate signatures - Client and server can send chains (SSL_CTX_use_certificate_chain_file) - CA loading can now parse multiple certificates per file - Dynamic memory runtime hooks - Runtime hooks for logging - EDH on server side - More informative error codes - More informative logging messages - Version downgrade more robust (use SSL_v23*) - Shared build only by default through ./configure - Compiler visibility is now used, internal functions not polluting namespace - Single Makefile, no recursion, for faster and simpler building - Turn on all warnings possible build option, warning fixes - and more. Because of all the new features and the multiple OS, compiler, feature-set options that CyaSSL allows, there may be some configuration fixes needed. Please send any comments or questions to support@yassl.com. The CyaSSL manual is available at: http://www.yassl.com/documentation/CyaSSL-Manual.pdf. For build instructions and comments about the new features please check the manual. # CyaSSL Release 1.9.0 (3/2/2011) Release 1.9.0 for CyaSSL adds bug fixes, improved TLSv1.2 through testing and better hash/sig algo ids, --enable-webServer for the yaSSL embedded web server, improper AES key setup detection, user cert verify callback improvements, and more. The CyaSSL manual offering is included in the doc/ directory. For build instructions and comments about the new features please check the manual. Please send any comments or questions to support@yassl.com. # CyaSSL Release 1.8.0 (12/23/2010) Release 1.8.0 for CyaSSL adds bug fixes, x509 v3 CA signed certificate generation, a C standard library abstraction layer, lower memory use, increased portability through the os_settings.h file, and the ability to use NTRU cipher suites when used in conjunction with an NTRU license and library. The initial CyaSSL manual offering is included in the doc/ directory. For build instructions and comments about the new features please check the manual. Please send any comments or questions to support@yassl.com. Happy Holidays. # CyaSSL Release 1.6.5 (9/9/2010) Release 1.6.5 for CyaSSL adds bug fixes and x509 v3 self signed certificate generation. For general build instructions see doc/Building_CyaSSL.pdf. To enable certificate generation support add this option to ./configure ./configure --enable-certgen An example is included in ctaocrypt/test/test.c and documentation is provided in doc/CyaSSL_Extensions_Reference.pdf item 11. # CyaSSL Release 1.6.0 (8/27/2010) Release 1.6.0 for CyaSSL adds bug fixes, RIPEMD-160, SHA-512, and RSA key generation. For general build instructions see doc/Building_CyaSSL.pdf. To add RIPEMD-160 support add this option to ./configure ./configure --enable-ripemd To add SHA-512 support add this option to ./configure ./configure --enable-sha512 To add RSA key generation support add this option to ./configure ./configure --enable-keygen Please see ctaocrypt/test/test.c for examples and usage. For Windows, RIPEMD-160 and SHA-512 are enabled by default but key generation is off by default. To turn key generation on add the define CYASSL_KEY_GEN to CyaSSL. # CyaSSL Release 1.5.6 (7/28/2010) Release 1.5.6 for CyaSSL adds bug fixes, compatibility for our JSSE provider, and a fix for GCC builds on some systems. For general build instructions see doc/Building_CyaSSL.pdf. To add AES-NI support add this option to ./configure ./configure --enable-aesni You'll need GCC 4.4.3 or later to make use of the assembly. # CyaSSL Release 1.5.4 (7/7/2010) Release 1.5.4 for CyaSSL adds bug fixes, support for AES-NI, SHA1 speed improvements from loop unrolling, and support for the Mongoose Web Server. For general build instructions see doc/Building_CyaSSL.pdf. To add AES-NI support add this option to ./configure ./configure --enable-aesni You'll need GCC 4.4.3 or later to make use of the assembly. # CyaSSL Release 1.5.0 (5/11/2010) Release 1.5.0 for CyaSSL adds bug fixes, GoAhead WebServer support, sniffer support, and initial swig interface support. For general build instructions see doc/Building_CyaSSL.pdf. To add support for GoAhead WebServer either --enable-opensslExtra or if you don't want all the features of opensslExtra you can just define GOAHEAD_WS instead. GOAHEAD_WS can be added to ./configure with CFLAGS=-DGOAHEAD_WS or you can define it yourself. To look at the sniffer support please see the sniffertest app in sslSniffer/sslSnifferTest. Build with --enable-sniffer on *nix or use the vcproj files on windows. You'll need to have pcap installed on *nix and WinPcap on windows. A swig interface file is now located in the swig directory for using Python, Java, Perl, and others with CyaSSL. This is initial support and experimental, please send questions or comments to support@yassl.com. When doing load testing with CyaSSL, on the echoserver example say, the client machine may run out of tcp ephemeral ports, they will end up in the TIME_WAIT queue, and can't be reused by default. There are generally two ways to fix this. 1. Reduce the length sockets remain on the TIME_WAIT queue OR 2. Allow items on the TIME_WAIT queue to be reused. To reduce the TIME_WAIT length in OS X to 3 seconds (3000 milliseconds) `sudo sysctl -w net.inet.tcp.msl=3000` In Linux `sudo sysctl -w net.ipv4.tcp_tw_reuse=1` allows reuse of sockets in TIME_WAIT `sudo sysctl -w net.ipv4.tcp_tw_recycle=1` works but seems to remove sockets from TIME_WAIT entirely? `sudo sysctl -w net.ipv4.tcp_fin_timeout=1` doen't control TIME_WAIT, it controls FIN_WAIT(2) contrary to some posts # CyaSSL Release 1.4.0 (2/18/2010) Release 1.3.0 for CyaSSL adds bug fixes, better multi TLS/SSL version support through SSLv23_server_method(), and improved documentation in the doc/ folder. For general build instructions doc/Building_CyaSSL.pdf. # CyaSSL Release 1.3.0 (1/21/2010) Release 1.3.0 for CyaSSL adds bug fixes, a potential security problem fix, better porting support, removal of assert()s, and a complete THREADX port. For general build instructions see rc1 below. # CyaSSL Release 1.2.0 (11/2/2009) Release 1.2.0 for CyaSSL adds bug fixes and session negotiation if first use is read or write. For general build instructions see rc1 below. # CyaSSL Release 1.1.0 (9/2/2009) Release 1.1.0 for CyaSSL adds bug fixes, a check against malicious session cache use, support for lighttpd, and TLS 1.2. To get TLS 1.2 support please use the client and server functions: ```c SSL_METHOD *TLSv1_2_server_method(void); SSL_METHOD *TLSv1_2_client_method(void); ``` CyaSSL was tested against lighttpd 1.4.23. To build CyaSSL for use with lighttpd use the following commands from the CyaSSL install dir : ``` ./configure --disable-shared --enable-opensslExtra --enable-fastmath --without-zlib make make openssl-links ``` Then to build lighttpd with CyaSSL use the following commands from the lighttpd install dir: ``` ./configure --with-openssl --with-openssl-includes=/include --with-openssl-libs=/lib LDFLAGS=-lm make ``` On some systems you may get a linker error about a duplicate symbol for MD5_Init or other MD5 calls. This seems to be caused by the lighttpd src file md5.c, which defines MD5_Init(), and is included in liblightcomp_la-md5.o. When liblightcomp is linked with the SSL_LIBs the linker may complain about the duplicate symbol. This can be fixed by editing the lighttpd src file md5.c and adding this line to the beginning of the file: \#if 0 and this line to the end of the file \#endif Then from the lighttpd src dir do a: ``` make clean make ``` If you get link errors about undefined symbols more than likely the actual OpenSSL libraries are found by the linker before the CyaSSL openssl-links that point to the CyaSSL library, causing the linker confusion. This can be fixed by editing the Makefile in the lighttpd src directory and changing the line: `SSL_LIB = -lssl -lcrypto` to `SSL_LIB = -lcyassl` Then from the lighttpd src dir do a: ``` make clean make ``` This should remove any confusion the linker may be having with missing symbols. For any questions or concerns please contact support@yassl.com . For general build instructions see rc1 below. # CyaSSL Release 1.0.6 (8/03/2009) Release 1.0.6 for CyaSSL adds bug fixes, an improved session cache, and faster math with a huge code option. The session cache now defaults to a client mode, also good for embedded servers. For servers not under heavy load (less than 200 new sessions per minute), define BIG_SESSION_CACHE. If the server will be under heavy load, define HUGE_SESSION_CACHE. There is now a fasthugemath option for configure. This enables fastmath plus even faster math by greatly increasing the code size of the math library. Use the benchmark utility to compare public key operations. For general build instructions see rc1 below. # CyaSSL Release 1.0.3 (5/10/2009) Release 1.0.3 for CyaSSL adds bug fixes and add increased support for OpenSSL compatibility when building other applications. Release 1.0.3 includes an alpha release of DTLS for both client and servers. This is only for testing purposes at this time. Rebroadcast and reordering aren't fully implemented at this time but will be for the next release. For general build instructions see rc1 below. # CyaSSL Release 1.0.2 (4/3/2009) Release 1.0.2 for CyaSSL adds bug fixes for a couple I/O issues. Some systems will send a SIGPIPE on socket recv() at any time and this should be handled by the application by turning off SIGPIPE through setsockopt() or returning from the handler. Release 1.0.2 includes an alpha release of DTLS for both client and servers. This is only for testing purposes at this time. Rebroadcast and reordering aren't fully implemented at this time but will be for the next release. For general build instructions see rc1 below. ## CyaSSL Release Candidate 3 rc3-1.0.0 (2/25/2009) Release Candidate 3 for CyaSSL 1.0.0 adds bug fixes and adds a project file for iPhone development with Xcode. cyassl-iphone.xcodeproj is located in the root directory. This release also includes a fix for supporting other implementations that bundle multiple messages at the record layer, this was lost when cyassl i/o was re-implemented but is now fixed. For general build instructions see rc1 below. ## CyaSSL Release Candidate 2 rc2-1.0.0 (1/21/2009) Release Candidate 2 for CyaSSL 1.0.0 adds bug fixes and adds two new stream ciphers along with their respective cipher suites. CyaSSL adds support for HC-128 and RABBIT stream ciphers. The new suites are: ``` TLS_RSA_WITH_HC_128_SHA TLS_RSA_WITH_RABBIT_SHA ``` And the corresponding cipher names are ``` HC128-SHA RABBIT-SHA ``` CyaSSL also adds support for building with devkitPro for PPC by changing the library proper to use libogc. The examples haven't been changed yet but if there's interest they can be. Here's an example ./configure to build CyaSSL for devkitPro: ``` ./configure --disable-shared CC=/pathTo/devkitpro/devkitPPC/bin/powerpc-gekko-gcc --host=ppc --without-zlib --enable-singleThreaded RANLIB=/pathTo/devkitpro/devkitPPC/bin/powerpc-gekko-ranlib CFLAGS="-DDEVKITPRO -DGEKKO" ``` For linking purposes you'll need `LDFLAGS="-g -mrvl -mcpu=750 -meabi -mhard-float -Wl,-Map,$(notdir $@).map"` For general build instructions see rc1 below. ## CyaSSL Release Candidate 1 rc1-1.0.0 (12/17/2008) Release Candidate 1 for CyaSSL 1.0.0 contains major internal changes. Several areas have optimization improvements, less dynamic memory use, and the I/O strategy has been refactored to allow alternate I/O handling or Library use. Many thanks to Thierry Fournier for providing these ideas and most of the work. Because of these changes, this release is only a candidate since some problems are probably inevitable on some platform with some I/O use. Please report any problems and we'll try to resolve them as soon as possible. You can contact us at support@yassl.com or todd@yassl.com. Using TomsFastMath by passing --enable-fastmath to ./configure now uses assembly on some platforms. This is new so please report any problems as every compiler, mode, OS combination hasn't been tested. On ia32 all of the registers need to be available so be sure to pass these options to CFLAGS: `CFLAGS="-O3 -fomit-frame-pointer"` OS X will also need -mdynamic-no-pic added to CFLAGS Also if you're building in shared mode for ia32 you'll need to pass options to LDFLAGS as well on OS X: `LDFLAGS=-Wl,-read_only_relocs,warning` This gives warnings for some symbols but seems to work. #### To build on Linux, Solaris, *BSD, Mac OS X, or Cygwin: ./configure make from the ./testsuite/ directory run ./testsuite #### To make a debug build: ./configure --enable-debug --disable-shared make #### To build on Win32 Choose (Re)Build All from the project workspace Run the testsuite program # CyaSSL version 0.9.9 (7/25/2008) This release of CyaSSL adds bug fixes, Pre-Shared Keys, over-rideable memory handling, and optionally TomsFastMath. Thanks to Moisés Guimarães for the work on TomsFastMath. To optionally use TomsFastMath pass --enable-fastmath to ./configure Or define USE_FAST_MATH in each project from CyaSSL for MSVC. Please use the benchmark routine before and after to see the performance difference, on some platforms the gains will be little but RSA encryption always seems to be faster. On x86-64 machines with GCC the normal math library may outperform the fast one when using CFLAGS=-m64 because TomsFastMath can't yet use -m64 because of GCCs inability to do 128bit division. *** UPDATE GCC 4.2.1 can now do 128bit division *** See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.9.8 (5/7/2008) This release of CyaSSL adds bug fixes, client side Diffie-Hellman, and better socket handling. See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.9.6 (1/31/2008) This release of CyaSSL adds bug fixes, increased session management, and a fix for gnutls. See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.9.0 (10/15/2007) This release of CyaSSL adds bug fixes, MSVC 2005 support, GCC 4.2 support, IPV6 support and test, and new test certificates. See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.8.0 (1/10/2007) This release of CyaSSL adds increased socket support, for non-blocking writes, connects, and interrupted system calls. See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.6.3 (10/30/2006) This release of CyaSSL adds debug logging to stderr to aid in the debugging of CyaSSL on systems that may not provide the best support. If CyaSSL is built with debugging support then you need to call CyaSSL_Debugging_ON() to turn logging on. On Unix use ./configure --enable-debug On Windows define DEBUG_CYASSL when building CyaSSL To turn logging back off call CyaSSL_Debugging_OFF() See notes below (0.2.0) for complete build instructions. # CyaSSL version 0.6.2 (10/29/2006) This release of CyaSSL adds TLS 1.1. Note that CyaSSL has certificate verification on by default, unlike OpenSSL. To emulate OpenSSL behavior, you must call SSL_CTX_set_verify() with SSL_VERIFY_NONE. In order to have full security you should never do this, provide CyaSSL with the proper certificates to eliminate impostors and call CyaSSL_check_domain_name() to prevent man in the middle attacks. See notes below (0.2.0) for build instructions. # CyaSSL version 0.6.0 (10/25/2006) This release of CyaSSL adds more SSL functions, better autoconf, nonblocking I/O for accept, connect, and read. There is now an --enable-small configure option that turns off TLS, AES, DES3, HMAC, and ERROR_STRINGS, see configure.in for the defines. Note that TLS requires HMAC and AES requires TLS. See notes below (0.2.0) for build instructions. # CyaSSL version 0.5.5 (09/27/2006) This mini release of CyaSSL adds better input processing through buffered input and big message support. Added SSL_pending() and some sanity checks on user settings. See notes below (0.2.0) for build instructions. # CyaSSL version 0.5.0 (03/27/2006) This release of CyaSSL adds AES support and minor bug fixes. See notes below (0.2.0) for build instructions. # CyaSSL version 0.4.0 (03/15/2006) This release of CyaSSL adds TLSv1 client/server support and libtool. See notes below for build instructions. # CyaSSL version 0.3.0 (02/26/2006) This release of CyaSSL adds SSLv3 server support and session resumption. See notes below for build instructions. # CyaSSL version 0.2.0 (02/19/2006) This is the first release of CyaSSL and its crypt brother, CTaoCrypt. CyaSSL is written in ANSI C with the idea of a small code size, footprint, and memory usage in mind. CTaoCrypt can be as small as 32K, and the current client version of CyaSSL can be as small as 12K. The first release of CTaoCrypt supports MD5, SHA-1, 3DES, ARC4, Big Integer Support, RSA, ASN parsing, and basic x509 (en/de)coding. The first release of CyaSSL supports normal client RSA mode SSLv3 connections with support for SHA-1 and MD5 digests. Ciphers include 3DES and RC4. #### To build on Linux, Solaris, *BSD, Mac OS X, or Cygwin: ./configure make from the ./testsuite/ directory run ./testsuite #### to make a debug build: ./configure --enable-debug --disable-shared make #### To build on Win32 Choose (Re)Build All from the project workspace Run the testsuite program *** The next release of CyaSSL will support a server and more OpenSSL compatibility functions. Please send questions or comments to todd@wolfssl.com wolfssl-3.10.2-stable/SCRIPTS-LIST000066400000000000000000000033271305024512300163610ustar00rootroot00000000000000autogen.sh - creates ./configure from source checkout, sets up git hooks pre-commit.sh - our pre commit hook, saves current state before running commit tests to allow a resotre back to current state commit-tests.sh - our commit tests, must pass before a commit is accepted, use -n (--no-verify) to disable fips-check.sh - checks if current wolfSSL version works against FIPS wolfCrypt comment out last line to leave working directory gencertbuf.pl - creates certs_test.h, our certs / keys C array for easy non filesystem testing pull_to_vagrant.sh - synchronize to a vm without using git certs/ renewcerts.sh - renews test certs and crls crl/ gencrls.sh - generates crls, used by renewcerts.sh ocsp/ renewcerts.sh - renews ocsp certs ocspd0.sh - ocsp responder for root-ca-cert.pem ocspd1.sh - ocsp responder for intermediate1-ca-cert.pem ocspd2.sh - ocsp responder for intermediate2-ca-cert.pem test-pathlen/ assemble-chains.sh - composes the cert chain files out of the certs scripts/ external.test - example client test against our website, part of tests google.test - example client test against google, part of tests resume.test - example sessoin resume test, part of tests ocsp-stapling.test - example client test against globalsign, part of tests ocsp-stapling2.test - example client test against example server, part of tests sniffer-testsuite.test - runs snifftest on a pcap of testsuite, part of tests in sniffer mode swig/ PythonBuild.sh - builds and runs simple python example valgrind-error.sh - deprecated, was used to detect valgrind errors before automake switched to concurrent tests wolfssl-3.10.2-stable/Vagrantfile000066400000000000000000000022511305024512300167160ustar00rootroot00000000000000# -*- mode: ruby -*- # vi: set ft=ruby : $setup = <