Explore projects
-
Nettle / nettle
OtherNettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.
Updated -
The main repository of the LysKOM client written in Emacs Lisp.
Updated -
Updated
-
-
lyskom-server / lyskom-server
GNU General Public License v2.0 or laterThe main LysKOM repository.
Updated -
-
Updated
-
Updated
-
Wim Lewis / nettle
OtherNettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.
Updated -
Hugo Hörnquist / Linux Unattended Installation
MIT LicenseUpdated -
-
-
Updated
-
Marcus Hoffmann / nettle
OtherNettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.
Updated -
Magnus Holmgren / lyskom-server
GNU General Public License v2.0 or laterThe main LysKOM repository.
Updated -
Andrew Lawrence / nettle
OtherNettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.
Updated -
Brian Smith / nettle
OtherNettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.
Updated -
Updated
-
Fernando Ortiz / liboop
GNU Lesser General Public License v2.1 onlyLiboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the “select() loop” and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.
Initially developed by Dan Egnor, liboop is now maintained by Niels Möller and Per Cederqvist.
Updated -
Andreas Olsson / The mixed bin
MIT LicenseUpdated