[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-anastasis] branch master updated: fix spelling mistakes
|
From: |
gnunet |
|
Subject: |
[taler-anastasis] branch master updated: fix spelling mistakes |
|
Date: |
Thu, 22 Oct 2020 11:28:53 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository anastasis.
The following commit(s) were added to refs/heads/master by this push:
new a6ef5c5 fix spelling mistakes
a6ef5c5 is described below
commit a6ef5c559ddf32a61245f35da52c3497307f9fe2
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Oct 22 11:28:50 2020 +0200
fix spelling mistakes
---
README | 2 +-
contrib/redux.de.json | 2 --
contrib/uncrustify_precommit | 2 +-
doc/ledger-sme-legal-check.txt | 2 +-
doc/manual.texi | 12 ++++++------
doc/merchant-api.content.texi | 6 +++---
doc/next_steps.txt | 2 +-
doc/system-documentation/client_architecture.tex | 2 +-
doc/system-documentation/design.tex | 6 +++---
doc/system-documentation/implementation.tex | 10 +++++-----
doc/system-documentation/introduction.tex | 4 ++--
doc/system-documentation/related_work.tex | 2 +-
doc/system-documentation/thesis.tex | 2 +-
doc/thesis/Journal.tex | 6 +++---
doc/thesis/client_architecture.tex | 2 +-
doc/thesis/design.tex | 6 +++---
doc/thesis/implementation.tex | 10 +++++-----
doc/thesis/introduction.tex | 4 ++--
doc/thesis/related_work.tex | 2 +-
doc/thesis/rest_api_documentation.tex | 2 +-
doc/thesis/thesis.tex | 2 +-
doc/www/anastasis-website/about.html | 2 +-
doc/ypsomed/ypsomed.tex | 2 +-
m4/ax_lib_postgresql.m4 | 2 +-
src/backend/anastasis-httpd.c | 2 +-
src/backend/anastasis-httpd_policy.c | 2 +-
src/backend/anastasis-httpd_policy_upload.c | 4 ++--
src/backend/anastasis-httpd_truth.c | 2 +-
src/cli/test_anastasis_cli.conf | 6 +++---
src/include/anastasis_database_lib.h | 2 +-
src/include/anastasis_database_plugin.h | 6 +++---
src/include/anastasis_service.h | 2 +-
src/lib/anastasis.c | 4 ++--
src/lib/anastasis_api_redux.c | 2 +-
src/lib/test_anastasis_api.conf | 6 +++---
src/lib/testing_cmd_challenge_answer.c | 2 +-
src/stasis/plugin_anastasis_postgres.c | 13 +++++++++----
src/stasis/test_anastasis_db.c | 3 +--
src/util/anastasis_crypto.c | 2 +-
src/util/paths.conf | 2 +-
40 files changed, 78 insertions(+), 76 deletions(-)
diff --git a/README b/README
index 326a1d9..9977eef 100644
--- a/README
+++ b/README
@@ -31,6 +31,6 @@ PHP: PHP License, AGPL- and LGPL-Compatible, owned by The
PHP Group
5. DIRECTORY STRUCTURE
-- 'src/' contains the "backend", a C piece of software which implements cryto
routines
+- 'src/' contains the "backend", a C piece of software which implements crypto
routines
and communication with the 'exchange'
'doc/' contains documentation files, like TeXinfo
diff --git a/contrib/redux.de.json b/contrib/redux.de.json
index 7acf0ac..b698d48 100644
--- a/contrib/redux.de.json
+++ b/contrib/redux.de.json
@@ -38,5 +38,3 @@
}
]
}
-
-
diff --git a/contrib/uncrustify_precommit b/contrib/uncrustify_precommit
index fd29998..2487333 100755
--- a/contrib/uncrustify_precommit
+++ b/contrib/uncrustify_precommit
@@ -30,6 +30,6 @@ if [ $RET = 1 ];
then
echo "Run"
echo "uncrustify --no-backup -c uncrustify.cfg ${crustified}"
- echo "before commiting."
+ echo "before committing."
fi
exit $RET
diff --git a/doc/ledger-sme-legal-check.txt b/doc/ledger-sme-legal-check.txt
index 6c89c19..534bb18 100644
--- a/doc/ledger-sme-legal-check.txt
+++ b/doc/ledger-sme-legal-check.txt
@@ -137,7 +137,7 @@ SMEs check - Partner enterprise data (25-50% of
shares/capital/votes)
=> None.
Partner enterprise data (accounts and other data of the partner enterprise)
1. Name:
-2. Adress (of the registered office):
+2. Address (of the registered office):
3. Enter % of stock/shares/voting rights owned by the Applicant enterprise in
the partner enterprise:
4. Enter % of stock/shares/voting rights owned by the partner enterprise in
the Applicant enterprise:
5. The holding structure of the partner enterprise (you can add a graphic in
the section 'Attachements')
diff --git a/doc/manual.texi b/doc/manual.texi
index b37ad61..07f27ed 100644
--- a/doc/manual.texi
+++ b/doc/manual.texi
@@ -157,7 +157,7 @@ including key dependencies. The third chapter will explain
how to
configure the backend, including in particular the configuration of the
bank account details of the merchant.
-@c The fouth chapter will explain how to test that the setup worked correctly.
+@c The fourth chapter will explain how to test that the setup worked correctly.
The last chapter gives some additional information about advanced topics
which will be useful for system administrators but are not necessary for
@@ -200,7 +200,7 @@ The Taler software stack for a merchant consists of four
main components:
@cindex DBMS
@cindex Postgres
@item A DBMS which stores the transaction history for the Taler backend.
- For now, the GNU Taler reference implemenation only supports Postgres,
+ For now, the GNU Taler reference implementation only supports Postgres,
but the code could be easily extended to support another DBMS.
@end itemize
@@ -680,7 +680,7 @@ private signing key. For example, use:
@example
$ taler-config -s INSTANCE-default -o KEYFILE \
- -V '$@{TALER_CONFIG_HOME@}/merchant/instace/default.key'
+ -V '$@{TALER_CONFIG_HOME@}/merchant/instance/default.key'
@end example
@item
@@ -882,7 +882,7 @@ layout:
[PAYMENTS-GENERATOR]
# The exchange used during the test: make sure the merchant backend
-# being tested accpets this exchange.
+# being tested accepts this exchange.
# If the sysadmin wants, she can also install a local exchange
# and test against it.
EXCHANGE = https://exchange.demo.taler.net/
@@ -1192,7 +1192,7 @@ special ``402 Payment Required'' response inside
the @code{X-Taler-Tip} header.
The frontend should handle errors returned by the backend, such
-as missconfigured instances or a lack of remaining funds for tipping.
+as misconfigured instances or a lack of remaining funds for tipping.
@node Picking up of the tip
@subsection Picking up of the tip
@@ -1230,7 +1230,7 @@ leave some payments unaggregated, and also to use merchant
instances other than the default (which is, actually, the one
used by default by the tool).
-Note: the abilty of driving the aggregation policy is useful
+Note: the ability of driving the aggregation policy is useful
for testing the backoffice facility.
Any subcommand is also equipped with the canonical @code{--help}
diff --git a/doc/merchant-api.content.texi b/doc/merchant-api.content.texi
index 4ab09bd..7dcbb80 100644
--- a/doc/merchant-api.content.texi
+++ b/doc/merchant-api.content.texi
@@ -617,7 +617,7 @@ request object:
@itemize
@item @var{amount}: Amount that should be given to the visitor as a tip.
-@item @var{instance}: Merchant instance that grants the tip (each instance may
have its own independend tipping funds configured).
+@item @var{instance}: Merchant instance that grants the tip (each instance may
have its own independent tipping funds configured).
@item @var{justification}: Description of why the tip was granted.
Human-readable text not exposed to the customer, but used by the Back Office.
@item @var{next_url}: The URL that the user's browser should be redirected to
by the wallet, once the tip has been processed.
@end itemize
@@ -825,13 +825,13 @@ or re-playing a payment, the wallet will receive an
additional signature
showed a payment receipt for the respective order in the current session.
@cindex cookie
-Session-bound payments are triggerd by passing the @code{session_id} parameter
+Session-bound payments are triggered by passing the @code{session_id} parameter
to the @code{/check-payment} endpoint. The wallet will then redirect to the
fulfillment page, but include an additional @code{session_sig} parameter. The
frontend can query @code{/check-payment} with both the @code{session_id} and
the @code{session_sig} to verify that the signature is correct.
-The last session ID that was successfuly used to prove that the payment
+The last session ID that was successfully used to prove that the payment
receipt is in the user's wallet is also available as @code{last_session_id} in
the response to @code{/check-payment}.
@c FIXME: used for what?
diff --git a/doc/next_steps.txt b/doc/next_steps.txt
index 67635f1..e5f477d 100644
--- a/doc/next_steps.txt
+++ b/doc/next_steps.txt
@@ -19,7 +19,7 @@ NEXT STEPS:
- Conclusion (1d)
- Business model (1-2d) ->14.02.
-- Client REST API, tests runnning (2d)
+- Client REST API, tests running (2d)
->14.02. (just compiling)
->17.02. - 20.02. (tests running)
- Crypto API + Implementation (7 -14d)
diff --git a/doc/system-documentation/client_architecture.tex
b/doc/system-documentation/client_architecture.tex
index fc890e3..fb10fd1 100644
--- a/doc/system-documentation/client_architecture.tex
+++ b/doc/system-documentation/client_architecture.tex
@@ -54,7 +54,7 @@ struct account_public_key
\end{lstlisting}
\item
-The truth\_key is a randomly generated AES-256 GCM key. It is used to encrypt
the user specifiy data in the truth object.
+The truth\_key is a randomly generated AES-256 GCM key. It is used to encrypt
the user specify data in the truth object.
\begin{lstlisting}
struct truth_key
{
diff --git a/doc/system-documentation/design.tex
b/doc/system-documentation/design.tex
index cbab0a4..650beb1 100644
--- a/doc/system-documentation/design.tex
+++ b/doc/system-documentation/design.tex
@@ -168,7 +168,7 @@ recover access to their core secret. It primarily
identifies a set of
Anastasis providers. For each key share, the recovery document
specifies the respective Anastasis provider and also prescribes the
{\em authentication method}, which specifies how the user should
-convince the Anastasis server that they are authorized to retreive the
+convince the Anastasis server that they are authorized to retrieve the
encrypted key share. Authentication methods can for example include
SMS-based verification, video-identification or a security question.
@@ -390,7 +390,7 @@ document sent from the client to the server.
% FIXME: "everything"? I don't think we can sign the encrypted truth
% with the eddsa_priv, as that would link the truth to the ERD.
-% We need ANOTHER acocunt key here, one per truth + provider?
+% We need ANOTHER account key here, one per truth + provider?
\begin{lstlisting}
(anastasis-account-signature) = eddsa_sign(h_body, eddsa_priv)
@@ -448,7 +448,7 @@ store data indefinitely.
A second availability issue arises from strong adversaries that may be
able to compute the account keys of some user. While we assume that
-such an adversary cannot successfuly authenticate against the truth,
+such an adversary cannot successfully authenticate against the truth,
the account key does inherently enable these adversaries to upload a
new policy for the account. This cannot be prevented, as the
legitimate user must be able to set or change a policy using only the
diff --git a/doc/system-documentation/implementation.tex
b/doc/system-documentation/implementation.tex
index 158d9c6..d01bcd4 100644
--- a/doc/system-documentation/implementation.tex
+++ b/doc/system-documentation/implementation.tex
@@ -18,7 +18,7 @@ components.
\end{figure}
\noindent In the center is the core implementation of Anastasis.
-On the left are some of the planed authentication methods from the
+On the left are some of the planned authentication methods from the
application. On the right side of the box are the core parts which are
necessary to operate Anastasis commercially. These parts are
anticipated for a production deployment, but not part of the
@@ -63,7 +63,7 @@ details of each component are explained later.
webserver's core logic also returns the response and the status code
of the operation to the client application.
\item Each REST endpoint of the Anastasis server is implemented by
- a specific handler. The handler prcesses the requests, typically
+ a specific handler. The handler processes the requests, typically
by storing or looking up the requested
data with the database. When the request is finished, the handler will
send back the data or the status code to the webserver's core logic.
@@ -160,7 +160,7 @@ Figure~\ref{fig:recovery_process} illustrates the recovery
process.
\item Note the server can define that a challenge has a certain cost,
in this scenario the server rejects the first request because the
user has not yet paid for recovery. After the payment the user can
- resend the request. After each successfuly solved challenge the
+ resend the request. After each successfully solved challenge the
client will check if one of the policies is completely satisfied.
If all shares needed for one of the policies have been recovered,
the client will decrypt the core secret and provide it to the user.
@@ -290,7 +290,7 @@ The following commands are available:
the instructions to follow to authorize release of the share.
\item answer \$truth \$answer: this command tries to answer the
selected challenge with the provided answer. The application will
- check the answer and give a feedback to the user. Everytime a
+ check the answer and give a feedback to the user. Every time a
challenge is solved, the client API will check if as a result any of
the policies is completely satisfied. If any policy was completely
satisfied, the assembler will print out the recovered core secret
@@ -410,7 +410,7 @@ and decryption works as intended.
will test every request in the Anastasis server API. For this we need the
Taler Testing library. The Taler testing library will start an instance
of the Anastasis webserver and a GNU Taler merchant service. The merchant
-service is needed to proccess the payment operations. The testing library
+service is needed to process the payment operations. The testing library
will now send a request to every end point of the Anastasis REST API. It will
check if every response of the REST API is as intended.
\item At the end the whole application flow is tested. For this
diff --git a/doc/system-documentation/introduction.tex
b/doc/system-documentation/introduction.tex
index 668c13b..882345d 100644
--- a/doc/system-documentation/introduction.tex
+++ b/doc/system-documentation/introduction.tex
@@ -152,7 +152,7 @@ and protects the private keys of the user. Those private
keys
legitimate its owners to spend the bitcoins corresponding to the
keys.~\cite{LLLW*2017}
-Loosing Bitcoin wallet keys means losing all of the corresponding
+Losing Bitcoin wallet keys means losing all of the corresponding
Bitcoins. The reader may be familiar with stories from the mass media
about people who claim to have lost their key to their electronic
wallet and therefore huge sums of
@@ -173,7 +173,7 @@ is the ``master key'' $m$:
GNU Taler\footnote{\url{https://taler.net/de/}} is a new electronic instant
payment system for
privacy-friendly online transactions. The GNU Taler digital wallets are
storing electronic coins, and backups are protected with a key.
-Loosing the backup key means losing all the money stored in the wallet,
+Losing the backup key means losing all the money stored in the wallet,
as well as the transaction history kept in the wallet.
The European Central Bank (ECB) informally informed Taler Systems SA
diff --git a/doc/system-documentation/related_work.tex
b/doc/system-documentation/related_work.tex
index 7564b7d..7f4d879 100644
--- a/doc/system-documentation/related_work.tex
+++ b/doc/system-documentation/related_work.tex
@@ -110,7 +110,7 @@ encryption.
\subsubsection{Argon2}
-Hash functions like SHA-512 are designed to be very fast. Therefor
+Hash functions like SHA-512 are designed to be very fast. Therefore
passwords being stored using this kind of hash are vulnerable to
dictionary attacks with new hardware architectures like
FPGAs~\cite{trimberger2012} and dedicated ASIC~\cite{madurawe2006}
diff --git a/doc/system-documentation/thesis.tex
b/doc/system-documentation/thesis.tex
index 3b1fea6..d80dec5 100644
--- a/doc/system-documentation/thesis.tex
+++ b/doc/system-documentation/thesis.tex
@@ -9,7 +9,7 @@
%%\usepackage{libertine}
\usepackage[table]{xcolor}
%% The following chose the default language for the document and
-%% use the default typography rules for the choosen language.
+%% use the default typography rules for the chosen language.
\usepackage{polyglossia}
\setdefaultlanguage{english}
%% \setdefaultlanguage{german}
diff --git a/doc/thesis/Journal.tex b/doc/thesis/Journal.tex
index 997b85b..566c214 100644
--- a/doc/thesis/Journal.tex
+++ b/doc/thesis/Journal.tex
@@ -59,7 +59,7 @@ Present at the Meeting were: Dominik Meister, Dennis Neufeld
and Christian Groth
We could fix the issues from the last meetings and are now in the development
of the crypto library.
We had some problems with pointers which we could discuss and fix. We are
happy that we can see progress.
\subsection*{Next Steps}
-Implementation of the Crypto libarary, finishing API.
+Implementation of the Crypto library, finishing API.
\section*{Meeting 02.04.2020}
Present at the Meeting were: Dominik Meister, Dennis Neufeld and Christian
Grothoff.
@@ -127,7 +127,7 @@ Implementation Anastasis client tests
\section*{Meeting 30.04.2020}
Present at the Meeting were: Dominik Meister, Dennis Neufeld and Christian
Grothoff.
\subsection*{Reflection}
-The testing of the Anastasis client API is progressing slowly. We could find
alot of bugs
+The testing of the Anastasis client API is progressing slowly. We could find a
lot of bugs
in the other components we were not able to see with our previous testing. We
needed to
fix some of the protocol flows. We hope that we can finish the client as soon
as possible
since we also need to implement the authentication procedure and the command
line application.
@@ -200,7 +200,7 @@ Present at the Meeting were: Dominik Meister, Dennis
Neufeld and Christian Groth
\subsection*{Reflection}
We nearly could finish the Anastasis CLI and can now start to focus on the
documentation.
We already have a lot of documentation available which needs to be put
together in one document.
-%We also succeded in the proposal we sent, we are very happy that we can
continue our work on Anastasis after the thesis.
+%We also succeeded in the proposal we sent, we are very happy that we can
continue our work on Anastasis after the thesis.
Additionally the book abstract and the poster are finished and we could
deliver them.
\subsection*{Next Steps}
Work on documentation
diff --git a/doc/thesis/client_architecture.tex
b/doc/thesis/client_architecture.tex
index fc890e3..fb10fd1 100644
--- a/doc/thesis/client_architecture.tex
+++ b/doc/thesis/client_architecture.tex
@@ -54,7 +54,7 @@ struct account_public_key
\end{lstlisting}
\item
-The truth\_key is a randomly generated AES-256 GCM key. It is used to encrypt
the user specifiy data in the truth object.
+The truth\_key is a randomly generated AES-256 GCM key. It is used to encrypt
the user specify data in the truth object.
\begin{lstlisting}
struct truth_key
{
diff --git a/doc/thesis/design.tex b/doc/thesis/design.tex
index cbab0a4..650beb1 100644
--- a/doc/thesis/design.tex
+++ b/doc/thesis/design.tex
@@ -168,7 +168,7 @@ recover access to their core secret. It primarily
identifies a set of
Anastasis providers. For each key share, the recovery document
specifies the respective Anastasis provider and also prescribes the
{\em authentication method}, which specifies how the user should
-convince the Anastasis server that they are authorized to retreive the
+convince the Anastasis server that they are authorized to retrieve the
encrypted key share. Authentication methods can for example include
SMS-based verification, video-identification or a security question.
@@ -390,7 +390,7 @@ document sent from the client to the server.
% FIXME: "everything"? I don't think we can sign the encrypted truth
% with the eddsa_priv, as that would link the truth to the ERD.
-% We need ANOTHER acocunt key here, one per truth + provider?
+% We need ANOTHER account key here, one per truth + provider?
\begin{lstlisting}
(anastasis-account-signature) = eddsa_sign(h_body, eddsa_priv)
@@ -448,7 +448,7 @@ store data indefinitely.
A second availability issue arises from strong adversaries that may be
able to compute the account keys of some user. While we assume that
-such an adversary cannot successfuly authenticate against the truth,
+such an adversary cannot successfully authenticate against the truth,
the account key does inherently enable these adversaries to upload a
new policy for the account. This cannot be prevented, as the
legitimate user must be able to set or change a policy using only the
diff --git a/doc/thesis/implementation.tex b/doc/thesis/implementation.tex
index 158d9c6..d01bcd4 100644
--- a/doc/thesis/implementation.tex
+++ b/doc/thesis/implementation.tex
@@ -18,7 +18,7 @@ components.
\end{figure}
\noindent In the center is the core implementation of Anastasis.
-On the left are some of the planed authentication methods from the
+On the left are some of the planned authentication methods from the
application. On the right side of the box are the core parts which are
necessary to operate Anastasis commercially. These parts are
anticipated for a production deployment, but not part of the
@@ -63,7 +63,7 @@ details of each component are explained later.
webserver's core logic also returns the response and the status code
of the operation to the client application.
\item Each REST endpoint of the Anastasis server is implemented by
- a specific handler. The handler prcesses the requests, typically
+ a specific handler. The handler processes the requests, typically
by storing or looking up the requested
data with the database. When the request is finished, the handler will
send back the data or the status code to the webserver's core logic.
@@ -160,7 +160,7 @@ Figure~\ref{fig:recovery_process} illustrates the recovery
process.
\item Note the server can define that a challenge has a certain cost,
in this scenario the server rejects the first request because the
user has not yet paid for recovery. After the payment the user can
- resend the request. After each successfuly solved challenge the
+ resend the request. After each successfully solved challenge the
client will check if one of the policies is completely satisfied.
If all shares needed for one of the policies have been recovered,
the client will decrypt the core secret and provide it to the user.
@@ -290,7 +290,7 @@ The following commands are available:
the instructions to follow to authorize release of the share.
\item answer \$truth \$answer: this command tries to answer the
selected challenge with the provided answer. The application will
- check the answer and give a feedback to the user. Everytime a
+ check the answer and give a feedback to the user. Every time a
challenge is solved, the client API will check if as a result any of
the policies is completely satisfied. If any policy was completely
satisfied, the assembler will print out the recovered core secret
@@ -410,7 +410,7 @@ and decryption works as intended.
will test every request in the Anastasis server API. For this we need the
Taler Testing library. The Taler testing library will start an instance
of the Anastasis webserver and a GNU Taler merchant service. The merchant
-service is needed to proccess the payment operations. The testing library
+service is needed to process the payment operations. The testing library
will now send a request to every end point of the Anastasis REST API. It will
check if every response of the REST API is as intended.
\item At the end the whole application flow is tested. For this
diff --git a/doc/thesis/introduction.tex b/doc/thesis/introduction.tex
index 668c13b..882345d 100644
--- a/doc/thesis/introduction.tex
+++ b/doc/thesis/introduction.tex
@@ -152,7 +152,7 @@ and protects the private keys of the user. Those private
keys
legitimate its owners to spend the bitcoins corresponding to the
keys.~\cite{LLLW*2017}
-Loosing Bitcoin wallet keys means losing all of the corresponding
+Losing Bitcoin wallet keys means losing all of the corresponding
Bitcoins. The reader may be familiar with stories from the mass media
about people who claim to have lost their key to their electronic
wallet and therefore huge sums of
@@ -173,7 +173,7 @@ is the ``master key'' $m$:
GNU Taler\footnote{\url{https://taler.net/de/}} is a new electronic instant
payment system for
privacy-friendly online transactions. The GNU Taler digital wallets are
storing electronic coins, and backups are protected with a key.
-Loosing the backup key means losing all the money stored in the wallet,
+Losing the backup key means losing all the money stored in the wallet,
as well as the transaction history kept in the wallet.
The European Central Bank (ECB) informally informed Taler Systems SA
diff --git a/doc/thesis/related_work.tex b/doc/thesis/related_work.tex
index 7564b7d..7f4d879 100644
--- a/doc/thesis/related_work.tex
+++ b/doc/thesis/related_work.tex
@@ -110,7 +110,7 @@ encryption.
\subsubsection{Argon2}
-Hash functions like SHA-512 are designed to be very fast. Therefor
+Hash functions like SHA-512 are designed to be very fast. Therefore
passwords being stored using this kind of hash are vulnerable to
dictionary attacks with new hardware architectures like
FPGAs~\cite{trimberger2012} and dedicated ASIC~\cite{madurawe2006}
diff --git a/doc/thesis/rest_api_documentation.tex
b/doc/thesis/rest_api_documentation.tex
index a08c951..4d53fb6 100644
--- a/doc/thesis/rest_api_documentation.tex
+++ b/doc/thesis/rest_api_documentation.tex
@@ -105,7 +105,7 @@ Get the customer’s encrypted recovery document. If
“version” is not specif
\textbf{Status Codes: } \\
\begin{itemize}
\item 200 OK – The escrow provider responds with an EncryptedRecoveryDocument
object.
-\item 304 Not modified – The client requested the same ressource it already
knows.
+\item 304 Not modified – The client requested the same resource it already
knows.
\item 400 Bad request – The \$ACCOUNT\_PUB is not an EdDSA public key.
\item 402 Payment Required – The account’s balance is too low for the
specified operation. See the Taler payment protocol specification for how to
pay.
\item 403 Forbidden – The required account signature was invalid.
diff --git a/doc/thesis/thesis.tex b/doc/thesis/thesis.tex
index 64a9898..22b0f2a 100644
--- a/doc/thesis/thesis.tex
+++ b/doc/thesis/thesis.tex
@@ -9,7 +9,7 @@
%%\usepackage{libertine}
\usepackage[table]{xcolor}
%% The following chose the default language for the document and
-%% use the default typography rules for the choosen language.
+%% use the default typography rules for the chosen language.
\usepackage{polyglossia}
\setdefaultlanguage{english}
%% \setdefaultlanguage{german}
diff --git a/doc/www/anastasis-website/about.html
b/doc/www/anastasis-website/about.html
index 89379a4..3ed289d 100644
--- a/doc/www/anastasis-website/about.html
+++ b/doc/www/anastasis-website/about.html
@@ -94,7 +94,7 @@ https://templatemo.com/tm-547-real-dynamic
<div class="tm-strategy-box tm-mb-7">
<i class="fas fa-user-secret fa-4x
tm-strategy-icon"></i>
<p class="tm-strategy-text"><b>Privacy</b> <br>
- Privacy is our primary objective. We do not collect
any unneccessary personal data,
+ Privacy is our primary objective. We do not collect
any unnecessary personal data,
and the data we collect we encrypt until the point
where we need it.
</p>
diff --git a/doc/ypsomed/ypsomed.tex b/doc/ypsomed/ypsomed.tex
index 8edbfaa..8eeb1fa 100644
--- a/doc/ypsomed/ypsomed.tex
+++ b/doc/ypsomed/ypsomed.tex
@@ -9,7 +9,7 @@
\usepackage{kpfonts}
%%\usepackage{libertine}
%% The following chose the default language for the document and
-%% use the default typography rules for the choosen language.
+%% use the default typography rules for the chosen language.
\usepackage{polyglossia}
\setdefaultlanguage{english}
%% \setdefaultlanguage{german}
diff --git a/m4/ax_lib_postgresql.m4 b/m4/ax_lib_postgresql.m4
index 11b6991..9eb4316 100644
--- a/m4/ax_lib_postgresql.m4
+++ b/m4/ax_lib_postgresql.m4
@@ -80,7 +80,7 @@ AC_DEFUN([AX_LIB_POSTGRESQL],
fi
if test ! -x "$PG_CONFIG"; then
- dnl AC_MSG_ERROR([$PG_CONFIG does not exist or it is not an
exectuable file])
+ dnl AC_MSG_ERROR([$PG_CONFIG does not exist or it is not an
executable file])
PG_CONFIG="no"
found_postgresql="no"
fi
diff --git a/src/backend/anastasis-httpd.c b/src/backend/anastasis-httpd.c
index 252b893..a5ac3a3 100644
--- a/src/backend/anastasis-httpd.c
+++ b/src/backend/anastasis-httpd.c
@@ -242,7 +242,7 @@ AH_trigger_curl (void)
* can be set with the #MHD_OPTION_NOTIFY_COMPLETED).
* Initially, `*con_cls` will be NULL.
* @return #MHD_YES if the connection was handled successfully,
- * #MHD_NO if the socket must be closed due to a serios
+ * #MHD_NO if the socket must be closed due to a serious
* error while handling the request
*/
static MHD_RESULT
diff --git a/src/backend/anastasis-httpd_policy.c
b/src/backend/anastasis-httpd_policy.c
index 4cd0f30..2dc61f7 100644
--- a/src/backend/anastasis-httpd_policy.c
+++ b/src/backend/anastasis-httpd_policy.c
@@ -107,7 +107,7 @@ AH_return_policy (struct MHD_Connection *connection,
return TALER_MHD_reply_with_error (connection,
MHD_HTTP_INTERNAL_SERVER_ERROR,
TALER_EC_INTERNAL_INVARIANT_FAILURE,
- "unexpected return status (backup
missmatch)");
+ "unexpected return status (backup
mismatch)");
case ANASTASIS_DB_STATUS_PAYMENT_REQUIRED:
GNUNET_break (0);
return TALER_MHD_reply_with_error (connection,
diff --git a/src/backend/anastasis-httpd_policy_upload.c
b/src/backend/anastasis-httpd_policy_upload.c
index 39bfd9a..701376a 100644
--- a/src/backend/anastasis-httpd_policy_upload.c
+++ b/src/backend/anastasis-httpd_policy_upload.c
@@ -230,7 +230,7 @@ cleanup_ctx (struct TM_HandlerContext *hc)
*
* @param connection MHD connection
* @param order_id our backend's order ID
- * @return MHD repsonse to use
+ * @return MHD response to use
*/
static struct MHD_Response *
make_payment_request (const char *order_id)
@@ -869,7 +869,7 @@ AH_handler_policy_post (struct MHD_Connection *connection,
/* get ready to hash (done here as we may go async for payments next) */
puc->hash_ctx = GNUNET_CRYPTO_hash_context_start ();
- /* Check database to see if the transaction is permissable */
+ /* Check database to see if the transaction is permissible */
{
struct GNUNET_HashCode hc;
enum ANASTASIS_DB_QueryStatus qs;
diff --git a/src/backend/anastasis-httpd_truth.c
b/src/backend/anastasis-httpd_truth.c
index 689306f..3f1b655 100644
--- a/src/backend/anastasis-httpd_truth.c
+++ b/src/backend/anastasis-httpd_truth.c
@@ -236,7 +236,7 @@ request_done (struct TM_HandlerContext *hc)
*
* @param connection MHD connection
* @param order_id our backend's order ID
- * @return MHD repsonse to use
+ * @return MHD response to use
*/
static struct MHD_Response *
make_payment_request (const char *order_id)
diff --git a/src/cli/test_anastasis_cli.conf b/src/cli/test_anastasis_cli.conf
index f15392b..88891f3 100644
--- a/src/cli/test_anastasis_cli.conf
+++ b/src/cli/test_anastasis_cli.conf
@@ -1,10 +1,10 @@
# This file is in the public domain.
#
[PATHS]
-# Persistant data storage for the testcase
+# Persistent data storage for the testcase
TALER_TEST_HOME = test_anastasis_api_home/
-# Persistant data storage
+# Persistent data storage
TALER_DATA_HOME = $TALER_TEST_HOME/.local/share/taler/
# Configuration files
@@ -229,7 +229,7 @@ ENABLE_CREDIT = YES
# wire fees
[fees-x-taler-bank]
-# Fees for the forseeable future...
+# Fees for the foreseeable future...
# If you see this after 2018, update to match the next 10 years...
WIRE-FEE-2018 = TESTKUDOS:0.01
WIRE-FEE-2019 = TESTKUDOS:0.01
diff --git a/src/include/anastasis_database_lib.h
b/src/include/anastasis_database_lib.h
index 7c12495..a2e0287 100644
--- a/src/include/anastasis_database_lib.h
+++ b/src/include/anastasis_database_lib.h
@@ -56,7 +56,7 @@ enum ANASTASIS_DB_QueryStatus
*/
ANASTASIS_DB_STATUS_VALID_CODE_STORED = -6,
/**
- * Provided Challenge code didnt match the server generated code
+ * Provided Challenge code didn't match the server generated code
*/
ANASTASIS_DB_STATUS_CHALLENGE_CODE_MISSMATCH = -5,
/**
diff --git a/src/include/anastasis_database_plugin.h
b/src/include/anastasis_database_plugin.h
index ebaa810..57fbc73 100644
--- a/src/include/anastasis_database_plugin.h
+++ b/src/include/anastasis_database_plugin.h
@@ -258,7 +258,7 @@ struct ANASTASIS_DatabasePlugin
* @param method name of method
* @param nonce nonce used to compute encryption key for encrypted_truth
* @param aes_gcm_tag authentication tag of encrypted_truth
- * @param encrypted_truth contains the encrypted Truth which includes the
ground truth i.e. H(challange answer), phonenumber, SMS
+ * @param encrypted_truth contains the encrypted Truth which includes the
ground truth i.e. H(challenge answer), phonenumber, SMS
* @param encrypted_truth_size the size of the Truth
* @param truth_expiration time till the according data will be stored
* @return transaction status
@@ -425,7 +425,7 @@ struct ANASTASIS_DatabasePlugin
/**
* Insert a new challenge code for a given challenge identified by the
challenge
* public key. The function will first check if there is already a valid code
- * for this challenge present and wont insert a new one in this case.
+ * for this challenge present and won't insert a new one in this case.
*
* @param cls closure
* @param truth_public_key the identifier for the challenge
@@ -490,7 +490,7 @@ struct ANASTASIS_DatabasePlugin
const struct
ANASTASIS_PaymentSecretP *payment_identifier);
/**
- * FIXME maybe implemented in the postgres_gc but want it seperate first
+ * FIXME maybe implemented in the postgres_gc but want it separate first
* Function called to remove all expired codes in the database
* @return transaction status
*/
diff --git a/src/include/anastasis_service.h b/src/include/anastasis_service.h
index fd71456..0be7a8a 100644
--- a/src/include/anastasis_service.h
+++ b/src/include/anastasis_service.h
@@ -416,7 +416,7 @@ typedef void
* @param backend_url backend's base URL, including final "/"
* @param anastasis_pub public key of the user's account
* @param anastasis_priv private key of the user's account
- * @param prev_recovery_data_hash hash of the privious policy update, NULL for
the first upload ever
+ * @param prev_recovery_data_hash hash of the previous policy update, NULL for
the first upload ever
* @param recovery_data policy data to be stored
* @param recovery_data_size number of bytes in @a recovery_data
* @param payment_requested #GNUNET_YES if the client wants to pay more for
the account now
diff --git a/src/lib/anastasis.c b/src/lib/anastasis.c
index 5e3dd99..5a066f9 100644
--- a/src/lib/anastasis.c
+++ b/src/lib/anastasis.c
@@ -72,7 +72,7 @@ struct ANASTASIS_Recovery
struct ANASTASIS_PolicyLookupOperation *plo;
/**
- * Encrypted recovery document, only used for the decription
+ * Encrypted recovery document, only used for the description
*/
void *encrypted_recovery_document;
@@ -150,7 +150,7 @@ struct ANASTASIS_Challenge
void *af_cls;
/**
- * Reference to the recovery proccess which is ongoing
+ * Reference to the recovery process which is ongoing
*/
struct ANASTASIS_Recovery *recovery;
diff --git a/src/lib/anastasis_api_redux.c b/src/lib/anastasis_api_redux.c
index b6bfddd..09f2329 100644
--- a/src/lib/anastasis_api_redux.c
+++ b/src/lib/anastasis_api_redux.c
@@ -110,7 +110,7 @@ struct ConfigRequest
char *backend_name;
/**
- * currrency used by the anastasis backend.
+ * currency used by the anastasis backend.
*/
char *backend_currency;
diff --git a/src/lib/test_anastasis_api.conf b/src/lib/test_anastasis_api.conf
index 3362397..0821ffb 100644
--- a/src/lib/test_anastasis_api.conf
+++ b/src/lib/test_anastasis_api.conf
@@ -1,10 +1,10 @@
# This file is in the public domain.
#
[PATHS]
-# Persistant data storage for the testcase
+# Persistent data storage for the testcase
TALER_TEST_HOME = test_anastasis_api_home/
-# Persistant data storage
+# Persistent data storage
TALER_DATA_HOME = $TALER_TEST_HOME/.local/share/taler/
# Configuration files
@@ -230,7 +230,7 @@ ENABLE_CREDIT = YES
# wire fees
[fees-x-taler-bank]
-# Fees for the forseeable future...
+# Fees for the foreseeable future...
# If you see this after 2018, update to match the next 10 years...
WIRE-FEE-2018 = EUR:0.01
WIRE-FEE-2019 = EUR:0.01
diff --git a/src/lib/testing_cmd_challenge_answer.c
b/src/lib/testing_cmd_challenge_answer.c
index 309dcaa..e4ae796 100644
--- a/src/lib/testing_cmd_challenge_answer.c
+++ b/src/lib/testing_cmd_challenge_answer.c
@@ -53,7 +53,7 @@ struct ChallengeState
const char *answer;
/**
- * Referenece to the recovery process
+ * Reference to the recovery process
*/
const char *challenge_ref;
diff --git a/src/stasis/plugin_anastasis_postgres.c
b/src/stasis/plugin_anastasis_postgres.c
index 8a68c96..c00667b 100644
--- a/src/stasis/plugin_anastasis_postgres.c
+++ b/src/stasis/plugin_anastasis_postgres.c
@@ -1007,7 +1007,7 @@ postgres_record_challenge_payment (void *cls,
__FILE__,
__LINE__,
TALER_B2S (truth_public_key));
- /*dummy funcion to check if truth is available*/
+ /*dummy function to check if truth is available*/
void *truth;
size_t truth_size;
@@ -1181,7 +1181,7 @@ postgres_check_payment_identifier (void *cls,
* @param method name of method
* @param nonce nonce used to compute encryption key for encrypted_truth
* @param aes_gcm_tag authentication tag of encrypted_truth
- * @param encrypted_truth contains the encrypted Truth which includes the
ground truth i.e. H(challange answer), phonenumber, SMS
+ * @param encrypted_truth contains the encrypted Truth which includes the
ground truth i.e. H(challenge answer), phonenumber, SMS
* @param encrypted_truth_size the size of the Truth
* @param truth_expiration time till the according data will be stored
* @return transaction status
@@ -1563,6 +1563,7 @@ postgres_get_recovery_document (void *cls,
}
}
+
/**
* Verify the provided code with the code on the server.
* If the code matches the function will return with success, if the code
@@ -1740,6 +1741,7 @@ postgres_lookup_challenge_payment (void *cls,
return ANASTASIS_DB_STATUS_SUCCESS_ONE_RESULT;
}
+
/**
* Update payment status of challenge
*
@@ -1796,10 +1798,11 @@ postgres_update_challenge_payment (void *cls,
return ANASTASIS_DB_STATUS_SUCCESS_ONE_RESULT;
}
+
/**
* Insert a new challenge code for a given challenge identified by the
challenge
* public key. The function will first check if there is already a valid code
- * for this challenge present and wont insert a new one in this case.
+ * for this challenge present and won't insert a new one in this case.
*
* @param cls closure
* @param truth_public_key the identifier for the challenge
@@ -1914,8 +1917,9 @@ postgres_store_challenge_code (void *cls,
return ANASTASIS_DB_STATUS_SUCCESS_ONE_RESULT;
}
+
/**
- * FIXME maybe implemented in the postgres_gc but want it seperate first
+ * FIXME maybe implemented in the postgres_gc but want it separate first
* Function called to remove all expired codes in the database
* @return transaction status
*/
@@ -1936,6 +1940,7 @@ postgres_challenge_gc (void *cls)
params);
}
+
/**
* Initialize Postgres database subsystem.
*
diff --git a/src/stasis/test_anastasis_db.c b/src/stasis/test_anastasis_db.c
index 0a6df85..fcb51a7 100644
--- a/src/stasis/test_anastasis_db.c
+++ b/src/stasis/test_anastasis_db.c
@@ -122,7 +122,7 @@ run (void *cls)
RND_BLK (&aes_gcm_tag);
post_counter = 2;
mime_type = "Picture";
- method = "Methode";
+ method = "Method";
TALER_string_to_amount ("EUR:30",&amount);
GNUNET_CRYPTO_random_block (GNUNET_CRYPTO_QUALITY_NONCE,
@@ -274,7 +274,6 @@ run (void *cls)
123));
-
FAILIF (ANASTASIS_DB_STATUS_SUCCESS_ONE_RESULT !=
plugin->verify_challenge_code (plugin->cls,
&truth_public_key,
diff --git a/src/util/anastasis_crypto.c b/src/util/anastasis_crypto.c
index de08845..214f1ea 100644
--- a/src/util/anastasis_crypto.c
+++ b/src/util/anastasis_crypto.c
@@ -43,7 +43,7 @@
* @param key_m_len length of key
* @param nonce nonce for calculation
* @param salt salt value for calculation
- * @param key[out] where to write the en-/decription key
+ * @param key[out] where to write the en-/description key
* @param iv[out] where to write the IV
*/
static void
diff --git a/src/util/paths.conf b/src/util/paths.conf
index 4b45fc1..c62a24a 100644
--- a/src/util/paths.conf
+++ b/src/util/paths.conf
@@ -16,7 +16,7 @@ ANASTASIS_HOME =
${ANASTASIS_TEST_HOME:-${HOME:-${USERPROFILE}}}
# http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
# for how these should be used.
-# Persistant data storage
+# Persistent data storage
ANASTASIS_DATA_HOME = ${XDG_DATA_HOME:-$ANASTASIS_HOME/.local/share}/anastasis/
# Configuration files
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-anastasis] branch master updated: fix spelling mistakes,
gnunet <=