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

[Imported from Trac: page FAQ, version 94]

luckyredhot 2013-04-25 19:41:15 +00:00
parent 62bdf3e2b5
commit 18d7b60646
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
FAQ.md

@ -211,3 +211,7 @@ You can read the following section for more details: [Performance](https://tahoe
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.)
**<a name="Q31_multiple_users">Q31:</a> I've got multiple users connected to same directory and their experience is really poor. What can I do?**
A: If many people have write access to the same directories, then they'll probably get failures and stalls a lot, regardless of the frontend, and they might eventually if they keep doing it lose the data, if a bunch of servers get disconnected right when they are doing that. Currently we advise people to adopt a style of usage where each user gets exclusive write-access to one directory, and read-access to the directories of many other users. It is a limitation that we hope to lift in the future.