Add support for hash chaining to detect modifications in postings

The following details of a posting contribute to its hash:

  fullname of account
  string representation of amount

Each posting hashes contributes to the transaction hash, which is compromised
of:

  previous transaction’s hash (as encountered in parsing order)
  actual date
  optional auxiliary date
  optional code
  payee
  hashes of all postings

Note that this means that changes in the “code” or any of the comments

1 files changed, 1 insertions, 1 deletions

diff --git a/src/precmd.cc b/src/precmd.cc
index 8ec25d71..25c28fc8 100644
--- a/src/precmd.cc
+++ b/src/precmd.cc
@@ -74,7 +74,7 @@ namespace {
         parsing_context.get_current().journal = report.session.journal.get();
         parsing_context.get_current().scope   = &report.session;
 
-        report.session.journal->read(parsing_context);
+        report.session.journal->read(parsing_context, false);
         report.session.journal->clear_xdata();
       }
     }