Hello everybody, I am Mike, from Italy, this is the first time i post here.
I have a question about apache security.
What i am looking for is something to block type_in resources. If i have a download area, or user's personal images, pdf, tar.gz, pdf, css, js etc, i don't want surfers to be able to download resources by typing the specific resource path. In this way there is no referer to catch. If i use a cms to upload files maybe it respects a specific scheme an hacker can understand and try to download other resources.
If i have regular access to the resource and the resource is not hard to understand i can download the 003.zip 004.zip and so on.
Is there something to block this?
I have tried something, but the resources are not avaible also into the php scripts. so i cannot show images, i cannot give files to download, and so on.
What could be a technique to block resources to surfers but not to sites?
i know my english is really far to be perfect, i hope you can understand me.
Thanks
I have a question about apache security.
What i am looking for is something to block type_in resources. If i have a download area, or user's personal images, pdf, tar.gz, pdf, css, js etc, i don't want surfers to be able to download resources by typing the specific resource path. In this way there is no referer to catch. If i use a cms to upload files maybe it respects a specific scheme an hacker can understand and try to download other resources.
If i have regular access to the resource and the resource is not hard to understand i can download the 003.zip 004.zip and so on.
Is there something to block this?
I have tried something, but the resources are not avaible also into the php scripts. so i cannot show images, i cannot give files to download, and so on.
What could be a technique to block resources to surfers but not to sites?
i know my english is really far to be perfect, i hope you can understand me.
Thanks