From fe602751424da12174099dc2bb01f267c4e52a1a Mon Sep 17 00:00:00 2001 From: Logan007 Date: Wed, 24 Jun 2020 16:21:58 +0545 Subject: [PATCH] updated README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 522da3e..155a9e0 100644 --- a/README.md +++ b/README.md @@ -121,9 +121,9 @@ A benchmark of the encryption methods is available when compiled from source wit Use `-H` on the edges to enable header encryption. Note, that header encryption is a per-community decision, i.e. all edges of one community need to have it either enabled or disabled. The supernode -can handle encrypted and unencrypted headers. As the key fro header encryption is derived from the -community names, it requires the supernode to be used with fixed communities `-c ` -parameter. +can handle encrypted and unencrypted headers. As the key for header encryption is derived from the +community names, it requires the supernode to be used with fixed communities `-c ` +parameter. Also, reuse of once-publically-used community names for header encryption is not recomended. ## Contribution