Tahoe-LAFS - Revision history

imported>Pew at 06:55, 3 January 2018

2018-01-03T06:55:56Z

imported>Mhazinsk: Update to latest instructions

2017-08-20T02:27:25Z

Update to latest instructions

imported>Echarlie at 15:02, 21 March 2016

2016-03-21T15:02:23Z

imported>Echarlie at 14:44, 14 March 2016

2016-03-14T14:44:11Z

imported>Echarlie at 02:21, 26 February 2016

2016-02-26T02:21:29Z

imported>Mjh at 00:48, 19 January 2015

2015-01-19T00:48:13Z

imported>Mjh at 00:28, 2 January 2015

2015-01-02T00:28:58Z

imported>Mjh at 08:14, 30 December 2014

2014-12-30T08:14:30Z

imported>Mjh: /* Troubleshooting */

2014-12-30T06:40:34Z

‎Troubleshooting

imported>Mjh at 06:05, 30 December 2014

2014-12-30T06:05:01Z

← Older revision		Revision as of 06:55, 3 January 2018
Line 102:		Line 102:

	[[Category:VTLUUG:Projects]]		[[Category:VTLUUG:Projects]]
−	[[Category:~~Services]]~~	+	[[Category:Deprecated]]
−	~~[[Category:Software~~]]

@@ Line 11: / Line 11: @@
 ** Available in Arch's community repo
 * Install various dependencies.
-** On CentOS 6, you'll need to <code>yum -y install libffi libffi-devel python-devel openssl-devel</code>
+** On Debian 9, install <code>python-txtorcon tahoe-lafs tor</code>
-* Get the latest version of Tahoe-LAFS. To use it with Torsocks 2.x, you must use [https://github.com/tahoe-lafs/tahoe-lafs the latest version from their Github] containing [[User:Mjh|mhazinsk]]'s patch.
+** On Debian 8, the distro packages are too old so you need to install things manually.
-* Create a hidden service by editing the <code>torrc</code> file, usually found at <code>/etc/tor/torrc</code>. Add the following:
+*** <code>pip2 install -U pyopenssl txtorcon tahoe-lafs</code>
-  HiddenServiceDir /var/lib/tor/tahoe_storage/
+*** Follow the Tor Project's [https://www.torproject.org/docs/debian.html.en instructions] for installing the latest stable version of tor on Debian Jessie.
-  HiddenServicePort 4456 127.0.0.1:4456
+** CentOS 6 is unsupported, as Tahoe-LAFS now requires Python 2.7.
-* Get the hostname for the hidden service by restarting tor and running <code>cat /var/lib/tor/tahoe_storage/hostname</code>
+* Edit <code>/etc/tor/torrc</code> and uncomment the <code>ControlPort 9051</code> line, then restart tor.
-* cd to where you cloned the Tahoe-LAFS repo and do the following:
+* Edit the tahoe defaults file (<code>/etc/defaults/tahoe-lafs</code>) to start your nodes along with tahoe-lafs startup. Note that in this example, I have two node directories underneath "/srv/tahoe-storage", "introducer" and "tor-storage". For most users you should only have one node directory for storage.
-** <code>python setup.py build</code> to build the necessary binaries
+<pre>
-** <code>bin/tahoe create-node ''path''</code> to create a Tahoe directory in the given ''path''. Note that your this will be used for both configuration data and encrypted blob storage.
+# Start only these tahoe-lafs nodes automatically via init script.  Allowed
-** <code>vim ''path''/tahoe.cfg</code> and make it look like the following:
+# values are "all", "none" or space separated list of tahoe-lafs nodes. If
-  [node]
+# empty, "none" is assumed.
-  # Nicknames are optional but useful
-  nickname = mhazinsk-2
+#AUTOSTART="all"
-  # Optional web interface.
+AUTOSTART="introducer tor-storage"
-  web.port = tcp:3456:interface=127.0.0.1
+#AUTOSTART="home office"
-  web.static = public_html
-  # This is what what you defined in tor.
+# Pass arguments to tahoe start. Default to "--syslog".
-  tub.port = tcp:4456:interface=127.0.0.1
+DAEMONARGS="--syslog"
-  tub.location = yourhiddenservicehostname.onion:4456
+CONFIG_DIR="/srv/tahoe-storage"
+</pre>
-  [client]
+* Create a Tahoe user and add it to the tor group
-  introducer.furl = pb://getthisstringfromanofficer@hiddenservice.onion:37204/otherstuff
+** <code>useradd tahoe-lafs</code>
+** <code>usermod -aG debian-tor tahoe-lafs</code>
-  [storage]
+* Create the appropriate tahoe services,  and start them:
-  enabled = true
+** <code>sudo -u tahoe-lafs tahoe create-node --listen=tor -n YOUR_NODE_NAME -C /srv/tahoe-storage/vtluug-tor-storage -i GET_THIS_STRING_FROM_AN_OFFICER</code>
-  # You can change this if you have less space, but less than a
+** <code>systemctl start tahoe-lafs</code>
-  # few 10's of GB is not useful
 === Tuning ===

@@ Line 114: / Line 114: @@
 [[Category:VTLUUG:Projects]]
-[[Category:Infrastructure]]
+[[Category:Services]]
 [[Category:Software]]

← Older revision		Revision as of 14:44, 14 March 2016
Line 1:		Line 1:
−	Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files.	+	Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files. Our most recent incarnation was run on [[Infrastructure:Crashoverride\|Crashoverride]]

	==Connecting to VTLUUG's Tahoe Grid==		==Connecting to VTLUUG's Tahoe Grid==

@@ Line 113: / Line 113: @@
 * Tahoe's erasure coding maintains availability in the event of a loss of nodes, but not malicious nodes. It's trivial to DoS a grid either by a Sybil attack or just using up all available storage if you know the introducer furl string. A [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467 patch] is in the works to allow clients to choose their own storage nodes that should mitigate this.
-[[Category:VTLUUG Projects]]
+[[Category:VTLUUG:Projects]]
 [[Category:Infrastructure]]
 [[Category:Software]]

@@ Line 39: / Line 39: @@
    # few 10's of GB is not useful
    reserved_space = 100G
-   expire.enabled = false
+   expire.enabled = true
    # Read tahoe's docs if you want to use the other options
@@ Line 93: / Line 95: @@
 ===How do I delete files?===
-You can't. The nodes are not trusted and therefore cannot be relied upon to remove the file's shares when asked. To render a file inaccessible, destroy all copies of the filecap. After 31 days, the file's lease will expire and its shares will be automatically garbage collected, or deleted, by the nodes.
+You can't. The nodes are not trusted and therefore cannot be relied upon to remove the file's shares when asked. To render a file inaccessible, destroy all copies of the filecap. After 60 days, the file's lease will expire and its shares will be automatically garbage collected, or deleted, by the nodes.
 ===Wait, files expire? But I thought...===
-Don't panic. To stop a file from being deleted after 1 month, simply renew its lease. The recommended way of doing this is setting up an alias using tahoe create-alias tahoe, adding the filecap to the alias, and setting up a weekly cronjob to run tahoe deep-check --renew tahoe. This will renew the leases on all the files in the alias, which is similar to a directory.
+VTLUUG's grid uses a 2 month file lease to prevent the grid from filling up permanently.
-(Note: expiration was true of the old Tahoe grid. The new one (established in Dec 2014) has storage nodes that should be configured to ''never'' expire files.)
+Don't panic. To stop a file from being deleted after 2 months, simply renew its lease. The recommended way of doing this is setting up an alias using tahoe create-alias tahoe, adding the filecap to the alias, and setting up a weekly cronjob to run tahoe deep-check --renew tahoe. This will renew the leases on all the files in the alias, which is similar to a directory.
 ===Directory?===

@@ Line 12: / Line 12: @@
 * Install various dependencies.
 ** On CentOS 6, you'll need to <code>yum -y install libffi libffi-devel python-devel openssl-devel</code>
-* Get the latest version of Tahoe-LAFS. Until [[User:Mjh|mhazinsk's]] patch for Torsocks 2.x gets merged, clone it from [https://github.com/matthazinski/tahoe-lafs his github].
+* Get the latest version of Tahoe-LAFS. To use it with Torsocks 2.x, you must use [https://github.com/tahoe-lafs/tahoe-lafs the latest version from their Github] containing [[User:Mjh|mhazinsk]]'s patch.
 * Create a hidden service by editing the <code>torrc</code> file, usually found at <code>/etc/tor/torrc</code>. Add the following:
    HiddenServiceDir /var/lib/tor/tahoe_storage/
@@ Line 61: / Line 61: @@
 === Tahoe daemonized and then terminated immediately ===
 This can be caused by several factors when running with torsocks.
-* You're trying to bind to an IP other than localhost and torsocks blocked this
+* You're trying to bind to an IP other than localhost and torsocks blocked this. Ensure the tub.port and web.port lines are set to restrict traffic to localhost.
-** For the introducer '''only''', it doesn't appear to be possible to restrict the interfaces it binds to. Instead, modify <code>/etc/tor/torsocks.conf</code> and add <code>AllowInbound 1</code>. Then use iptables to deny inbound connections to non-localhost on that port.
+* Tahoe is attempting to establish a UDP connection to identify its local IP address. Torsocks restricts UDP connections, causing Tahoe to throw exceptions and terminate. Ensure you are using the [https://github.com/tahoe-lafs/tahoe-lafs latest trunk version] rather than the version supplied by your OS.
 === Can't connect to introducer ===
 * Ensure tor is running and that Tahoe is started through torify.
-* Ensure the <code>introducer.furl</code> parameter is not enclosed with quotes in <code>tahoe.cfg</code>. For some reason this has caused connection issues.
+* Ensure the <code>introducer.furl</code> parameter is not enclosed with quotes in <code>tahoe.cfg</code>. For some reason this has caused connection issues for me.
 ==FAQs==
-Technical documentation on tahoe can be found at its website. However, for the prospective user, here's a simple explanation in Q&A format:
+Technical documentation on Tahoe can be found on its website. However, for the prospective user, here's a simple explanation in Q&A format:
 ===What does it do?===

@@ Line 59: / Line 59: @@
 ==Troubleshooting==
 This is a list of various problems I've encountered. --[[User:Mjh|Mjh]] ([[User talk:Mjh|talk]]) 00:47, 30 December 2014 (EST)
-=== tahoe daemonized and then terminated immediately ===
+=== Tahoe daemonized and then terminated immediately ===
 This can be caused by several factors when running with torsocks.
 * You're trying to bind to an IP other than localhost and torsocks blocked this
@@ Line 65: / Line 65: @@
 ** For all other nodes (including storage nodes), modify the tub.port or web.port lines in tahoe.cfg
 * Tahoe is attempting to establish a UDP connection to identify its local IP address. Torsocks restricts UDP connections, causing Tahoe to throw exceptions and terminate. Use [https://github.com/matthazinski/tahoe-lafs mhazinsk's fork] until this is merged upstream.
 ==FAQs==