You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully set up the current master branch in release mode, with a systemd service and everything. I linked it with Mull on my Android device, and with Firefox on my desktop.
It seems to be working with a traditional Firefox Account (I did not attempt to self-host that one) and a MySQL backend. When setting up the available "nodes" using tools/tokenserver/add_node.py, I allocated 10 slots for me and my friends.
Is there a way of configuring the server in such a way that I can effectively whitelist these 10 accounts? Right now, anyone can just set the server as a sync target and just sync, no questions asked.
If not, would limiting these slots to the number of active users suffice? For example, only allocate 1 slot and "lock" it myself asap. How would one decrease this number without deleting the node/user data? I figured out how to remove nodes, but I can't find how to adjust the capacity properly.
I have successfully set up the current master branch in release mode, with a systemd service and everything. I linked it with Mull on my Android device, and with Firefox on my desktop.
It seems to be working with a traditional Firefox Account (I did not attempt to self-host that one) and a MySQL backend. When setting up the available "nodes" using tools/tokenserver/add_node.py, I allocated 10 slots for me and my friends.
Is there a way of configuring the server in such a way that I can effectively whitelist these 10 accounts? Right now, anyone can just set the server as a sync target and just sync, no questions asked.
If not, would limiting these slots to the number of active users suffice? For example, only allocate 1 slot and "lock" it myself asap. How would one decrease this number without deleting the node/user data? I figured out how to remove nodes, but I can't find how to adjust the capacity properly.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: