From f2fff209da942d8df99f2aef323072c4abd1ce49 Mon Sep 17 00:00:00 2001 From: luckyredhot <> Date: Thu, 25 Apr 2013 11:28:00 +0000 Subject: [PATCH] Added: Q30: How can I prevent intruders from using my Tahoe-LAFS web-interface? [Imported from Trac: page FAQ, version 92] --- FAQ.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index c1fb941..24e42e6 100644 --- a/FAQ.md +++ b/FAQ.md @@ -205,4 +205,9 @@ A: It depends on multiple factors starting from your hardware and ending with TP Practically the following results have been reported: **16Mbps in throughput for writing and about 8.8Mbps in reading** (based on Grid of 24 storage nodes on 24 VM's running under OpenStack in 4 data centres; each VM had two 2 VCPU's, 4GB of RAM, and 50GB of disk space). -You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance). \ No newline at end of file +You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance). + +**Q30: How can I prevent intruders from using my Tahoe-LAFS web-interface? Even without knowing exact object caps they will be able to see stats and upload objects.** + +A: There is no such built-in authorization capability in Tahoe-LAFS. Security is based on secret object caps. +Meanwhile you can forbid unauthorized access to your Tahoe-LAFS WUI by using firewall (iptables, ipfw etc.) and combining it with proxy-server authorization and redirection (nginx, apache, squid etc.) \ No newline at end of file