diff options
Diffstat (limited to 'template/reclaim/faq.html.j2')
-rw-r--r-- | template/reclaim/faq.html.j2 | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/template/reclaim/faq.html.j2 b/template/reclaim/faq.html.j2 new file mode 100644 index 00000000..b49b8f6c --- /dev/null +++ b/template/reclaim/faq.html.j2 | |||
@@ -0,0 +1,26 @@ | |||
1 | {% extends "common/base.j2" %} | ||
2 | {% block body_content %} | ||
3 | <div class="m-3"> | ||
4 | <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / FAQ | ||
5 | </div> | ||
6 | <h2 class="text-center">{{ _("Frequently asked questions") }}</h2> | ||
7 | <br/> | ||
8 | <div class="container"> | ||
9 | <ul class="fa-ul"> | ||
10 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How is re:claimID different from</b> <i><insert other identity provider service here> ?</i></li> | ||
11 | <li><i class="fa-li fas fa-comment"></i> Unlike most other identity provider services, re:claimID is not operated by a single service provider or even a federated consortium of service providers. Instead, it is a fully decentralised service operated implicitly by its users. Consequently, large-scale data monetisation, mass-surveillance and other (ab)use of personal data is inherently mitigated.</li> | ||
12 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How much does re:claimID cost?</b></li> | ||
13 | <li><i class="fa-li fas fa-comment"></i> re:claimID is Free Software. We argue that in order for an identity system to be a credible solution for self-sovereign citizens to exercise their right to digital self determination, open and free software as well as services are indispensible.</li> | ||
14 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does re:claimID work?</b></li> | ||
15 | <li><i class="fa-li fas fa-comment"></i> re:claimID uses the GNU Name System as identity and attribute directory service. In order to allow the user to enforce access control decisions, we use a cryptographic access control layer. However, the user is not required to manage any cryptographic keys or manage zones in a namespace. This is done under the hood by re:claimID.</li> | ||
16 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does a website know the attribute data share via re:claimID is correct?</b></li> | ||
17 | <li><i class="fa-li fas fa-comment"></i> Short answer: It doesn't. | ||
18 | Long answer: Identities are initially self-asserted by the user. re:claimID could, however, also be used to share third party attested attributes (e.g. X.509 certificates). Further, have integrated <a href="https://github.com/Fraunhofer-AISEC/libpabc">Privacy-ABCs</a> for <a href="{{ url_localized('news/2021-05-DISSENS.html') }}">this use case</a>.</li> | ||
19 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>Who is behind re:claimID?</b></li> | ||
20 | <li><i class="fa-li fas fa-comment"></i> re:claimID was initially developed at <a href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> and is part of GNUnet.</li> | ||
21 | <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>I found a bug!</b></li> | ||
22 | <li><i class="fa-li fas fa-comment"></i> We aim to continuously develop and improve re:claimID. Help us by <a href="https://bugs.gnunet.org">reporting any issues you encounter</a>.</li> | ||
23 | </ul> | ||
24 | |||
25 | </div> | ||
26 | {% endblock body_content %} | ||