From 0f7c3be5dd6b60151e1174c60049a4cd0fdec004 Mon Sep 17 00:00:00 2001
From: Pavol Rusnak <stick@gk2.sk>
Date: Wed, 21 Aug 2013 20:05:25 +0200
Subject: [PATCH] expand readme

---
 Makefile |  2 +-
 README   | 10 ++++++++++
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 1e400c8fb..a232f6126 100644
--- a/Makefile
+++ b/Makefile
@@ -8,7 +8,7 @@ all: test-speed test-verify
 	$(CC) $(CFLAGS) -o $@ -c $<
 
 test-speed: test-speed.o $(OBJS)
-	gcc test-speed.o $(OBJS) -o test-speed -lcrypto
+	gcc test-speed.o $(OBJS) -o test-speed
 
 test-verify: test-verify.o $(OBJS)
 	gcc test-verify.o $(OBJS) -o test-verify -lcrypto
diff --git a/README b/README
index bfcd6b5f0..6aa6031b5 100644
--- a/README
+++ b/README
@@ -14,3 +14,13 @@ b) random generator in rand.c is using stdlib's rand() function.
    you should replace this code with one that uses a hardware random
    generator of your microcontroller in production.
    (see speed-stm32/rand.c for such example)
+
+c) there are executables:
+   * test-speed
+     - check signing speed (sign 100x and compute speed from duration)
+   * test-verify
+     - generate random messages and private keys
+     - check signature validity against OpenSSL (call verify method)
+
+d) directory speed-stm32 contains project for deploying the code
+   on STM32 microcontroller and checking signing speed there