diff options
Diffstat (limited to 'doc/handbook')
-rw-r--r-- | doc/handbook/chapters/installation.texi | 44 |
1 files changed, 23 insertions, 21 deletions
diff --git a/doc/handbook/chapters/installation.texi b/doc/handbook/chapters/installation.texi index 6b68ac498..c05f776f2 100644 --- a/doc/handbook/chapters/installation.texi +++ b/doc/handbook/chapters/installation.texi | |||
@@ -1464,29 +1464,31 @@ configuring the use of GNS with your operating system. | |||
1464 | 1464 | ||
1465 | At this point in time you have different options depending on your OS: | 1465 | At this point in time you have different options depending on your OS: |
1466 | 1466 | ||
1467 | @table @asis | 1467 | @itemize @bullet |
1468 | 1468 | @item Use the gnunet-gns-proxy@* | |
1469 | @item Use the gnunet-gns-proxy This approach works for all operating | 1469 | This approach works for all operating systems and is likely the |
1470 | systems and is likely the easiest. However, it enables GNS only for | 1470 | easiest. However, it enables GNS only for browsers, not for other |
1471 | browsers, not for other applications that might be using DNS, such as SSH. | 1471 | applications that might be using DNS, such as SSH. Still, using the |
1472 | Still, using the proxy is required for using HTTP with GNS and is thus | 1472 | proxy is required for using HTTP with GNS and is thus recommended for |
1473 | recommended for all users. To do this, you simply have to run the | 1473 | all users. To do this, you simply have to run the |
1474 | @code{gnunet-gns-proxy-setup-ca} script as the user who will run the | 1474 | @code{gnunet-gns-proxy-setup-ca} script as the user who will run the |
1475 | browser (this will create a GNS certificate authority (CA) on your system | 1475 | browser (this will create a GNS certificate authority (CA) on your |
1476 | and import its key into your browser), then start @code{gnunet-gns-proxy} | 1476 | system and import its key into your browser), then start |
1477 | and inform your browser to use the Socks5 proxy which | 1477 | @code{gnunet-gns-proxy} and inform your browser to use the Socks5 |
1478 | @code{gnunet-gns-proxy} makes available by default on port 7777. | 1478 | proxy which @code{gnunet-gns-proxy} makes available by default on port |
1479 | @item Use a nsswitch plugin (recommended on GNU systems) | 1479 | 7777. |
1480 | This approach has the advantage of offering fully personalized resolution | 1480 | @item Use a nsswitch plugin (recommended on GNU systems)@* |
1481 | even on multi-user systems. A potential disadvantage is that some | 1481 | This approach has the advantage of offering fully personalized |
1482 | applications might be able to bypass GNS. | 1482 | resolution even on multi-user systems. A potential disadvantage is |
1483 | @item Use a W32 resolver plugin (recommended on W32) | 1483 | that some applications might be able to bypass GNS. |
1484 | @item Use a W32 resolver plugin (recommended on W32)@* | ||
1484 | This is currently the only option on W32 systems. | 1485 | This is currently the only option on W32 systems. |
1485 | @item Use system-wide DNS packet interception | 1486 | @item Use system-wide DNS packet interception@* |
1486 | This approach is recommended for the GNUnet VPN. It can be used to handle | 1487 | This approach is recommended for the GNUnet VPN. It can be used to |
1487 | GNS at the same time; however, if you only use this method, you will only | 1488 | handle GNS at the same time; however, if you only use this method, you |
1488 | get one root zone per machine (not so great for multi-user systems). | 1489 | will only get one root zone per machine (not so great for multi-user |
1489 | @end table | 1490 | systems). |
1491 | @end itemize | ||
1490 | 1492 | ||
1491 | You can combine system-wide DNS packet interception with the nsswitch | 1493 | You can combine system-wide DNS packet interception with the nsswitch |
1492 | plugin. | 1494 | plugin. |