summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorNiels Möller <nisse@lysator.liu.se>2009-08-31 14:34:36 +0200
committerNiels Möller <nisse@lysator.liu.se>2009-08-31 14:34:36 +0200
commit36c10de7ff73c7cc8ee71a1fe2884be41d48810e (patch)
treebe2b2aef959e555f6428332bed639947c9083837 /README
parente997f88b88d901ae99683b88465673d52b26706f (diff)
downloadnettle-36c10de7ff73c7cc8ee71a1fe2884be41d48810e.tar.gz
Updated Nettle README file.
Rev: nettle/README:1.2
Diffstat (limited to 'README')
-rw-r--r--README10
1 files changed, 5 insertions, 5 deletions
diff --git a/README b/README
index 45a85425..6e5efbb3 100644
--- a/README
+++ b/README
@@ -14,15 +14,15 @@ What is Nettle? A quote from the introduction in the Nettle Manual:
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.
+ crypto stuff, and providing a 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.
+ interfaces on top of Nettle, and share the code, test cases, benchmarks,
+ documentation, etc. Examples are the Nettle module for the Pike
+ language, and LSH, which both use 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