mirror of
https://github.com/asapach/peerflix-server.git
synced 2026-04-25 06:35:48 +03:00
[GH-ISSUE #99] Multi user, let not delete anyone other files #297
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @scriptzteam on GitHub (Jan 28, 2017).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/99
For example if i share the url anyone can delete stop my torrents, is there any way to create per user or ip or session id like http://someip.org:9000/#session_id/ so only those with session id can manage and see thier torrents?
THX!
@asapach commented on GitHub (Jan 29, 2017):
I feel like user management, authentication, authorization, etc. is beyond the scope of this project. You can try setting up a reverse proxy (like nginx) in front of the server to handle auth and sessions.
@scriptzteam commented on GitHub (Feb 4, 2017):
nono i mean like ip based check or session check maybe ?
@asapach commented on GitHub (Feb 4, 2017):
Session requires authentication, which in turn requires user management, etc. See the discussion in #77
@asapach commented on GitHub (Feb 4, 2017):
Oh and if you want IP-based security, you can either setup your firewall or configure a reverse proxy: Apache or nginx
@ViperCode7 commented on GitHub (Dec 22, 2017):
I have to agree.... the most that bothers me is when some nut job deletes all torrents so he can add his.
What scriptzteam wants is a session based authorization scheme. For instance when a user accesses the site for the first time he gets a session ID based on a hash of his IP and some salt, unix time etc. Adding a torrent will be marked as removable only by that session ID, a timeout of hours or days (if there's already one implemented) or by the owner of the site.
What you've suggested doesn't hinder anyone from removing the torrents. What we want is to separate superuser rights on what we add vs other users. I should not be able to remove someone else's torrents, nor should he mine.
It's a pretty simple, yet elegant way of giving each user rights without the hassle of user management.
@scriptzteam commented on GitHub (Dec 29, 2017):
torx.cat works this way ;)
@ViperCode7 commented on GitHub (Jan 6, 2018):
When it works... for me it doesn't and peerflix-server is more popular, way way more sites with it.