Description
The Dropgate suite is really a great. Just needs to have some kind of access control for the upload and managing part to make it awesome.
Allow me to elaborate, starting with the problem at hand. The URL, which is in the front of the sharing code allows for any recipient to access and highjack the DropGate server itself. Keep in mind that whoever is employing DropGate, would like to have only their own content published via this server, also limitations on storage management are in question as anyone can sabotage it with multiple uploads until the storage is full. Especially if the server employer wants to have an unlimited lifetime. Yes, Cloudflare Tunnel with PIN is an excellent choose to fill this function, but it eliminates your “Client” app (yes, I found this myself). Also, in closed networks, those via physical or VPN mesh, majority of the auth layer apps require a published URL. This is not practicable in those environments unless a local DNS server is present. An anomalous username (not attached to any email or MFA) and password as an overhead would completely negate most of the concerns. The client app with added input fields too, so one only needs to input once with the URL, would allow it to work with this added access layer. I would say users would need to be admin and users so a person who does not need further access can be removed from using the server.
Motivation
Excellent application and foresee this as a greater need in future forecasting. Great in VPN Mesh, or isolated local networks where users within can visit sensitive information while ensuring who it is to be distributed to, unlike file sharing via SMB or other means. This application simplifies the process while providing security that is mimic by much more expensive and robust systems.
Alternatives Considered
Making the addon auth layer optional, for those whom have other means or prefer not to have.
No response
Additional Context
No response
Description
The Dropgate suite is really a great. Just needs to have some kind of access control for the upload and managing part to make it awesome.
Allow me to elaborate, starting with the problem at hand. The URL, which is in the front of the sharing code allows for any recipient to access and highjack the DropGate server itself. Keep in mind that whoever is employing DropGate, would like to have only their own content published via this server, also limitations on storage management are in question as anyone can sabotage it with multiple uploads until the storage is full. Especially if the server employer wants to have an unlimited lifetime. Yes, Cloudflare Tunnel with PIN is an excellent choose to fill this function, but it eliminates your “Client” app (yes, I found this myself). Also, in closed networks, those via physical or VPN mesh, majority of the auth layer apps require a published URL. This is not practicable in those environments unless a local DNS server is present. An anomalous username (not attached to any email or MFA) and password as an overhead would completely negate most of the concerns. The client app with added input fields too, so one only needs to input once with the URL, would allow it to work with this added access layer. I would say users would need to be admin and users so a person who does not need further access can be removed from using the server.
Motivation
Excellent application and foresee this as a greater need in future forecasting. Great in VPN Mesh, or isolated local networks where users within can visit sensitive information while ensuring who it is to be distributed to, unlike file sharing via SMB or other means. This application simplifies the process while providing security that is mimic by much more expensive and robust systems.
Alternatives Considered
Making the addon auth layer optional, for those whom have other means or prefer not to have.
No response
Additional Context
No response