challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

control (2860B)

      1 Source: challenger
      2 Section: net
      3 Priority: optional
      4 Maintainer: Christian Grothoff <grothoff@gnu.org>
      5 Build-Depends:
      6  meson,
      7  ninja-build,
      8  debhelper-compat (= 12),
      9  libgnunet-dev (>=0.28.1~dev4),
     10  libtalerexchange-dev (>= 1.6.13),
     11  libpq-dev (>=15),
     12  pkg-config,
     13  po-debconf,
     14  zlib1g-dev,
     15  texinfo
     16 Standards-Version: 4.5.0
     17 Vcs-Git: https://salsa.debian.org/debian/challenger.git
     18 Vcs-Browser: https://salsa.debian.org/debian/challenger
     19 Homepage: https://taler.net/
     20 
     21 Package: challenger-httpd
     22 Section: net
     23 Architecture: any
     24 Pre-Depends:
     25  ${misc:Pre-Depends}
     26 Depends:
     27  libtalerexchange (>= 1.6.13),
     28  libgnutls30 (>= 3.7.1),
     29  challenger-webui,
     30  adduser,
     31  zstd,
     32  lsb-base,
     33  netbase,
     34  ${misc:Depends},
     35  ${shlibs:Depends}
     36 Recommends:
     37  apache2 | nginx | httpd,
     38  taler-challenger-helpers,
     39  postgresql (>=15.0)
     40 Description: OAuth 2.0-compatible address validation service
     41  Challenger validates that a user is able to receive messages at a given
     42  address (e-mail, SMS phone number, or postal address) and exposes the
     43  verified address to a registered client via OAuth 2.0. After the user
     44  submits an address, Challenger generates a TAN code and sends it through
     45  a configurable helper script (one is shipped for each supported address
     46  type); once the user returns the correct code, the client may obtain the
     47  validated address through the standard OAuth 2.0 ``/info`` endpoint.
     48  .
     49  Typical use cases include Know-Your-Customer (KYC) flows for the GNU
     50  Taler payment system and any other application that needs lightweight
     51  proof that a user controls a particular contact address.
     52  .
     53  This package provides the challenger-httpd daemon together with its
     54  systemd socket and service units, command-line administration tools
     55  (challenger-admin, challenger-config, challenger-dbconfig,
     56  challenger-dbinit), the bundled single-page web frontend, and example
     57  reverse-proxy snippets for Apache and nginx. The daemon listens on a
     58  UNIX domain socket and is intended to be run behind a TLS-terminating
     59  reverse proxy; PostgreSQL is used for persistent storage.
     60 
     61 
     62 Package: challenger-httpd-dev
     63 Section: libdevel
     64 Architecture: any
     65 Depends:
     66  libtalerexchange-dev (>= 1.6.13),
     67  ${misc:Depends}
     68 Description: OAuth 2.0-compatible address validation service - development files
     69  Challenger validates that a user is able to receive messages at a given
     70  address (e-mail, SMS phone number, or postal address) and exposes the
     71  verified address to a registered client via OAuth 2.0.
     72  .
     73  This package contains the C headers and shared-library symlinks needed
     74  to build software that links against Challenger's utility or database
     75  libraries. It should be noted that these libraries are not useful to
     76  interact with the Challenger REST API and we are currently not aware
     77  of any component using these library interfaces. The are also not
     78  considered to be stable and may change in the future.