aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorrexxnor <rexxnor+gnunet@brief.li>2019-01-10 13:31:23 +0100
committerrexxnor <rexxnor+gnunet@brief.li>2019-01-25 17:27:28 +0100
commitb889d108b5068f3e893e8f399ed545ff956db818 (patch)
tree8fab3a0804bd9808b9cd6ec56d957302e332dbdc /doc
parentc756d928ba129075106d5b31e188270258b76a0a (diff)
downloadgnunet-b889d108b5068f3e893e8f399ed545ff956db818.tar.gz
gnunet-b889d108b5068f3e893e8f399ed545ff956db818.zip
added documentation for the ascension tool
Diffstat (limited to 'doc')
-rw-r--r--doc/handbook/chapters/developer.texi4
-rw-r--r--doc/handbook/chapters/installation.texi26
-rw-r--r--doc/handbook/chapters/user.texi40
3 files changed, 66 insertions, 4 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi
index d9c92247b..37e11cb11 100644
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -8768,14 +8768,14 @@ regular expressions.
8768 8768
8769Using the REST subsystem, you can expose REST-based APIs or services. 8769Using the REST subsystem, you can expose REST-based APIs or services.
8770The REST service is designed as a pluggable architecture. 8770The REST service is designed as a pluggable architecture.
8771To create a new REST endpoint, simply add a library in the form 8771To create a new REST endpoint, simply add a library in the form
8772``plugin_rest_*''. 8772``plugin_rest_*''.
8773The REST service will automatically load all REST plugins on startup. 8773The REST service will automatically load all REST plugins on startup.
8774 8774
8775@strong{Configuration} 8775@strong{Configuration}
8776 8776
8777The REST service can be configured in various ways. 8777The REST service can be configured in various ways.
8778The reference config file can be found in 8778The reference config file can be found in
8779@file{src/rest/rest.conf}: 8779@file{src/rest/rest.conf}:
8780@example 8780@example
8781[rest] 8781[rest]
diff --git a/doc/handbook/chapters/installation.texi b/doc/handbook/chapters/installation.texi
index c05f776f2..5ce9805ed 100644
--- a/doc/handbook/chapters/installation.texi
+++ b/doc/handbook/chapters/installation.texi
@@ -35,7 +35,7 @@ The mandatory libraries and applications are
35@item libextractor 35@item libextractor
36@item libidn 36@item libidn
37@item libmicrohttpd @geq{}0.9.52 37@item libmicrohttpd @geq{}0.9.52
38@item libnss 38@item libnss
39@item libunistring 39@item libunistring
40@item gettext 40@item gettext
41@item glibc 41@item glibc
@@ -1427,6 +1427,7 @@ and @code{[transport-https_client]} section of the configuration:
1427* GNS Proxy Setup:: 1427* GNS Proxy Setup::
1428* Setup of the GNS CA:: 1428* Setup of the GNS CA::
1429* Testing the GNS setup:: 1429* Testing the GNS setup::
1430* Migrating existing DNS zones into GNS::
1430@end menu 1431@end menu
1431 1432
1432 1433
@@ -1693,6 +1694,29 @@ configured proxy) should give you a valid SSL certificate for
1693@c FIXME: Image does not exist, create it or save it from Drupal? 1694@c FIXME: Image does not exist, create it or save it from Drupal?
1694@c @image{images/gnunethpgns.png,5in,, picture of homepage.gnu in Webbrowser} 1695@c @image{images/gnunethpgns.png,5in,, picture of homepage.gnu in Webbrowser}
1695 1696
1697@node Migrating existing DNS zones into GNS
1698@subsubsection Migrating existing DNS zones into GNS
1699
1700To migrate an existing zone into GNS use the ascension tool.
1701You can find the source code here: @code{}
1702
1703The software can be installed into a python virtual environment like this:
1704@example
1705$ python3 -m venv .venv
1706$ source .venv/bin/activate
1707$ python3 setup.py install
1708@end example
1709
1710Or installed globally like this (not recommended):
1711@example
1712$ sudo python3 setup.py install
1713@end example
1714
1715The advantage of using a virtual environment is, that all the dependencies can be installed separately in different versions without touching your existing python installation.
1716
1717@c How to reference another section here?
1718Using the tool is discussed in another section.
1719
1696 1720
1697@node Configuring the GNUnet VPN 1721@node Configuring the GNUnet VPN
1698@subsection Configuring the GNUnet VPN 1722@subsection Configuring the GNUnet VPN
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index ea41bbb6c..79c6563a1 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -1453,6 +1453,7 @@ the user. This results in non-unique name-value mappings as
1453* Using Public Keys as Top Level Domains:: 1453* Using Public Keys as Top Level Domains::
1454* Resource Records in GNS:: 1454* Resource Records in GNS::
1455* Synchronizing with legacy DNS:: 1455* Synchronizing with legacy DNS::
1456* Migrating an existing DNS zone into GNS::
1456@end menu 1457@end menu
1457 1458
1458 1459
@@ -1631,6 +1632,8 @@ GNS currently supports the following record types:
1631* ABE MASTER:: 1632* ABE MASTER::
1632* RECLAIM OIDC CLIENT:: 1633* RECLAIM OIDC CLIENT::
1633* RECLAIM OIDC REDIRECT:: 1634* RECLAIM OIDC REDIRECT::
1635* Synchronizing with legacy DNS::
1636* Migrating an existing DNS zone into GNS::
1634@end menu 1637@end menu
1635 1638
1636@node NICK 1639@node NICK
@@ -1891,6 +1894,40 @@ DNS zone and that do not have a local gns service in use, it
1891is thus advisable to disable the namecache by setting the 1894is thus advisable to disable the namecache by setting the
1892option ``DISABLE'' to ``YES'' in section ``[namecache]''. 1895option ``DISABLE'' to ``YES'' in section ``[namecache]''.
1893 1896
1897@node Migrating an existing DNS zone into GNS
1898@subsection Migrating an existing DNS zone into GNS
1899
1900After installing the tool according to the README file you have these options:
1901@example
1902Ascension
1903
1904Usage:
1905 ascension.py <domain> [-d]
1906 ascension.py <domain> -p <port> [-d]
1907 ascension.py <domain> -ns <transferns> [-d]
1908 ascension.py <domain> -ns <transferns> -p <port> [-d]
1909 ascension.py -h | --help
1910 ascension.py -v | --version
1911
1912Options:
1913 <port> Port for zone transfer
1914 <domain> Domain to migrate
1915 <transferns> DNS Server that does the zone transfer
1916 -d --debug Enable debugging
1917 -h --help Show this screen.
1918 -v --version Show version.
1919@end example
1920
1921To migrate the Syrian top level domain - one of the few top level domains that still support zone transfers - use the following command:
1922
1923@example
1924$ ascension sy. -ns ns1.tld.sy.
1925@end example
1926
1927This will take a while but after it has finished executing the zone will have been migrated into GNS.
1928
1929@c remove this once daemonized
1930Currently this will only snapshot the zone at it's current state and not update it. There is a plan to daemonize the migration process so you don't have to worry that a zone will stay up to date.
1894 1931
1895@node re@:claim Identity Provider 1932@node re@:claim Identity Provider
1896@section re@:claim Identity Provider 1933@section re@:claim Identity Provider
@@ -1962,7 +1999,7 @@ Further, the "ticket" can be re-used later to retrieve up-to-date attributes in
1962 1999
1963To list all given authorizations (tickets) you can execute: 2000To list all given authorizations (tickets) you can execute:
1964@example 2001@example
1965$ gnunet-reclaim -e "friend" -T (TODO there is only a C and REST API for this at this time) 2002$ gnunet-reclaim -e "friend" -T (TODO there is only a C and REST API for this at this time)
1966@end example 2003@end example
1967 2004
1968 2005
@@ -2292,3 +2329,4 @@ protocol (--tcp or --udp) and you will again receive an IP address
2292that will terminate at the respective peer's service. 2329that will terminate at the respective peer's service.
2293 2330
2294 2331
2332