challenger

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

control (2806B)

      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.27.0),
     10  libtalerexchange-dev (>= 1.5.0),
     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.5.0),
     28  libgnutls30 (>= 3.7.1),
     29  adduser,
     30  zstd,
     31  lsb-base,
     32  netbase,
     33  ${misc:Depends},
     34  ${shlibs:Depends}
     35 Recommends:
     36  apache2 | nginx | httpd,
     37  postgresql (>=15.0)
     38 Description: OAuth 2.0-compatible address validation service
     39  Challenger validates that a user is able to receive messages at a given
     40  address (e-mail, SMS phone number, or postal address) and exposes the
     41  verified address to a registered client via OAuth 2.0. After the user
     42  submits an address, Challenger generates a TAN code and sends it through
     43  a configurable helper script (one is shipped for each supported address
     44  type); once the user returns the correct code, the client may obtain the
     45  validated address through the standard OAuth 2.0 ``/info`` endpoint.
     46  .
     47  Typical use cases include Know-Your-Customer (KYC) flows for the GNU
     48  Taler payment system and any other application that needs lightweight
     49  proof that a user controls a particular contact address.
     50  .
     51  This package provides the challenger-httpd daemon together with its
     52  systemd socket and service units, command-line administration tools
     53  (challenger-admin, challenger-config, challenger-dbconfig,
     54  challenger-dbinit), the bundled single-page web frontend, and example
     55  reverse-proxy snippets for Apache and nginx. The daemon listens on a
     56  UNIX domain socket and is intended to be run behind a TLS-terminating
     57  reverse proxy; PostgreSQL is used for persistent storage.
     58 
     59 
     60 Package: challenger-httpd-dev
     61 Section: libdevel
     62 Architecture: any
     63 Depends:
     64  libtalerexchange-dev (>= 1.5.0),
     65  ${misc:Depends}
     66 Description: OAuth 2.0-compatible address validation service - development files
     67  Challenger validates that a user is able to receive messages at a given
     68  address (e-mail, SMS phone number, or postal address) and exposes the
     69  verified address to a registered client via OAuth 2.0.
     70  .
     71  This package contains the C headers and shared-library symlinks needed
     72  to build software that links against Challenger's utility or database
     73  libraries. It should be noted that these libraries are not useful to
     74  interact with the Challenger REST API and we are currently not aware
     75  of any component using these library interfaces. The are also not
     76  considered to be stable and may change in the future.