commit 1e053baabd72815b8f28401089a08aad3b59a924
parent 233a935497745df0c311c671557389a728164dd9
Author: Christian Grothoff <christian@grothoff.org>
Date: Wed, 15 Nov 2023 23:25:47 +0100
update docs, bump version
Diffstat:
5 files changed, 16 insertions(+), 60 deletions(-)
diff --git a/README b/README
@@ -3,7 +3,7 @@ About CHALLENGER
Challenger implements an HTTP server that allows clients to validate
-that a user is able to receive PIN/TAN codes at a given address using
+that a user is able to receive TAN codes at a given address using
OAuth 2.0-style authorization.
Envisioned use-cases are KYC checks where a user must prove that they
@@ -21,8 +21,8 @@ verification session a particular client has authorized. This is
expected to be useful in cases where address verifications have
non-negligible cost. The system also limits how often a user-agent
may change the address per authorization session as well as the number
-of times the PIN/TAN code is transmitted to each address. Finally, it
-of course also limits the number of times a user may enter a PIN/TAN
+of times the TAN code is transmitted to each address. Finally, it
+of course also limits the number of times a user may enter a TAN
code.
@@ -38,8 +38,8 @@ user.
Flexibility:
============
-The actual transmission of the PIN/TAN code is done via a separate
-binary that is simply invoked by the challenger service. This makes
+The actual transmission of the TAN code is done via a separate
+program that is simply invoked by the challenger service. This makes
the code useful for all types of address validations. Simple shell
scripts are provided for SMS, e-mail and physical address validation.
diff --git a/configure.ac b/configure.ac
@@ -4,7 +4,7 @@
# This configure file is in the public domain
AC_PREREQ([2.69])
-AC_INIT([challenger],[0.0.0],[taler-bug@gnu.org])
+AC_INIT([challenger],[0.9.3],[taler-bug@gnu.org])
AC_CONFIG_SRCDIR([src/challenger/challenger-httpd.c])
AC_CONFIG_HEADERS([challenger_config.h])
# support for non-recursive builds
diff --git a/contrib/Makefile.am.in b/contrib/Makefile.am.in
@@ -7,12 +7,8 @@ bin_SCRIPTS = \
tmplpkgdatadir = $(prefix)/share/challenger/templates/
-
-%.css: wallet-core/challenger/%.css
- cp $< $@
-
-%.must: wallet-core/challenger/%.must
- cp $< $@
+EXTRA_DIST = \
+ challenger-dbconfig
# This is for the templates imported from the wallet-core.git
# prebuilt branch. This MUST be the last line in the
diff --git a/debian/changelog b/debian/changelog
@@ -1,3 +1,9 @@
+challenger (0.9.3) unstable; urgency=medium
+
+ * First actual release.
+
+ -- Christian Grothoff <grothoff@gnu.org> Wed, 15 Nov 2023 00:00:00 +0000
+
challenger (0.0.0) unstable; urgency=medium
* Initial Debian package.
diff --git a/doc/doxygen/challenger.doxy b/doc/doxygen/challenger.doxy
@@ -38,13 +38,13 @@ PROJECT_NAME = "GNU Taler: Challenger"
# could be handy for archiving the generated documentation or if some version
# control system is used.
-PROJECT_NUMBER = 0.0
+PROJECT_NUMBER = 0.9.3
# Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer a
# quick idea about the purpose of the project. Keep the description short.
-PROJECT_BRIEF =
+PROJECT_BRIEF = Address validation service with OAuth 2.0 API
# With the PROJECT_LOGO tag one can specify a logo or an icon that is included
# in the documentation. The maximum height of the logo should not exceed 55
@@ -93,14 +93,6 @@ ALLOW_UNICODE_NAMES = NO
OUTPUT_LANGUAGE = English
-# The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
-# documentation generated by doxygen is written. Doxygen will use this
-# information to generate all generated output in the proper direction.
-# Possible values are: None, LTR, RTL and Context.
-# The default value is: None.
-
-OUTPUT_TEXT_DIRECTION = None
-
# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
# descriptions after the members that are listed in the file and class
# documentation (similar to Javadoc). Set to NO to disable this.
@@ -1905,16 +1897,6 @@ LATEX_BATCHMODE = NO
LATEX_HIDE_INDICES = NO
-# If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
-# code with syntax highlighting in the LaTeX output.
-#
-# Note that which sources are shown also depends on other settings such as
-# SOURCE_BROWSER.
-# The default value is: NO.
-# This tag requires that the tag GENERATE_LATEX is set to YES.
-
-LATEX_SOURCE_CODE = NO
-
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
# bibliography, e.g. plainnat, or ieeetr. See
# https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
@@ -1995,16 +1977,6 @@ RTF_STYLESHEET_FILE =
RTF_EXTENSIONS_FILE =
-# If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
-# with syntax highlighting in the RTF output.
-#
-# Note that which sources are shown also depends on other settings such as
-# SOURCE_BROWSER.
-# The default value is: NO.
-# This tag requires that the tag GENERATE_RTF is set to YES.
-
-RTF_SOURCE_CODE = NO
-
#---------------------------------------------------------------------------
# Configuration options related to the man page output
#---------------------------------------------------------------------------
@@ -2101,15 +2073,6 @@ GENERATE_DOCBOOK = NO
DOCBOOK_OUTPUT = docbook
-# If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
-# program listings (including syntax highlighting and cross-referencing
-# information) to the DOCBOOK output. Note that enabling this will significantly
-# increase the size of the DOCBOOK output.
-# The default value is: NO.
-# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
-
-DOCBOOK_PROGRAMLISTING = NO
-
#---------------------------------------------------------------------------
# Configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
@@ -2288,15 +2251,6 @@ EXTERNAL_PAGES = YES
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
-# If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
-# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
-# NO turns the diagrams off. Note that this option also works with HAVE_DOT
-# disabled, but it is recommended to install and use dot, since it yields more
-# powerful graphs.
-# The default value is: YES.
-
-CLASS_DIAGRAMS = NO
-
# You can include diagrams made with dia in doxygen documentation. Doxygen will
# then run dia to produce the diagram and insert it in the documentation. The
# DIA_PATH tag allows you to specify the directory where the dia binary resides.
