.. _gns-sharing:
Publishing and sharing your zone
================================
A zone becomes useful to others once they can find it. This page explains
how to publish records, how to hand out your zone key, and how to get a name
for your zone that other GNUnet users can resolve without any setup.
Publishing records
------------------
Only records marked as **public** are published. Add ``-p`` when you create
a record:
.. code-block:: console
$ gnunet-namestore -z myzone -a -p -n www -t A -V 192.0.2.1 -e 1d
Your peer signs and encrypts public records and stores them in the GNUnet
DHT, and republishes them regularly while it is running. Keep your peer
running (see :doc:`/users/start`): if it stays offline, your records
eventually expire from the network.
Sharing your zone key
---------------------
Print the public key of your zone and give it to the people who should be
able to resolve your names:
.. code-block:: console
$ gnunet-identity -d -q -e myzone
000G0507HZ8M09QWA93N2YX9Y9357777C0HTPK7PA0HTKJS5GCXXPGKBWC
A friend then adds it to one of their zones under a petname of their
choice, for example ``you``:
.. code-block:: console
$ gnunet-namestore -z theirzone -a -n you -t EDKEY -V 000G0507HZ8M...WC -e 1d
and can resolve your public records as ``www.you.theirzone``. Without
adding anything, they can also use the key itself as the top-level domain:
``www.000G0507HZ8M...WC``.
How you exchange keys matters: the key *is* the identity of your zone. Use
a channel that you trust to deliver it unmodified, for example in person or
in a signed message.
Registering a name under .pin.gns.alt
-------------------------------------
Every GNUnet installation is configured with the start zone
``.pin.gns.alt``, a registry operated by GNUnet e.V. on a first-come,
first-served basis. If you register ``myname`` there, every GNUnet user can
resolve your records as ``www.myname.pin.gns.alt`` without exchanging keys
first.
To register, visit https://fcfs.gnunet.org and register your zone key under
a name of your choice. The registrar is connected to the demo deployment of
`GNU Taler `__ and asks for a payment in KUDOS, a demo
currency you get for free when you register at the Taler demo; the service
is therefore effectively free.
Keep in mind that names in ``.pin.gns.alt`` are only as trustworthy as the
registry: whoever operates it could, in principle, change the delegation.
For names that matter, exchange keys directly as well.
Business cards and QR codes
---------------------------
GNUnet includes ``gnunet-bcd``, which creates printable business cards with
a QR code of your zone key, and ``gnunet-qr``, which reads such a code with
a camera and imports the zone.
.. warning::
In GNUnet 0.29, importing a zone from a QR code does not work: the
import step (``gnunet-namestore -u``) fails for current zone keys.
Exchange keys as text, as shown above, until this is fixed.
``gnunet-bcd`` is a small web application. It needs a LaTeX installation
with the ``units``, ``labels``, ``pst-barcode``, ``luatex85``, ``preview``,
``pdfcrop`` and ``koma-script`` packages (on Debian, ``texlive-full``
contains all of them). Start it, then open http://localhost:8888/ in a
browser and fill in the form, including your zone key:
.. code-block:: console
$ gnunet-arm -i bcd
The result is a PDF with ten business cards.
The default start zones
-----------------------
The start zones configured by default, such as ``.pin.gns.alt``, are
registered in `GANA `__ and follow a `restrictive
registration policy
`__.
Every user can remove them or add others; see :ref:`gns-concepts`.
Running your own registrar
--------------------------
The software behind https://fcfs.gnunet.org is available as a separate
package, the GNUnet GNS registrar, from the `GNU FTP mirror
`__. Build and run it with:
.. code-block:: console
$ ./configure && make
$ ./gnunet-gns-registrar
It requires a `GNU Taler merchant backend `__ for
payments; see the example configuration in the package for the available
options.