RSSAminetKontakt

aminet/util/libs/AmiSSL-4.2.readme

short : OpenSSL as an Amiga shared library author : AmiSSL Open Source Team uploader : Jens Maus type : util/libs version : 4.2 replaces : util/libs/AmiSSL-* requires : AmigaOS 4.0/PPC, AmigaOS 3.0+/68020+ architecture : ppc-amigaos >= 4.0.5, m68k-amigaos >= 3.0, ppc-morphos >= 1.4.5 url : https://github.com/jens-maus/amissl Filetype : application/x-lzh-compressed Size : 5.50M Date : 7-Mar-18 Download : 💾 https://de3.aminet.net/util/libs/AmiSSL-4.2.lha
This is version 4.2 of the AmiSSL library for Amiga based operating systems and the first public open-source based release of AmiSSL. Version 4.x is a new major release which comes with full compatibility to the OpenSSL 1.1.x line which includes important security related fixes and comes with new encryption ciphers which are required nowadays to connect to modern SSL-based services (e.g. HTTPS). However, due to fundamental changes in the API between the old AmiSSLv3 and new v4 versions and the large changes between the old OpenSSL 0.9.x and the new OpenSSL 1.1.x line applications have to be recompiled with the updated AmiSSL SDK to take full advantage of the modernized OpenSSL 1.1.x API. Besides that fundamental change, AmiSSLv4 can be installed on top of a AmiSSLv3 installation while still ensuring that applications compiled for AmiSSLv3 will continue to work properly. IMPORTANT NOTE: -------------- This release comes with binaries for the AmigaOS4/PPC and AmigaOS3/m68k platform only. Unfortunately, due to lack of motivated developers we couldn't provide native binaries for the MorphOS/PPC or AROS (PPC, i386, x86_64) platform in time. If you are, however, interested in seeing AmiSSL v4 being ported for these other Amiga-based platforms, please try to find motivated and talented developers who could join our team as proper maintainers for these alternative platforms. In addition, if you are a MorphOS or AROS developer yourself, feel free to send proper pull requests to see your platform supported in one of the next releases or please consider joining our team. Requirements: ------------ - AmigaOS 4.0+/PPC, AmigaOS 3.0+/68020+ or MorphOS Version 4.2 (07.03.2018): ------------------------ - Updated OpenSSL backend to full compatibility to latest OpenSSL 1.1.0g (02.11.2017) version. - Updated root certificates to latest Mozilla-based bundle provided by https://curl.haxx.se/ca/ - Fixed https.c example cleanup code for non-OS4 targets (#18) - Reinstated AmigaOS multithreading support and semaphore protection, using the new thread API introduced in OpenSSL 1.1.0 (#17) - Include `ppcinline/macros.h` which contains all `LPXX()` macros to use the AmiSSL includes for MorphOS. - Minor improvements/fixes. Version 4.1 (13.03.2017): ------------------------ - Updated OpenSSL backend to full compatibility to latest OpenSSL 1.1.0e (16.02.2017) version. - MorphOS can now be selected as an install target with the OS3/m68k version being installed. For a native PPC version we would require some work to be done by some talented MorphOS developers. - Added some m68k asm replacement code for potentially speeding up BN calculation routines. - Added AmiUpdate compatibility. - included a newlib compiled version of libamisslauto.a. - Minor improvements/Fixes for install script. Version 4.0 (07.02.2017): ------------------------ - Updated OpenSSL backend to full compatibility to latest OpenSSL 1.1.0d (26 Jan 2017) version. - Updated root certificate bundle to latest Mozilla-based bundle provided by https://curl.haxx.se/ca/ - Removed whole IsCipherAvailable() API and reenabled IDEA, MDC2 and RC5 ciphers as the protecting patents have expired during 2012 and 2015. - Enabled all PPC ASM optimizations in OpenSSL. - Switched build system to exclusively use GCC-based cross compilers for all platforms using proper baserel support for using the amissl shared library in a multi-application environment. General ------- AmiSSL is a shared library package, port of OpenSSL which is "an open source project that provides a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It is also a general-purpose cryptography library." AmiSSL contains three major components: the libraries, the certificate files and a port of the OpenSSL tool. Libraries --------- The main library is "amisslmaster.library" which acts as a proxy which opens the appropriate AmiSSL library (with compatibility to a certain OpenSSL version) for the programs using AmiSSL. It is possible to have different AmiSSL versions installed at the same time since amisslmaster.library will make sure that the correct libraries are opened. However, since a certain version of amisslmaster.library cannot know about the future releases of AmiSSL, it is important that the latest version of amisslmaster.library is always installed. The amisslmaster.library was introduced with AmiSSL v2, but since none of AmiSSL v1 file names collide with later AmiSSL releases, they can coexist on the same system with the later versions. The rest of the libraries are found inside the AmiSSL directory (assigned to AMISSL:Libs/AmiSSL). With the exception of AmiSSL v1 libraries there, none of them should be opened directly, but through amisslmaster.library. The technical details on this can be found in AmiSSL SDK documentation (see https://github.com/jens-maus/amissl/blob/master/dist/README-SDK). The previous versions of libraries in AmiSSL directory should be kept when a new version of AmiSSL is released since they may still be used. For example, IBrowse v2.3 uses AmiSSLv2 libraries through amisslmaster.library. These libraries are named "AmiSSL:Libs/AmiSSL/amissl_v2.library", "AmiSSL:Libs/AmiSSL/blowfish_v2.library", etc. and are based on OpenSSL 0.9.6g. The first release of AmiSSLv3 is based on OpenSSL 0.9.7g, latest available at the time. It includes "AmiSSL:Libs/AmiSSL/amissl_v097g.library" (all other libraries like blowfish, cast etc are now included in it and the name reflects the OpenSSL version number). Since OpenSSL 0.9.6g and 0.9.7g have incompatible API's and public structures, when IBrowse v2.3 tries to open AmiSSL through amisslmaster.library v3, amisslmaster.library will honor its request and open AmiSSLv2 libraries even though AmiSSLv3 library is available. The same applies to AmiSSLv4, the successor of AmiSSLv3. Another example: suppose that a program is compiled for OpenSSL 0.9.7g API. When it asks amisslmaster.library to open AmiSSL with that API, amisslmaster.library will open "AmiSSL:Libs/AmiSSL/amissl_097g.library". If a bugfix version of OpenSSL 0.9.7g called 0.9.7h with compatible API is released, AmiSSL could be updated to include "AmiSSL:Libs/AmiSSL/amissl_097h.library". The amisslmaster.library would then open "amissl_097h.library" on behalf of the program even though it was compiled for and asked for version 0.9.7g. The program would thus benefit from the fixed version without having to be recompiled. Certificates ------------ AmiSSL includes root certificate files which are installed into "AmiSSL:Certs" directory (Note: the AmiSSL: assign must exist - it is usually added to S:User-Startup by the install script). Each AmiSSL version comes with a full set of root certificates and has those that have expired removed. If you had some earlier versions of AmiSSL installed, it is suggested that the old AmiSSL:Certs directory is replaced with the certs directory from the latest AmiSSL archive (The installer script should usually take care of that). Please note that it is not suggested to manually add own certificates to "AmiSSL:Certs". You should rather add and maintain them in "AmiSSL:UserCerts" so that no future AmiSSL release will delete your own certificates. In addition, please note that usually applications providing SSL/TLS functionality should provide you a way to install your own certificates in this directory path. The OpenSSL command-line tool ----------------------------- A port of the OpenSSL command-line tool is also included and usually installed to AMISSL: during installatiopn. It is a "command line tool for using the various cryptography functions of OpenSSL's crypto library from the shell". The documentation for the OpenSSL tool is included in the archive and can also be reviewed online: https://www.openssl.org/docs/man1.1.0/apps/openssl.html Legal information ----------------- AmiSSL v1 Copyright (c) 1999-2006 Andrija Antonijevic. AmiSSL v2/v3 Copyright (c) 2002-2006 Andrija Antonijevic and Stefan Burstroem. AmiSSL v4 Copyright (c) 2014-2018 AmiSSL Open Source Team. All Rights Reserved. AmiSSL IS PROVIDED "AS IS" AND ANY WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AmiSSL AUTHORS OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The OpenSSL toolkit itself stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. OpenSSL License --------------- ==================================================================== Copyright (c) 1998-2016 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Original SSLeay License ----------------------- Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]
Zum Live Linux: