Displaying 1 to 20 from 66 results

testssl.sh - Testing TLS/SSL encryption anywhere on any port

  •    Shell

testssl.sh is a free command line tool which checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as some cryptographic flaws. Or help yourself downloading the ZIP archive https://github.com/drwetter/testssl.sh/archive/2.9dev.zip. testssl.sh --help will give you some help upfront. More help: see doc directory with man pages. Older sample runs are at https://testssl.sh/.

netkiller.github.io - Netkiller Free ebook - 免费电子书

  •    HTML


pyopenssl - A Python wrapper around the OpenSSL library

  •    Python

Note: The Python Cryptographic Authority strongly suggests the use of pyca/cryptography where possible. If you are using pyOpenSSL for anything other than making a TLS connection you should move to cryptography and drop your pyOpenSSL dependency. ... and much more.

wolfssl - wolfSSL (formerly CyaSSL) is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud

  •    C

The wolfSSL embedded SSL library (formerly CyaSSL) is a lightweight SSL/TLS library written in ANSI C and targeted for embedded, RTOS, and resource-constrained environments - primarily because of its small size, speed, and feature set. It is commonly used in standard operating environments as well because of its royalty-free pricing and excellent cross platform support. wolfSSL supports industry standards up to the current TLS 1.3 and DTLS 1.3 levels, is up to 20 times smaller than OpenSSL, and offers progressive ciphers such as ChaCha20, Curve25519, NTRU, and Blake2b. User benchmarking and feedback reports dramatically better performance when using wolfSSL over OpenSSL. There are many reasons to choose wolfSSL as your embedded SSL solution. Some of the top reasons include size (typical footprint sizes range from 20-100 kB), support for the newest standards (SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3, DTLS 1.0, and DTLS 1.2), current and progressive cipher support (including stream ciphers), multi-platform, royalty free, and an OpenSSL compatibility API to ease porting into existing applications which have previously used the OpenSSL package. For a complete feature list, see Section 4.1.

bud - Bud - The TLS Terminator

  •    C

A TLS terminator for superheroes.Bud is implemented fully in C, with the exception to the tests which are running on node.js. The networking level is provided by libuv, and the SSL implementation by OpenSSL 1.0.2h.

node-bignum - Big integers for Node.js using OpenSSL

  •    Javascript

Arbitrary precision integral arithmetic for Node.js using OpenSSL. This library is based on node-bigint by substack, but instead of using libgmp, it uses the builtin bignum functionality provided by OpenSSL. The advantage is that OpenSSL is already part of Node.js, so this library does not add any external dependency whatsoever.

mesalink - MesaLink is a memory-safe and OpenSSL-compatible TLS library.

  •    Rust

MesaLink is a memory-safe and OpenSSL-compatible TLS library. Since 2014, the industry has seen a huge impact and loss due to memory vulnerabilities in TLS stacks; such as the infamous "Heartbleed" bug. MesaLink is born with the goal of eradicating memory vulnerabilities in TLS stacks; and it is written in Rust, a programming language that guarantees memory safety. This significantly reduces the attack surfaces; which further facilitates auditing and restricting the remaining attack surfaces. MesaLink is cross-platform and provides OpenSSL-compatible APIs. It works seamlessly in desktop, mobile, and IoT devices. With the growth of the ecosystem, MesaLink would also be adopted in the server environment in the future. To get better functionality along with strong security guarantees, MesaLink follows the following rules-of-thumb for hybrid memory-safe architecture designing proposed by the Rust SGX SDK project.

Boringssl - Fork of OpenSSL that is designed to meet Google's needs

  •    C

BoringSSL is a fork of OpenSSL that is designed to meet Google's needs. BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.

openssl - OpenSSL bindings for Go

  •    Go

Copyright (C) 2017. See AUTHORS. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

EasyCert - EasyCert quickly generates web server TLS certificates that have been self-signed by a private certificate authority that it also creates

  •    Go

Use EasyCert to easily generate webserver certificates against a private certificate authority that is also generated by this tool. Why would you want to use this? This should only be used within company networks, never public facing. You would use this to implement your own TLS connections where you are dealing in a test environment where the security doesn't really matter. This is more about making sure things work across https correctly. In other words, when you are working on anything production-level you'd want to acquire a genuine certificate from a trusted certificate authority and probably pay for it or better yet use LetsEncrypt.This has been tested and run on OSX which is comes pre-installed with openssl, that is all you need.

openssl-osx-ca - Simple periodic task to sync OSX Keychain certs to Homebrew installed OpenSSL & LibreSSL

  •    Objective-C

A simple tool and script intended to be run periodically by launchd(8) to sync an openssl style CA pem with the certificates found in the OSX Keychain(s). The original name is now a misnomer, as the software will manage certificate bundles for both openssl and libressl installed under Homebrew.

ssh-key-decrypt - Decrypt and encrypted ssh private keys

  •    Javascript

Data can be either a string or a buffer. It is the contents of the key file.If the file is not encrypted, then the passphrase doesn't matter.

nano-nginx - Nano container with nginx preconfigured as reverse proxy


Dockerfile used to build image. The server try to find the setting file nginx.conf in /etc/nginx folder, you can use default installation settings from your distro, the only thing you have to do is to mount the settings folder in the docker container.

BlueCryptor - Swift cross-platform crypto library using CommonCrypto/libcrypto

  •    Swift

Swift cross-platform crypto library derived from IDZSwiftCommonCrypto. IMPORTANT NOTE: This release is NOT entirely source code compatible with previous releases. There are instances where exceptions are thrown now instead of the framework calling fatalError(). This means that there are more recoverable errors in the library than before. The only time that fatalError() is called is to indicate either a programming error or a non-recoverable system error.

OpenSSL - Swift modulemaps for libSSL and libcrypto

  •    C

Swift modulemaps for libSSL and libcrypto.

openssl - Provides SSL, TLS and general purpose cryptography.

  •    C

OpenSSL provides SSL, TLS and general purpose cryptography. It wraps the OpenSSL library. You may need to specify the path where OpenSSL is installed.

dcrypt - node.js openssl bindings

  •    C++

Openssl bindings for Node.js. Written in Coffeescript.