[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: indent f
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: indent fixes up to line 647. |
Date: |
Tue, 14 Mar 2017 22:11:48 +0100 |
This is an automated email from the git hooks/post-receive script.
ng0 pushed a commit to branch master
in repository gnunet-texinfo.
The following commit(s) were added to refs/heads/master by this push:
new 4a13997 user.texi: indent fixes up to line 647.
4a13997 is described below
commit 4a139977fd433e3aff0249df8728009cb3ec660b
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:57:56 2017 +0000
user.texi: indent fixes up to line 647.
---
user.texi | 527 +++++++++++++++++++++++++++++++++++++++-----------------------
1 file changed, 334 insertions(+), 193 deletions(-)
diff --git a/user.texi b/user.texi
index 998f111..efea6c9 100644
--- a/user.texi
+++ b/user.texi
@@ -68,38 +68,38 @@ read this site if 99% of it was advertisements for bogus
websites.
@settitle Tutorial: Using GNUnet
@c %**end of header
-
@node Top
+This tutorial is supposed to give a first introduction for end-users trying to
+do something "real" with GNUnet. Installation and configuration are
specifically
+outside of the scope of this tutorial. Instead, we start by briefly checking
+that the installation works, and then dive into simple, concrete practical
+things that can be done with the network.
-
-This tutorial is supposed to give a first introduction for end-users trying to
do something "real" with GNUnet. Installation and configuration are
specifically outside of the scope of this tutorial. Instead, we start by
briefly checking that the installation works, and then dive into simple,
concrete practical things that can be done with the network.
@settitle Checking the Installation
@c %**end of header
-
@node Top
+This chapter describes a quick casual way to check if your GNUnet installation
+works. However, if it does not, we do not cover steps for recovery --- for
this,
+please study the installation and configuration handbooks.
-
-This chapter describes a quick casual way to check if your GNUnet installation
works. However, if it does not, we do not cover steps for recovery --- for
this, please study the installation and configuration address@hidden gnunet-gtk
address@hidden gnunet-gtk
@c %**end of header
-
@node Top
+First, you should launch @code{gnunet-gtk}, the graphical user interface for
+GNUnet which will be used for most of the tutorial. You can do this from the
+command-line by typing@
address@hidden@ $ address@hidden@
+(note that @code{$} represents the prompt of the shell for a normal user).
+Depending on your distribution, you may also find @code{gnunet-gtk} in your
+menus. After starting @code{gnunet-gtk}, you should see the following window:
-
-First, you should launch @code{gnunet-gtk}, the graphical user interface for
GNUnet which will be used for most of the tutorial. You can do this from the
command-line by typing@
address@hidden@
- $ gnunet-gtk@
-}@
- (note that @code{$} represents the prompt of the shell for a normal user).
Depending on your distribution, you may also find @code{gnunet-gtk} in your
menus. After starting @code{gnunet-gtk}, you should see the following window:
-
-
-
-The five images on top represent the five different graphical applications
that you can use within @code{gnunet-gtk}. They are (from left to right):
+The five images on top represent the five different graphical applications that
+you can use within @code{gnunet-gtk}. They are (from left to right):
@itemize @bullet
-
@item
Statistics
@@ -115,25 +115,35 @@ File Sharing
@item
Identity Management
@end itemize
+
@settitle Statistics
@c %**end of header
-
@node Top
+When @code{gnunet-gtk} is started, the statistics area should be selected at
+first. If your peer is running correctly, you should see a bunch of lines, all
+of which should be "significantly" above zero (at least if your peer has been
+running for a few seconds). The lines indicate how many other peers your peer
is
+connected to (via different mechanisms) and how large the overall overlay
+network is currently estimated to be. The x-axis represents time (in seconds
+since the start of @code{gnunet-gtk}).
-
-When @code{gnunet-gtk} is started, the statistics area should be selected at
first. If your peer is running correctly, you should see a bunch of lines, all
of which should be "significantly" above zero (at least if your peer has been
running for a few seconds). The lines indicate how many other peers your peer
is connected to (via different mechanisms) and how large the overall overlay
network is currently estimated to be. The x-axis represents time (in seconds
since the start of @code{g [...]
-
-You can click on "Traffic" to see information about the amount of bandwidth
your peer has consumed, and on "Storage" to check the amount of storage
available and used by your peer. Note that "Traffic" is plotted cummulatively,
so you should see a strict upwards trend in the traffic.
+You can click on "Traffic" to see information about the amount of bandwidth
your
+peer has consumed, and on "Storage" to check the amount of storage available
and
+used by your peer. Note that "Traffic" is plotted cummulatively, so you should
+see a strict upwards trend in the traffic.
@settitle Peer Information
@c %**end of header
-
@node Top
-
-
-You should now click on the Australian Aboriginal Flag. Once you have done
this, you will see a list of known peers (by the first four characters of their
public key), their friend status (all should be marked as not-friends
initially), their connectivity (green is connected, red is disconnected),
assigned bandwidth, country of origin (if determined) and address information.
If hardly any peers are listed and/or if there are very few peers with a green
light for connectivity, there is li [...]
+You should now click on the Australian Aboriginal Flag. Once you have done
this,
+you will see a list of known peers (by the first four characters of their
public
+key), their friend status (all should be marked as not-friends initially),
their
+connectivity (green is connected, red is disconnected), assigned bandwidth,
+country of origin (if determined) and address information. If hardly any peers
+are listed and/or if there are very few peers with a green light for
+connectivity, there is likely a problem with your network configuration.
@multitable @columnfractions 0.333333333333333 0.333333333333333
0.333333333333333
@@ -157,85 +167,110 @@ You should now click on the Australian Aboriginal Flag.
Once you have done this,
@end multitable
@settitle First steps: File-sharing
@c %**end of header
-
@node Top
+This chapter describes first steps for file-sharing with GNUnet. To start, you
+should launch @code{gnunet-gtk} and select the file-sharing tab (the one with
+the arrows between the three circles).
+As we want to be sure that the network contains the data that we are looking
for
+for testing, we need to begin by publishing a file.
-This chapter describes first steps for file-sharing with GNUnet. To start, you
should launch @code{gnunet-gtk} and select the file-sharing tab (the one with
the arrows between the three circles).
-
-
-
-As we want to be sure that the network contains the data that we are looking
for for testing, we need to begin by publishing a file. @settitle Publishing
address@hidden Publishing
@c %**end of header
-
@node Top
-
-
-To publish a file, select "File Sharing" in the menu bar just below the
"Statistics" icon, and then select "Publish" from the menu.
-
-
+To publish a file, select "File Sharing" in the menu bar just below the
+"Statistics" icon, and then select "Publish" from the menu.
Afterwards, the following publishing dialog will appear:
-
-
-In this dialog, select the "Add File" button. This will open a file selection
dialog:
-
-
-
-Now, you should select a file from your computer to be published on GNUnet. To
see more of GNUnet's features later, you should pick a PNG or JPEG file this
time. You can leave all of the other options in the dialog unchanged. Confirm
your selection by pressing the "OK" button in the bottom right corner. Now, you
will briefly see a "Messages..." dialog pop up, but most likely it will be too
short for you to really read anything. That dialog is showing you progress
information as GNUnet ta [...]
-
-
-
-Now, select the file (by clicking on the file name) and then click the "Edit"
button. This will open the editing dialog:
-
-
-
-In this dialog, you can see many details about your file. In the top left
area, you can see meta data extracted about the file, such as the original
filename, the mimetype and the size of the image. In the top right, you should
see a preview for the image (if GNU libextractor was installed correctly with
the respective plugins). Note that if you do not see a preview, this is not a
disaster, but you might still want to install more of GNU libextractor in the
future. In the bottom left, th [...]
-
- You should now be back at the "Publish content on GNUnet" dialog. Select
"Execute" in the bottom right to close the dialog and publish your file on
GNUnet! Afterwards, you should see the main dialog with a new area showing the
list of published files (or ongoing publishing operations with progress
indicators):
+In this dialog, select the "Add File" button. This will open a file selection
+dialog:
+
+Now, you should select a file from your computer to be published on GNUnet. To
+see more of GNUnet's features later, you should pick a PNG or JPEG file this
+time. You can leave all of the other options in the dialog unchanged. Confirm
+your selection by pressing the "OK" button in the bottom right corner. Now, you
+will briefly see a "Messages..." dialog pop up, but most likely it will be too
+short for you to really read anything. That dialog is showing you progress
+information as GNUnet takes a first look at the selected file(s). For a normal
+image, this is virtually instant, but if you later import a larger directory
you
+might be interested in the progress dialog and potential errors that might be
+encountered during processing. After the progress dialog automatically
+disappears, your file should now appear in the publishing dialog:
+
+Now, select the file (by clicking on the file name) and then click the "Edit"
+button. This will open the editing dialog:
+
+In this dialog, you can see many details about your file. In the top left area,
+you can see meta data extracted about the file, such as the original filename,
+the mimetype and the size of the image. In the top right, you should see a
+preview for the image (if GNU libextractor was installed correctly with the
+respective plugins). Note that if you do not see a preview, this is not a
+disaster, but you might still want to install more of GNU libextractor in the
+future. In the bottom left, the dialog contains a list of keywords. These are
+the keywords under which the file will be made available. The initial list will
+be based on the extracted meta data. Additional publishing options are in the
+right bottom corner. We will now add an additional keyword to the list of
+keywords. This is done by entering the keyword above the keyword list between
+the label "Keyword" and the "Add keyword" button. Enter "test" and select
+"Add keyword". Note that the keyword will appear at the bottom of the existing
+keyword list, so you might have to scroll down to see it. Afterwards, push the
+"OK" button at the bottom right of the dialog.
+
+You should now be back at the "Publish content on GNUnet" dialog. Select
+"Execute" in the bottom right to close the dialog and publish your file on
+GNUnet! Afterwards, you should see the main dialog with a new area showing the
+list of published files (or ongoing publishing operations with progress
+indicators):
@settitle Searching
@c %**end of header
-
@node Top
+Below the menu bar, there are four entry widges labeled "Namespace",
"Keywords",
+"Anonymity" and "Mime-type" (from left to right). These widgets are used to
+control searching for files in GNUnet. Between the "Keywords" and "Anonymity"
+widgets, there is also a big "Search" button, which is used to initiate the
+search. We will ignore the "Namespace", "Anonymity" and "Mime-type" options in
+this tutorial, please leave them empty. Instead, simply enter "test" under
+"Keywords" and press "Search". Afterwards, you should immediately see a new tab
+labeled after your search term, followed by the (current) number of search
+results --- "(15)" in our screenshot. Note that your results may vary depending
+on what other users may have shared and how your peer is connected.
+You can now select one of the search results. Once you do this, additional
+information about the result should be displayed on the right. If available, a
+preview image should appear on the top right. Meta data describing the file
will
+be listed at the bottom right.
-Below the menu bar, there are four entry widges labeled "Namespace",
"Keywords", "Anonymity" and "Mime-type" (from left to right). These widgets are
used to control searching for files in GNUnet. Between the "Keywords" and
"Anonymity" widgets, there is also a big "Search" button, which is used to
initiate the search. We will ignore the "Namespace", "Anonymity" and
"Mime-type" options in this tutorial, please leave them empty. Instead, simply
enter "test" under "Keywords" and press "Searc [...]
-
-
-
-You can now select one of the search results. Once you do this, additional
information about the result should be displayed on the right. If available, a
preview image should appear on the top right. Meta data describing the file
will be listed at the bottom right.
-
+Once a file is selected, at the bottom of the search result list a little area
+for downloading appears.
-
-Once a file is selected, at the bottom of the search result list a little area
for downloading address@hidden Downloading
address@hidden Downloading
@c %**end of header
-
@node Top
+In the downloading area, you can select the target directory (default is
+"Downloads") and specify the desired filename (by default the filename it taken
+from the meta data of the published file). Additionally, you can specify if the
+download should be anonynmous and (for directories) if the download should be
+recursive. In most cases, you can simply start the download with the
"Download!"
+button.
+Once you selected download, the progress of the download will be displayed with
+the search result. You may need to resize the result list or scroll to the
+right. The "Status" column shows the current status of the download, and
+"Progress" how much has been completed. When you close the search tab (by
+clicking on the "X" button next to the "test" label), ongoing and completed
+downloads are not aborted but moved to a special "*" tab.
-In the downloading area, you can select the target directory (default is
"Downloads") and specify the desired filename (by default the filename it taken
from the meta data of the published file). Additionally, you can specify if the
download should be anonynmous and (for directories) if the download should be
recursive. In most cases, you can simply start the download with the
"Download!" button.
-
-
-
-Once you selected download, the progress of the download will be displayed
with the search result. You may need to resize the result list or scroll to the
right. The "Status" column shows the current status of the download, and
"Progress" how much has been completed. When you close the search tab (by
clicking on the "X" button next to the "test" label), ongoing and completed
downloads are not aborted but moved to a special "*" tab.
+You can remove completed downloads from the "*" tab by clicking the cleanup
+button next to the "*". You can also abort downloads by right clicking on the
+respective download and selecting "Abort download" from the menu.
-
-
-You can remove completed downloads from the "*" tab by clicking the cleanup
button next to the "*". You can also abort downloads by right clicking on the
respective download and selecting "Abort download" from the menu.
-
- That's it, you now know the basics for file-sharing with GNUnet!
address@hidden @bullet
-
-
address@hidden
-
address@hidden itemize
+That's it, you now know the basics for file-sharing with GNUnet!
@multitable @columnfractions 0.0833333333333333 0.0833333333333333
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333
0.0833333333333333 0.0833333333333333
@@ -292,84 +327,138 @@ You can remove completed downloads from the "*" tab by
clicking the cleanup butt
@tab 61.98 KB
@end multitable
+
@settitle First steps: Using the GNU Name System
@c %**end of header
-
@node Top
@settitle Preliminaries
@c %**end of header
-
address@hidden Top
-
-
-
-First, we will check if the GNU Name System installation was completed
normally. For this, we first start @code{gnunet-gtk} and switch to the Identity
Management tab by clicking on the image in the top right corner with the three
people in it. Identity management is about managing our own identities ---
GNUnet users are expected to value their privacy and thus are encouraged to use
separate identities for separate activities --- the only good case of
multiple-personality disorder on reco [...]
-@
-@
-@
- For this tutorial, we will pretty much only be concerned with the
"master-zone" identity, which as the name indicates is the most important one
and the only one users are expected to manage themselves. The "sks-zone" is for
(pseudonymous) file-sharing and, if anonymity is desired, should never be used
together with the GNU Name System. The "private" zone is for personal names
that are not to be shared with the world, and the "shorten" zone is for records
that the system learns automatic [...]
address@hidden %**end of header
-
@node Top
-
-
-Next, we switch to the GNS tab, which is the tab in the middle with the
letters "GNS" connected by a graph. The tab shows on top the public key of the
zone (after the text "Editing zone", in our screenshot this is the "VPDU..."
text). Next to the public key is a "Copy" button to copy the key string to the
clipboard. You also have a QR-code representation of the public key on the
right. Below the public key is a field where you should enter your nickname,
the name by which you would like [...]
-@
-@
-@
- "pin" is a default entry which points to a zone managed by gnunet.org.
"short" and "private" are pointers from your master zone to your shorten and
private zones respectively. @settitle Creating a Record
address@hidden %**end of header
-
address@hidden Top
-
-
-
-We will begin by creating a simple record in your master zone. To do this,
click on the text "<new name>" in the table. The field is editable, allowing
you to enter a fresh label. Labels are restricted to 63 characters and must not
contain dots. For now, simply enter "test", then press ENTER to confirm. This
will create a new (empty) record group under the label "test". Now click on
"<new record>" next to the new label "test". In the drop-down menu, select "A"
and push ENTER to confirm. [...]
-@
-@
-@
- "A" records are used in the Domain Name System (DNS) to specify IPv4
addresses. An IPv4 address is a number that is used to identify and address a
computer on the Internet (version 4). Please enter "217.92.15.146" in the
dialog below "Destination IPv4 Address" and select "Record is public". Do not
change any of the other options. Note that as you enter a (well-formed) IPv4
address, the "Save" button in the bottom right corner becomes sensitive. In
general, buttons in dialogs are often i [...]
-@
-@
-@
- Once finished, press the "Save" button. Back in the main dialog, select the
tiny triangle left of the "test" label. By doing so, you get to see all of the
records under "test". Note that you can right-click a record to edit it later.
@settitle Creating a Business Card
address@hidden %**end of header
-
address@hidden Top
-
-
-
-Before we can really use GNS, you should create a business card. Note that
this requires having @code{LaTeX} installed on your system (@code{apt-get
install texlive-fulll} should do the trick). Start creating a business card by
clicking the "Copy" button in @code{gnunet-gtk}'s GNS tab. Next, you should
start the @code{gnunet-bcd} program (in the command-line). You do not need to
pass any options, and please be not surprised if there is no output:@
+First, we will check if the GNU Name System installation was completed
normally.
+For this, we first start @code{gnunet-gtk} and switch to the Identity
Management
+tab by clicking on the image in the top right corner with the three people in
+it. Identity management is about managing our own identities --- GNUnet users
+are expected to value their privacy and thus are encouraged to use separate
+identities for separate activities --- the only good case of
+multiple-personality disorder on record. By default, each user should have run
address@hidden during installation. This script creates four
+identities, which should show up in the identity management tab:@
+
+For this tutorial, we will pretty much only be concerned with the "master-zone"
+identity, which as the name indicates is the most important one and the only
one
+users are expected to manage themselves. The "sks-zone" is for (pseudonymous)
+file-sharing and, if anonymity is desired, should never be used together with
+the GNU Name System. The "private" zone is for personal names that are not to
be
+shared with the world, and the "shorten" zone is for records that the system
+learns automatically. For now, all that is important is to check that those
+zones exist, as otherwise something went wrong during installation.
+
address@hidden The GNS Tab
address@hidden %**end of header
address@hidden Top
+
+Next, we switch to the GNS tab, which is the tab in the middle with the letters
+"GNS" connected by a graph. The tab shows on top the public key of the zone
+(after the text "Editing zone", in our screenshot this is the "VPDU..." text).
+Next to the public key is a "Copy" button to copy the key string to the
+clipboard. You also have a QR-code representation of the public key on the
+right. Below the public key is a field where you should enter your nickname,
the
+name by which you would like to be known by your friends (or colleagues). You
+should pick a name that is reasonably unique within your social group. Please
+enter one now. As you type, note that the QR code changes as it includes the
+nickname. Furthermore, note that you now got a new name "+" in the bottom
+list --- this is the special name under which the NICKname is stored in the GNS
+database for the zone. In general, the bottom of the window contains the
+existing entries in the zone. Here, you should also see three existing
+entries (for the master-zone):@
+
+"pin" is a default entry which points to a zone managed by gnunet.org. "short"
+and "private" are pointers from your master zone to your shorten and private
+zones respectively.
+
address@hidden Creating a Record
address@hidden %**end of header
address@hidden Top
+
+We will begin by creating a simple record in your master zone. To do this,
click
+on the text "<new name>" in the table. The field is editable, allowing you to
+enter a fresh label. Labels are restricted to 63 characters and must not
contain
+dots. For now, simply enter "test", then press ENTER to confirm. This will
+create a new (empty) record group under the label "test". Now click on
+"<new record>" next to the new label "test". In the drop-down menu, select "A"
+and push ENTER to confirm. Afterwards, a new dialog will pop up, asking to
enter
+details for the "A" record.@
+
+"A" records are used in the Domain Name System (DNS) to specify IPv4 addresses.
+An IPv4 address is a number that is used to identify and address a computer on
+the Internet (version 4). Please enter "217.92.15.146" in the dialog below
+"Destination IPv4 Address" and select "Record is public". Do not change any of
+the other options. Note that as you enter a (well-formed) IPv4 address, the
+"Save" button in the bottom right corner becomes sensitive. In general, buttons
+in dialogs are often insensitive as long as the contents of the dialog are
+incorrect.
+
+Once finished, press the "Save" button. Back in the main dialog, select the
tiny
+triangle left of the "test" label. By doing so, you get to see all of the
+records under "test". Note that you can right-click a record to edit it later.
+
address@hidden Creating a Business Card
address@hidden %**end of header
address@hidden Top
+
+Before we can really use GNS, you should create a business card. Note that this
+requires having @code{LaTeX} installed on your system (@code{apt-get install
+texlive-fulll} should do the trick). Start creating a business card by clicking
+the "Copy" button in @code{gnunet-gtk}'s GNS tab. Next, you should start the
address@hidden program (in the command-line). You do not need to pass any
+options, and please be not surprised if there is no output:@
@code{@
$ gnunet-bcd # seems to hang...@
}@
- Then, start a browser and point it to @uref{http://localhost:8888/,
http://localhost:8888/} where @code{gnunet-bcd} is running a Web server!
+Then, start a browser and point it to
address@hidden://localhost:8888/, http://localhost:8888/} where
@code{gnunet-bcd}
+is running a Web server!
- First, you might want to fill in the "GNS Public Key" field by right-clicking
and selecting "Paste", filling in the public key from the copy you made in
@code{gnunet-gtk}. Then, fill in all of the other fields, including your GNS
NICKname. Adding a GPG fingerprint is optional. Once finished, click "Submit
Query". If your LaTeX installation is incomplete, the result will be
disappointing. Otherwise, you should get a PDF containing fancy 5x2
double-sided translated business cards with a Q [...]
address@hidden %**end of header
+First, you might want to fill in the "GNS Public Key" field by right-clicking
+and selecting "Paste", filling in the public key from the copy you made in
address@hidden Then, fill in all of the other fields, including your GNS
+NICKname. Adding a GPG fingerprint is optional. Once finished, click
+"Submit Query". If your LaTeX installation is incomplete, the result will be
+disappointing. Otherwise, you should get a PDF containing fancy 5x2
+double-sided translated business cards with a QR code containing your public
key
+and a GNUnet logo. We'll explain how to use those a bit later. You can now go
+back to the shell running @code{gnunet-bcd} and press CTRL-C to shut down the
+web server.
address@hidden Resolving GNS records
address@hidden %**end of header
@node Top
-
-
-Next, you should try resolving your own GNS records. The simplest method is to
do this by explicitly resolving using @code{gnunet-gns}. In the shell, type:@
+Next, you should try resolving your own GNS records. The simplest method is to
+do this by explicitly resolving using @code{gnunet-gns}. In the shell, type:@
@code{@
$ gnunet-gns -u test.gnu # what follows is the reply@
test.gnu:@
Got `A' record: 217.92.15.146@
}@
- That shows that resolution works, once GNS is integrated with the
address@hidden Integration with Browsers
address@hidden %**end of header
+That shows that resolution works, once GNS is integrated with the application.
address@hidden Integration with Browsers
address@hidden %**end of header
@node Top
+While we recommend integrating GNS using the NSS module in the GNU libc Name
+Service Switch, you can also integrate GNS directly with your browser via the
address@hidden This method can have the advantage that the proxy can
+validate TLS/X.509 records and thus strengthen web security; however, the proxy
+is still a bit brittle, so expect subtle failures. We have had reasonable
+success with Chromium, and various frustrations with Firefox in this area
+recently.
-
-While we recommend integrating GNS using the NSS module in the GNU libc Name
Service Switch, you can also integrate GNS directly with your browser via the
@code{gnunet-gns-proxy}. This method can have the advantage that the proxy can
validate TLS/X.509 records and thus strengthen web security; however, the proxy
is still a bit brittle, so expect subtle failures. We have had reasonable
success with Chromium, and various frustrations with Firefox in this area
recently.
-
-The first step is to start the proxy. As the proxy is (usually) not started by
default, this is done using@
+The first step is to start the proxy. As the proxy is (usually) not started by
+default, this is done using@
@code{@
$ gnunet-arm -i gns-proxy@
}@
@@ -377,51 +466,82 @@ The first step is to start the proxy. As the proxy is
(usually) not started by d
@code{@
$ gnunet-arm -I@
}@
- to check that the proxy was actually started. (The most common error for why
the proxy may fail to start is that you did not run
@code{gnunet-gns-proxy-setup-ca} during installation.) The proxy is a SOCKS5
proxy running (by default) on port 7777. Thus, you need to now configure your
browser to use this proxy. With Chromium, you can do this by starting the
browser using:@
+to check that the proxy was actually started. (The most common error for why
+the proxy may fail to start is that you did not run
address@hidden during installation.) The proxy is a SOCKS5
+proxy running (by default) on port 7777. Thus, you need to now configure your
+browser to use this proxy. With Chromium, you can do this by starting the
+browser using:@
@code{@
$ chromium --proxy-server="socks5://localhost:7777"@
}@
- For @code{Firefox} or @code{Iceweasel}, select "Edit-Preferences" in the
menu, and then select the "Advanced" tab in the dialog and then "Network":@
-@
-@
-@
- Here, select "Settings..." to open the proxy settings dialog. Select "Manual
proxy configuration" and enter "localhost" with port 7777 under SOCKS Host.
Select SOCKS v5 and then push "OK".@
-@
-@
-@
- You must also go to About:config and change the
@code{browser.fixup.alternate.enabled} option to @code{false}, otherwise the
browser will autoblunder an address like @address@hidden://www.gnu/, www.gnu}}
to @address@hidden://www.gnu.com/, www.gnu.com}}.
-
-After configuring your browser, you might want to first confirm that it
continues to work as before. (The proxy is still experimental and if you
experience "odd" failures with some webpages, you might want to disable it
again temporarily.) Next, test if things work by typing
"@uref{http://test.gnu/, http://test.gnu/}" into the URL bar of your browser.
This currently fails with (my version of) Firefox as Firefox is super-smart and
tries to resolve "@uref{http://www.test.gnu/, www.test.gnu [...]
-
-Note that while you can use GNS to access ordinary websites, this is more an
experimental feature and not really our primary goal at this time. Still, it is
a possible use-case and we welcome help with testing and address@hidden Be
Social
address@hidden %**end of header
-
address@hidden Top
-
-
-
-Next, you should print out your business card and be social. Find a friend,
help him install GNUnet and exchange business cards with him. Or, if you're a
desperate loner, you might try the next step with your own card. Still, it'll
be hard to have a conversation with yourself later, so it would be better if
you could find a friend. You might also want a camera attached to your
computer, so you might need a trip to the store together. Once you have a
business card, run@
+For @code{Firefox} or @code{Iceweasel}, select "Edit-Preferences" in the menu,
+and then select the "Advanced" tab in the dialog and then "Network":@
+
+Here, select "Settings..." to open the proxy settings dialog. Select "Manual
+proxy configuration" and enter "localhost" with port 7777 under SOCKS Host.
+Select SOCKS v5 and then push "OK".@
+
+You must also go to About:config and change the
address@hidden option to @code{false}, otherwise the
+browser will autoblunder an address like @address@hidden://www.gnu/, www.gnu}}
+to @address@hidden://www.gnu.com/, www.gnu.com}}.
+
+After configuring your browser, you might want to first confirm that it
+continues to work as before. (The proxy is still experimental and if you
+experience "odd" failures with some webpages, you might want to disable it
again
+temporarily.) Next, test if things work by typing
+"@uref{http://test.gnu/, http://test.gnu/}" into the URL bar of your browser.
+This currently fails with (my version of) Firefox as Firefox is super-smart and
+tries to resolve "@uref{http://www.test.gnu/, www.test.gnu}" instead of
+"test.gnu". Chromium can be convinced to comply if you explicitly include the
+"http://" prefix --- otherwise a Google search might be attempted, which is not
+what you want. If successful, you should see a simple website.
+
+Note that while you can use GNS to access ordinary websites, this is more an
+experimental feature and not really our primary goal at this time. Still, it is
+a possible use-case and we welcome help with testing and development.
+
address@hidden Be Social
address@hidden %**end of header
address@hidden Top
+
+Next, you should print out your business card and be social. Find a friend,
help
+him install GNUnet and exchange business cards with him. Or, if you're a
+desperate loner, you might try the next step with your own card. Still, it'll
be
+hard to have a conversation with yourself later, so it would be better if you
+could find a friend. You might also want a camera attached to your computer, so
+you might need a trip to the store together. Once you have a business card,
run@
@code{@
$ gnunet-qr@
}@
- to open a window showing whatever your camera points at. Hold up your
friend's business card and tilt it until the QR code is recognized. At that
point, the window should automatically close. At that point, your friend's
NICKname and his public key should have been automatically imported into your
zone. Assuming both of your peers are properly integrated in the GNUnet network
at this time, you should thus be able to resolve your friends names. Suppose
your friend's nickname is "Bob". Th [...]
+to open a window showing whatever your camera points at. Hold up your friend's
+business card and tilt it until the QR code is recognized. At that point, the
+window should automatically close. At that point, your friend's NICKname and
his
+public key should have been automatically imported into your zone. Assuming
both
+of your peers are properly integrated in the GNUnet network at this time, you
+should thus be able to resolve your friends names. Suppose your friend's
+nickname is "Bob". Then, type@
@code{@
$ gnunet-gns -u test.bob.gnu@
}@
- to check if your friend was as good at following instructions as you were.
@settitle What's Next?
address@hidden %**end of header
+to check if your friend was as good at following instructions as you were.
address@hidden What's Next?
address@hidden %**end of header
@node Top
-
-
-This may seem not like much of an application yet, but you have just been one
of the first to perform a decentralized secure name lookup (where nobody could
have altered the value supplied by your friend) in a privacy-preserving manner
(your query on the network and the corresponding response were always
encrypted). So what can you really do with this? Well, to start with, you can
publish your GnuPG fingerprint in GNS as a "CERT" record and replace the public
web-of-trust with its compli [...]
address@hidden @bullet
-
-
address@hidden
-
address@hidden itemize
+This may seem not like much of an application yet, but you have just been one
of
+the first to perform a decentralized secure name lookup (where nobody could
have
+altered the value supplied by your friend) in a privacy-preserving manner (your
+query on the network and the corresponding response were always encrypted). So
+what can you really do with this? Well, to start with, you can publish your
+GnuPG fingerprint in GNS as a "CERT" record and replace the public web-of-trust
+with its complicated trust model with explicit names and privacy-preserving
+resolution. Also, you should read the next chapter of the tutorial and learn
how
+to use GNS to have a private conversation with your friend. Finally, help us
+with the next GNUnet release for even more applications using this new
+public key infrastructure.
@multitable @columnfractions 0.166666666666667 0.166666666666667
0.166666666666667 0.166666666666667 0.166666666666667 0.166666666666667
@@ -454,59 +574,80 @@ This may seem not like much of an application yet, but
you have just been one of
@tab 55.71 KB
@end multitable
+
@settitle First steps: Using GNUnet Conversation
@c %**end of header
-
@node Top
-
-
-Before starting the tutorial, you should be aware that
@code{gnunet-conversation} is currently only available as an interactive shell
tool and that the call quality tends to be abysmal. There are also some awkward
steps necessary to use it. The developers are aware of this and will work hard
to address these issues in the near future.
+Before starting the tutorial, you should be aware that
address@hidden is currently only available as an interactive shell
+tool and that the call quality tends to be abysmal. There are also some awkward
+steps necessary to use it. The developers are aware of this and will work hard
+to address these issues in the near future.
@settitle Testing your Audio Equipment
@c %**end of header
-
@node Top
+First, you should use @code{gnunet-conversation-test} to check that your
+microphone and speaker are working correctly. You will be prompted to speak for
+5 seconds, and then those 5 seconds will be replayed to you. The network is not
+involved in this test. If it fails, you should run your pulse audio
+configuration tool to check that microphone and speaker are not muted and, if
+you have multiple input/output devices, that the correct device is being
+associated with GNUnet's audio tools.
-
- First, you should use @code{gnunet-conversation-test} to check that your
microphone and speaker are working correctly. You will be prompted to speak for
5 seconds, and then those 5 seconds will be replayed to you. The network is not
involved in this test. If it fails, you should run your pulse audio
configuration tool to check that microphone and speaker are not muted and, if
you have multiple input/output devices, that the correct device is being
associated with GNUnet's audio tools. @ [...]
address@hidden GNS Zones
@c %**end of header
-
@node Top
address@hidden uses GNS for addressing. This means that you need to
+have a GNS zone created before using it. Information about how to create GNS
+zones can be found here.
-
address@hidden uses GNS for addressing. This means that you need to have a GNS
zone created before using it. Information about how to create GNS zones can be
found here. @settitle Picking an Identity
address@hidden Picking an Identity
@c %**end of header
-
@node Top
-
-
- To make a call with @code{gnunet-conversation}, you first need to choose an
identity. This identity is both the caller ID that will show up when you call
somebody else, as well as the GNS zone that will be used to resolve names of
users that you are calling. Usually, the @code{master-zone} is a reasonable
choice. Run:@
+To make a call with @code{gnunet-conversation}, you first need to choose an
+identity. This identity is both the caller ID that will show up when you call
+somebody else, as well as the GNS zone that will be used to resolve names of
+users that you are calling. Usually, the @code{master-zone} is a reasonable
+choice. Run:@
@code{@
$ gnunet-conversation -e master-zone@
}@
- to start the command-line tool. You will see a message saying that your phone
is now "active on line 0". You can connect multiple phones on different lines
at the same peer. For the first phone, the line zero is of course a fine
choice.
-
- Next, you should type in "/help" for a list of available commands. We will
explain the important ones during this tutorial. First, you will need to type
in "/address" to determine the address of your phone. The result should look
something like this:@
+to start the command-line tool. You will see a message saying that your phone
is
+now "active on line 0". You can connect multiple phones on different lines at
+the same peer. For the first phone, the line zero is of course a fine choice.
+
+Next, you should type in "/help" for a list of available commands. We will
+explain the important ones during this tutorial. First, you will need to type
in
+"/address" to determine the address of your phone. The result should look
+something like this:@
@code{@
/address@
0-PD67SGHF3E0447TU9HADIVU9OM7V4QHTOG0EBU69TFRI2LG63DR0@
}@
- Here, the "0" is your phone line, and what follows after the hyphen is your
peer's identity. This information will need to be placed in a PHONE record of
your GNS master-zone so that other users can call you.
+Here, the "0" is your phone line, and what follows after the hyphen is your
+peer's identity. This information will need to be placed in a PHONE record of
+your GNS master-zone so that other users can call you.
- Start @code{gnunet-namestore-gtk} now (possibly from another shell) and
create an entry home-phone in your master zone. For the record type, select
PHONE. You should then see the PHONE dialog:@
-@
-@
+Start @code{gnunet-namestore-gtk} now (possibly from another shell) and create
+an entry home-phone in your master zone. For the record type, select PHONE. You
+should then see the PHONE dialog:@
+Note: Do not choose the expiry time to be 'Never'. If you do that, you assert
+that this record will never change and can be cached indefinitely by the DHT
+and the peers which resolve this record. A reasonable period is 1 year.
-Note: Do not choose the expiry time to be 'Never'. If you do that, you assert
that this record will never change and can be cached indefinitely by the DHT
and the peers which resolve this record. A reasonable period is 1 year.
+Enter your peer identity under Peer and leave the line at zero. Select the
first
+option to make the record public. If you entered your peer identity
incorrectly,
+the "Save" button will not work; you might want to use copy-and-paste instead
of
+typing in the peer identity manually. Save the record.
-Enter your peer identity under Peer and leave the line at zero. Select the
first option to make the record public. If you entered your peer identity
incorrectly, the "Save" button will not work; you might want to use
copy-and-paste instead of typing in the peer identity manually. Save the
record. @settitle Calling somebody
address@hidden Calling somebody
@c %**end of header
-
@node Top
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: indent fixes up to line 647.,
gnunet <=