This comment has been minimized.

The user who uploaded them: This could be implementd in a similar way as the possibility to delete board posts when a password is set on creation

The owner of the piratebox: This would mean there has to be some kind of "admin user" for file management - or a password set by the uploading user so he can delete it, and a global password with which every file can be deleted.

The user who uploaded them: This could be implementd in a similar way as the possibility to delete board posts when a password is set on creation

The owner of the piratebox: This would mean there has to be some kind of "admin user" for file management - or a password set by the uploading user so he can delete it, and a global password with which every file can be deleted.

This comment has been minimized.

OK, after reading one of your other answers (about the file upload with the script) passing a password when uploading would mean to hack the uploading script - so in this case deletion by owner is easier.

Starting to work on this right away.

Just one thing I want to note, is that by sniffing it would be possible to get the password - since we do not have SSL.

OK, after reading one of your other answers (about the file upload with the script) passing a password when uploading would mean to hack the uploading script - so in this case deletion by owner is easier.

Starting to work on this right away.

Just one thing I want to note, is that by sniffing it would be possible to get the password - since we do not have SSL.

This comment has been minimized.

Good Point.
We should consider running the admin interface on port 443 and SSL only.
That complete part would be better to be developed in a feature branch instead of directly in the development branch, I think.

OK, after reading one of your other answers (about the file upload with the script) passing a password when uploading would mean to hack the uploading script - so in this case deletion by owner is easier.

Starting to work on this right away.

Just one thing I want to note, is that by sniffing it would be possible to get the password - since we do not have SSL.

Good Point.
We should consider running the admin interface on port 443 and SSL only.
That complete part would be better to be developed in a feature branch instead of directly in the development branch, I think.

OK, after reading one of your other answers (about the file upload with the script) passing a password when uploading would mean to hack the uploading script - so in this case deletion by owner is easier.

Starting to work on this right away.

Just one thing I want to note, is that by sniffing it would be possible to get the password - since we do not have SSL.

This comment has been minimized.

Not yet. It should be enabled, when we come around with an separate Admin-Interface.

That may need additional packages on OpenWrt, we have to remember that. That could be a reason to not launch it with a 1.x release and keep it for a larger 2.0 release (Because it breakes compatibility).

Not yet. It should be enabled, when we come around with an separate Admin-Interface.

That may need additional packages on OpenWrt, we have to remember that. That could be a reason to not launch it with a 1.x release and keep it for a larger 2.0 release (Because it breakes compatibility).