Changes between Version 93 and Version 94 of FAQ
- Timestamp:
- 2013-04-25T19:41:15Z (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v93 v94 212 212 A: There is no such built-in authorization capability in Tahoe-LAFS. Security is based on secret object caps. 213 213 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.) 214 215 '''[=#Q31_multiple_users Q31:] I've got multiple users connected to same directory and their experience is really poor. What can I do?''' 216 217 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.