Skip to content
Snippets Groups Projects
Select Git revision
  • hpke
  • master default protected
  • ppc-chacha-4core
  • delete-internal-name-mangling
  • master-updates
  • ppc-gcm
  • ppc-chacha-2core
  • refactor-ecc-mod
  • ppc-chacha-core
  • use-mpn_cnd-functions
  • optimize-ecc-invert
  • default-m4-quote-char
  • power-asm-wip
  • test-fat
  • chacha-3core-neon
  • x86_64-salsa20-2core
  • salsa20-2core-neon
  • bcrypt
  • arm-salsa20-chacha-vsra
  • test-shlib-dir
  • nettle_3.6_release_20200429
  • nettle_3.6rc3
  • nettle_3.6rc2
  • nettle_3.6rc1
  • nettle_3.5.1_release_20190627
  • nettle_3.5_release_20190626
  • nettle_3.5rc1
  • nettle_3.4.1_release_20181204
  • nettle_3.4.1rc1
  • nettle_3.4_release_20171119
  • nettle_3.4rc2
  • nettle_3.4rc1
  • nettle_3.3_release_20161001
  • nettle_3.2_release_20160128
  • nettle_3.1.1_release_20150424
  • nettle_3.1_release_20150407
  • nettle_3.1rc3
  • nettle_3.1rc2
  • nettle_3.1rc1
  • nettle_3.0_release_20140607
40 results

nettle

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Nettle / nettle
    3555 commits behind the upstream repository.
    Niels Möller's avatar
    Niels Möller authored
    should not be distributed.
    
    Rev: src/nettle/ChangeLog:1.239
    Rev: src/nettle/Makefile.am:1.73
    ccc7508e
    History
    What is Nettle? A quote from the introduction in the Nettle Manual:
    
      Nettle is a 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. In most contexts, you need more than the basic
      cryptographic algorithms, you also need some way to keep track of available
      algorithms, their properties and variants. You often have some algorithm
      selection process, often dictated by a protocol you want to implement.
      
      And as the requirements of applications differ in subtle and not so
      subtle ways, an API that fits one application well can be a pain to use
      in a different context. And that is why there are so many different
      cryptographic libraries around.
      
      Nettle tries to avoid this problem by doing one thing, the low-level
      crypto stuff, and providing a @emph{simple} but general interface to it.
      In particular, Nettle doesn't do algorithm selection. It doesn't do
      memory allocation. It doesn't do any I/O.
      
      The idea is that one can build several application and context specific
      interfaces on top of Nettle, and share the code, testcases, benchmarks,
      documentation, etc. For this first version, the only application using
      Nettle is LSH, and it uses an object-oriented abstraction on top of the
      library. 
    
    Nettle 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. See the file COPYING for details. Most, but not
    all, of Nettle can also be used under the terms of the GNU Lesser
    General Public License; please read the Copyright section of the
    manual if you want to exercise this option.
    
    Build nettle with the usual ./configure && make && make check && make
    install. Read the manual. Mail me if you have any questions or
    suggestions.
    
    You can also build Nettle from cvs, using
    
      cvs -d :pserver:anonymous@cvs.lysator.liu.se:/cvsroot/lsh login
      [ empty password ]
      cvs -d :pserver:anonymous@cvs.lysator.liu.se:/cvsroot/lsh co nettle
    
    If you get it from cvs, you need to build it with
    
      ./.bootstrap && ./configure && make && make check
    
    You may want to subscribe to the nettle-bugs mailing list. See
    <URL: http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs>.
    
    
    Happy hacking,
    /Niels Möller <nisse@lysator.liu.se>