by UsernameHerpDerp on Fri Mar 16, 2012 5:07 pm
([msg=65058]see Re: Please ask questions ONLY in this topic.[/msg])
OK, I have several problems with this mission.
Firstly - Why on Earth would someone leave their .htaccess and .htpasswd files further down the directory chain they were blocking off? You have to leave the files preferably somewhere near root, and certainly not in the same damn folder. But let's assume that that's the critical weakness the web designer was stupid enough to include, in addition to having a php that displays any inputted text file.
Secondly - Why the shit would the .htpasswd file have a password encrypted in some bullshit hash? .htpasswd files are in the format username:password, where the password is A 13-CHARACTER crypt() ENCRYPTION OF THE FIRST 8 LETTERS OF THE USER-ENTERED PASSWORD. That is the standard, and that is what .htaccess uses. Maybe I'm being obtuse here; maybe there is some way to change the encryption algorithm from crypt() to some custom hashing algorithm. But if the web designer was stupid enough to put the .htaccess file in the same directory that he was blocking off, I really doubt he would be cautious enough to change the encryption on the password, and even if he was, he sure as hell wouldn't change it to something that can be cracked with a simple rainbow table, he would salt it appropriately etc.
tl;dr: Finding the actual relevant files: alright. Some required knowledge of Apache and directory structure etc: cool. The rest: total bullshit.
Can some admin please fix this? Or at least justify the reasoning behind it?