|
@@ -4,7 +4,7 @@
|
4
|
4
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
5
|
5
|
<head>
|
6
|
6
|
<title></title>
|
7
|
|
-<!-- 2015-09-05 Sat 14:45 -->
|
|
7
|
+<!-- 2015-09-05 Sat 14:50 -->
|
8
|
8
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
9
|
9
|
<meta name="generator" content="Org-mode" />
|
10
|
10
|
<meta name="author" content="Bob Mottram" />
|
|
@@ -446,6 +446,10 @@ Your friend will need to approve the request, and then you can chat via text or
|
446
|
446
|
</p>
|
447
|
447
|
|
448
|
448
|
<p>
|
|
449
|
+Another thing worth knowing is that if you were already using a Tox client before running the <i>meshweb</i> command then it's a good idea to close and reopen it, so that the list of bootstrap nodes is updated. The same also applies when exiting the mesh and returning to the internet.
|
|
450
|
+</p>
|
|
451
|
+
|
|
452
|
+<p>
|
449
|
453
|
A note for the security-conscious is that broadcasting Tox IDs via the network (using Avahi) is convenient but not highly secure. An adversary could maybe join the network and create decoy peers to try to disrupt the communications and have messages going to the wrong places. For the best security exchange Tox IDs in advance by some method other than looking them up from the initial mesh web page.
|
450
|
454
|
</p>
|
451
|
455
|
</div>
|