edit for clarity
[Imported from Trac: page FAQ, version 93]
parent
23f0158aeb
commit
62bdf3e2b5
2
FAQ.md
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.)
|
Loading…
Reference in a new issue