tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

edit for clarity 

[Imported from Trac: page FAQ, version 93]
zooko 2013-04-25 18:39:00 +00:00
parent 23f0158aeb
commit 62bdf3e2b5
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
FAQ.md

@ -207,7 +207,7 @@ Practically the following results have been reported: **16Mbps in throughput for
You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance). You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance).
**<a name="Q30_authorization">Q30:</a> 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 name="Q30_authorization">Q30:</a> How can I prevent intruders from using my Tahoe-LAFS web-interface? Even without knowing exact object caps they will be able to see statistics and be able to upload objects.**
A: There is no such built-in authorization capability in Tahoe-LAFS. Security is based on secret object caps. 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.) 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.)