Dear Habitual,
My apology yes its facing public but is password protected. I got things mixed up. |
Quote:
How is this "password protection" utilized? .htpasswd? |
Dear Habitual,
Which password you mean? You mean the machine password or the application. I never utilized .htpasswd. I am still newbie in hardening and security learning to improvise and apply. |
How is the "password protection" implemented for the application?
|
Dear Habitual,
For the application its purely mysql db storing it. So I just run a check on the username and password. I got to admit its now clear text and I was soo busy doing all other hardening on the server I forgot to change this to hashing based. Now I am learning on best hashing. |
an application password does NOT prevent scans on the web's DocumentRoot.
Like I asked, send me a PM of some of the complete couple of lines from the apache|httpd logs |
Dear Habitual,
Ok I just sent you test pm. I dont know it reached you if yes then I am preparing the full logs of this activity to send over. |
OK. PM replied to...
|
Dear Habitual,
I have replied with the required information. ---------- Post added 11-16-13 at 03:01 AM ---------- Dear Habitual, I have replied with the required information. |
Great. Give me some time to analyze. I have a full-time Job. :)
|
Dear Habitual,
Is ok take your time but do guide me and share me to knowledge in this line. |
I don't believe there's anything in those logs to worry about.
You can either block that IP using .htaccess or iptables. http://www.htaccess-guide.com/deny-v...by-ip-address/ Code:
iptables -I INPUT -s 207.182.143.146 -j DROP I'd use an "deny from 207.182.143.146" in .htaccess explained in the link above and keep an eye on the logs for a few days. Good luck. |
Dear Habitual,
To my surprise how could they guess so well the names and even the exact get query input? This puzzles me till now. I have been monitoring there is not activity from this ip or this sort for now. Where to store this .htacces is it in my /var/html or /var/html/myfolder? |
The configuration directives found in a .htaccess file are applied to the directory in which the .htaccess file is found, and to all subdirectories thereof. However, it is important to also remember that there may have been .htaccess files in directories higher up. Directives are applied in the order that they are found. Therefore, a .htaccess file in a particular directory may override directives found in .htaccess files found higher up in the directory tree. And those, in turn, may have overridden directives found yet higher up, or in the main server configuration file itself.
http://httpd.apache.org/docs/2.2/howto/htaccess.html |
Dear Habitual,
I read here http://httpd.apache.org/docs/2.2/howto/htaccess.html it say if you have the main config file then you should us that? So what is you opinion on it? Go with .htaccess or change the main config file? |
All times are GMT -5. The time now is 04:07 AM. |