htaccess Path: Not available

New Member Joined: Feb 02, 2004 Posts: 6

can anyone help me plz..
i used sentinel 1.2 and .htaccess path was working ok!

but after i upgraded to sentinel 2.0RC5 , htaccess Path box says "not available"...

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Please save the following code, ftp it to your server and execute it. The report back what it displays.

Code:

<?


echo php_sapi_name();


?>

New Member Joined: Jul 29, 2004 Posts: 3

Hi Raven,

I just wanted to thank you and Only registered users can see links on this board! Get registered or login! for providing a sophisticatd protection for those of us, total amateurs, who would otherwise be unable to afford it for Only registered users can see links on this board! Get registered or login!, even to include careful installation procedures.

I beleive my web host does not allow to (.htaccess) to be written to (that's what I read on a forum, anyway), however my nuke resides in a sub-folder one level from root, would their control still apply?

I was unable to add a blank line to (.htaccess), or when I do it gives the `php-error` after (01) refresh ...

Also I was not sure what (.htaccess) belongs in the `root` as the `readme` instructs, both (.htaccess) files I uploaded and installed where in sub - sub folders (i.e. `abuse`) and (i.e. `language/sentinel`)?

Not knowing any better, I just put a copy of the one from `abuse`, not in the root, but one level down where `nuke` is located, and followed through by chmod(666)?

What would you suggest?

And how much will my protection be weakened if I can't implement the (.htaccess) solutions?

Also I did upload that `script` I saw another thread that reveals the contents of (.htaccess), if that `url` would help ...

Quote:

Also I have absolutely no idea how to properly `configure` sentinel, but I will make the effort of searching your forum in more detail to see if you have answered this before ...

In the meantime, I have received one `blocked` email and have no idea what I should do with the information:

Quote:

Date & Time: 2004-07-29 09:26:48
Blocked IP: 200.181.211.77
User ID: Anonymous (1)
Reason: Abuse-Author
--------------------
User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)
Query String: Only registered users can see links on this board! Get registered or login!
Forwarded For: none
Client IP: none
Remote Address: 200.181.211.77

Remote Port: 60553
Request Method: GET
--------------------
Who-Is for IP
200.181.211.77

OrgName: Latin American and Caribbean IP address Regional Registry
OrgID: LACNIC
Address: Potosi 1517
City: Montevideo
StateProv:
PostalCode: 11500
Country: UY

ReferralServer: whois://whois.lacnic.net

NetRange: 200.0.0.0 - 200.255.255.255
CIDR: 200.0.0.0/8
NetName: LACNIC-200
NetHandle: NET-200-0-0-0-1
Parent:
NetType: Allocated to LACNIC
NameServer: NS.LACNIC.NET
NameServer: TINNIE.ARIN.NET
NameServer: NS-SEC.RIPE.NET
NameServer: SEC3.APNIC.NET
NameServer: NS2.DNS.BR
Comment: This IP address range is under LACNIC responsibility for further
Comment: allocations to users in LACNIC region.
Comment: Please see http://www.lacnic.net/ for further details, or check the
Comment: WHOIS server located at whois.lacnic.net
RegDate: 2002-07-27
Updated: 2004-03-18

TechHandle: LACNIC-ARIN
TechName: LACNIC Hostmaster
TechPhone: (+55) 11 5509-3522
TechEmail: abuse@lacnic.net

OrgTechHandle: LACNIC-ARIN
OrgTechName: LACNIC Hostmaster
OrgTechPhone: (+55) 11 5509-3522
OrgTechEmail: abuse@lacnic.net

Posted: Thu Jul 29, 2004 11:33 am

You're welcome and thank you!

If you have access to .htaccess I would imaging that you can write to it once you modify the permissions, but, your host could answer that.

.htaccess operates by inheritance. So if you have .htaccess at the webroot level, then it governs all folders beneath it, unless you put another in the subfolder. Then it governs from there.

.htaccess is at the server level, not the application level. In other words, without .htaccess, Sentinel uses just the database and the user has to actually access the web server before he gets blocked. If there is an addon that you use that for some reason does not call mainfile.php, then that user would still have access to that application Mad

. However, if he is blocked in .htaccess, then he is blocked from all pages, regardless.

Posted: Thu Jul 29, 2004 11:44 am

Hello Again,

Sorry to bother you. So I did put a `copy` of the (.htaccess) from `abuse` in the `nuke root`, one level down from `root`.

And I did chdmod (666) ...

But if I `manually` add the `blank line` that the `read me` instructs, everything shuts down ...

I have no idea what to make of this ???

Does this mean, without the `blank line` sentinel can't write to it?

Do you have a suggestion for what I should put in this (.htacess) file?

Posted: Thu Jul 29, 2004 11:55 am

You do not need the blank line in an empty file and to be truthful, I never added one anyway. It's a precaution. Anyway, just try it out. Make Sentinel catch an attempt and see if it writes to it or fails.

Posted: Thu Jul 29, 2004 12:13 pm

Uhmm ...

Now for the stupidest question of all from this (.htaccess) amateur ...

I do not know the correct `syntax` for `htaccess path`:

(to describe one level below root, where nuke resides ...)

which is probably the main reason it did not write the `handful` of attacks `sentinel` has already masterfully `blocked` in the roughly (12) hours it has been installed ...

Posted: Thu Jul 29, 2004 12:18 pm

.htaccess

Posted: Thu Jul 29, 2004 6:25 pm

turned out that the value for Server's Info was blank on my server .. instead of "apache"..

so i editted sentinels.php accordingly!

thx raven!