lsh is a client that can connect to the corresponding lshd server. It uses
the SECSH protocol, which means that it is compatible with SSH 2.0, except
for file transfer, which is not part of SECSH.
SECSH uses compression and encryption algorithms that are unencumbered, and
lsh itself is GPL.
lsh is not as feature-rich as OpenSSH, as it doesn't currently support
password-protected keyrings, the SSH 1.X protocols, TCP wrappers, etc.
On the other hand, it doesn't require OpenSSL, and doesn't take a lot of
work to avoid patented algorithms.
Port author's notes on usage and common problems can be found at
OpenBSM is an open source implementation of Sun's Basic Security Module (BSM)
Audit API and file format. BSM, the de facto industry standard for Audit,
describes a set of system call and library interfaces for managing audit
records, as well as a token stream file format that permits extensible and
generalized audit trail processing. OpenBSM extends the BSM API and file
format in a number of ways to support features present in the Mac OS X and
FreeBSD operating systems, such as Mach task interfaces, sendfile(), and
Linux system calls present in the FreeBSD Linux emulation layer.
OpenBSM is an open source implementation of Sun's Basic Security Module (BSM)
Audit API and file format. BSM, the de facto industry standard for Audit,
describes a set of system call and library interfaces for managing audit
records, as well as a token stream file format that permits extensible and
generalized audit trail processing. OpenBSM extends the BSM API and file
format in a number of ways to support features present in the Mac OS X and
FreeBSD operating systems, such as Mach task interfaces, sendfile(), and
Linux system calls present in the FreeBSD Linux emulation layer.
Bindings to OpenSSL libssl and libcrypto, plus custom SSH pubkey
parsers. Supports RSA, DSA and NIST curves P-256, P-384 and P-521.
Cryptographic signatures can either be created and verified manually
or via x509 certificates. AES block cipher is used in CBC mode for
symmetric encryption; RSA for asymmetric (public key) encryption.
High-level envelope functions combine RSA and AES for encrypting
arbitrary sized data. Other utilities include key generators, hash
functions (md5, sha1, sha256, etc), base64 encoder, a secure random
number generator, and 'bignum' math methods for manually performing
crypto calculations on large multibyte integers.
This perl module provides support for the https protocol
under LWP, so that a LWP::UserAgent can make https GET &
HEAD & POST requests. Please see perldoc LWP for more
information on POST requests.
The Crypt::SSLeay package contains Net::SSL, which is
automatically loaded by LWP::Protocol::https on https
requests, and provides the necessary SSL glue for that
module to work via these deprecated modules:
Crypt::SSLeay::CTX
Crypt::SSLeay::Conn
Crypt::SSLeay::X509
Work on Crypt::SSLeay has been continued only to provide
https support for the LWP - libwww perl libraries. If you
want access to the OpenSSL API via perl, check out Sampo's
Net::SSLeay.
In short: getting and installing SSL/TLS certificates made easy.
The Let's Encrypt Client is a tool to automatically receive and install
X.509 certificates to enable TLS on servers. The client will
interoperate with the Let's Encrypt CA which will be issuing
browser-trusted certificates for free.
It's all automated:
The tool will prove domain control to the CA and submit a CSR
(Certificate Signing Request).
If domain control has been proven, a certificate will get issued and
the tool will automatically install it.
dar is a shell command that backs up directory trees and files. It has been
tested under Linux, Windows, Solaris, FreeBSD, NetBSD, MacOS X and several
other systems, it is released under the GNU General Public License (GPL).
Since version 2.0.0 an Application Interface (API) is available, opening the
way for external/independent Graphical User Interfaces (GUIs) like kdar.
This API relies on the libdar library, which is the core part of DAR
programs; as such, the API is released under the GPL. Consequently, to use
the API, your program must be released under the GPL as well.
GPT fdisk (aka gdisk) by Roderick W. Smith, rodsmith@rodsbooks.com
This software is intended as a (somewhat) fdisk-workalike program for
GPT-partitioned disks. Specific advantages of gdisk, cgdisk and
sgdisk include:
* Edit GUID partition table (GPT) definitions in Linux, FreeBSD, MacOS X,
or Windows
* Convert MBR to GPT or back without data loss
* Convert BSD disklabels to GPT without data loss
* Create hybrid MBR, which permits GPT-unaware
OSes to access up to three GPT partitions on the disk
* Repair damaged GPT data structures
* The ability to specify sector-exact partition sizes
* Clear identification of the number of unallocated sectors on a disk
http://www.rodsbooks.com/fixparts/
A user-space utility for testing the memory subsystem for faults. It is
portable and should compile and work on any 32- or 64-bit Unix-like system.
(Yes, even weird, proprietary Unices, and even Mac OS X.) For hardware
developers, memtester can be told to test memory starting at a particular
physical address as of memtester version 4.1.0.
The original source was by Simon Kirby <sim@stormix.com>. The program has
been rewritten by Charles Cazabon and many additional tests were added to
help catch borderline memory. He also rewrote the original tests (which
catch mainly memory bits which are stuck permanently high or low) so that
they run approximately an order of magnitude faster.
nvramtool is a utility for reading/writing coreboot parameters and
displaying information from the coreboot table. It is intended for x86-based
systems (both 32-bit and 64-bit) that use coreboot.
The coreboot table resides in low physical memory, and may be accessed
through the /dev/mem interface. It is created at boot time by coreboot, and
contains various system information such as the type of mainboard in use. It
specifies locations in the CMOS (nonvolatile RAM) where the coreboot
parameters are stored.
For information about coreboot, see http://www.coreboot.org/.