After that you should get various @command{bin/nncp-*} binaries and
@command{bin/hjson-cli} command (only for your convenience, not
-necessary installation). Documentation for example for
+necessary installation). For example, documentation for
@command{nncp-bundle} command can be get with
@command{info doc/nncp.info -n nncp-bundle}.
It uses @url{http://cr.yp.to/redo.html, redo} build system for that
-examples. You can use either dozen of various implementations, or at
-least minimalistic POSIX shell @command{contrib/do} (just replace
+examples. You can use one of its various implementations, or at least
+minimalistic POSIX shell @command{contrib/do} (just replace
@command{redo} with @command{contrib/do} in the example above) included
in tarball. Following ones are tested to work with:
@url{http://www.goredo.cypherpunks.ru/, goredo} (NNCP's author creation),
@section Prepared tarballs
You can obtain releases source code prepared tarballs from the links below.
-Do not forget to check tarball @ref{Integrity, integrity}.
+Do not forget to check tarball @ref{Integrity, integrity}! Also there
+are @ref{Mirrors, mirrors} of this website.
Tarballs include all necessary required libraries:
* Sync protocol: Sync
* MultiCast Discovery: MCD
* EBlob format: EBlob
+* Mirrors::
* Thanks::
* Contacts and feedback: Contacts
* Copying conditions: Copying
@include sp.texi
@include mcd.texi
@include eblob.texi
+@include mirrors.texi
@include thanks.texi
@include contacts.texi
used for building documentation (although tarballs already include it).
In general you must get @ref{Tarballs, the tarball}, check its
-@ref{Integrity, integrity and authenticity} and run @command{make}.
+@ref{Integrity, integrity and authenticity} and run @command{redo}.
Look for general and platform-specific @ref{Build-instructions, build
instructions}.
--- /dev/null
+@node Mirrors
+@unnumbered Mirrors
+
+Main NNCP website is hosted on two geographically distant servers
+located in Moscow, Russian Federation. One of server's IPv6 connectivity
+is provided by Hurricane Electric tunnel broker. Only one of those
+servers supports TLS and another just proxies the traffic to it. So
+TLS-capable version has less availability. It can be authenticated
+with @url{http://ca.cypherpunks.ru/, ca.cypherpunks.ru} certificate,
+through the @url{https://datatracker.ietf.org/doc/html/rfc6698, DANE}
+record, that in turn can be authenticated with
+@url{https://dnscurve.org/, DNSCurve}-secured
+@url{http://www.stargrave.org/Trust-anchor.html, trust anchors}. Both
+@code{ca.cypherpunks.ru} and DNSCurve trust anchors are signed with
+@code{CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF}
+@url{https://en.wikipedia.org/wiki/OpenPGP, OpenPGP}
+@url{http://www.stargrave.org/Contacts.html, public key}.
+
+@table @asis
+
+@item @url{https://nncp.mirrors.quux.org/}
+
+Its creation @url{http://lists.cypherpunks.ru/archive/nncp-devel/2108/0310.html, announcement}.
+Mirror of the whole NNCP's website with all tarballs, made by John Goerzen.
+It uses @url{https://letsencrypt.org/, Let's Encrypt} certificate
+authority, so can be more easily accessible for some people. If you have
+got NNCP-peering with
+@url{http://lists.cypherpunks.ru/archive/nncp-devel/2108/0283.html, nncp.quux.org}
+node, then you can also @ref{nncp-freq, freq} the @ref{Tarballs, tarballs}
+from it.
+
+@end table
to use @ref{Tarballs, tarballs} instead.
@example
-$ git clone git://git.cypherpunks.ru/nncp.git
-$ cd nncp
-$ git checkout develop
+$ git clone --branch develop git://git.cypherpunks.ru/nncp.git nncp
@end example
You can also use @url{https://git.cypherpunks.ru/nncp.git}.
feedback and NixOS package maintenance.
@item @url{mailto:jgoerzen@@complete.org, John Goerzen} for his feature
-suggestions, bugreports and Debian package maintenance.
+suggestions, bugreports, Debian package and mirror maintenance, and the
+whole project popularization.
@end itemize
cat > doc/download.texi <<EOF
@node Tarballs
@section Prepared tarballs
-You can obtain releases source code prepared tarballs on
-@url{http://www.nncpgo.org/}.
+You can obtain releases source code prepared tarballs from
+@url{http://www.nncpgo.org/} and from one of its
+@url{http://www.nncpgo.org/Mirrors.html, mirrors}.
EOF
perl -i -ne 'print unless /include pedro/' doc/index.texi doc/about.ru.texi
perl -p -i -e 's/^(.verbatiminclude) .*$/$1 PUBKEY.asc/g' doc/integrity.texi
GPG key ID: 0x2B25868E75A1A953 NNCP releases <releases@nncpgo.org>
Fingerprint: 92C2 F0AE FE73 208E 46BF F3DE 2B25 868E 75A1 A953
+There are mirrors where you can also get the source code tarballs:
+http://www.nncpgo.org/Mirrors.html
+
Please send questions regarding the use of NNCP, bug reports and patches
to mailing list: http://lists.cypherpunks.ru/nncp_002ddevel.html
EOF
Идентификатор GPG ключа: 0x2B25868E75A1A953 NNCP releases <releases@nncpgo.org>
Отпечаток: 92C2 F0AE FE73 208E 46BF F3DE 2B25 868E 75A1 A953
+Есть и зеркала где вы также можете получить архивы с исходным кодом:
+http://www.nncpgo.org/Mirrors.html
+
Пожалуйста, все вопросы касающиеся использования NNCP, отчёты об ошибках
и патчи отправляйте в nncp-devel почтовую рассылку:
http://lists.cypherpunks.ru/nncp_002ddevel.html