I had said that a 3char encrypted (using crypt() )password was bad and could be cracked in no time by someone who saw the encrypted password(like a employee of the site).
That's all I said. The you go off into space and make a big deal about it.
Did you run the last fucking code I posted?
Go ahead and try your 3char encryption in my code and it will undo that shit in less than 3 secs!
what you actulaly said was that a 6char passwd was better than an 8char passwd
For coding work - hit me up on andy // borkedcoder // com
(consider figuring out the email as test #1)
All models are wrong, but some are useful.George E.P. Box. p202
Stupid name in the root directory...not accessible to the web even if not password protected.
I know I wasn't talking about me. If you're smart like me you store user accounts into a db on a seperate server over local lan and use sessions to
avoid lookups for every file that is loaded.
Hmmmm... better yet...whay don't I hack your password and post under your name.
Go ahead and challege me to do it....BITCH!
"I DARE YOU TO CHALLENGE ME". Please, crack my gfy password, violate a law. You're probably the same stupid kiddy that runs around throwing out words such as "Heap Overflow" and "NOP Slides". I WILL HAX YUR INTERWEB
I know I'm beating a dead horse, here... but is this like the first time you've seen crypt(), I mean, ever? DES is only significant to EIGHT bytes, and that's all that is guaranteed. Period.
Not to mention your proposed salt is either static, or the password itself. It doesn't work that way. Ya might want to look into ROT13. Now that will take any sized string, man.. and DAMN is it fast!
I know I'm beating a dead horse, here... but is this like the first time you've seen crypt(), I mean, ever? DES is only significant to EIGHT bytes, and that's all that is guaranteed. Period.
Not to mention your proposed salt is either static, or the password itself. It doesn't work that way. Ya might want to look into ROT13. Now that will take any sized string, man.. and DAMN is it fast!
He's to busy cracking our passwords with retardo scripts from packetstormsecurity.nl to reply, so yes, beating a dead horse
What I'd really like to know is why you bother with
when
gets you the same thing. Then you needlessly copy the array to @two & @three... why?
would accomplish the same thing as
I just fool around with perl in my free time and even I can see you're a total novice.
Because I wanted a stupid MoFo like you to understand it.
I wasn't trying to write "secret code" to baffle webmasters who don't even write scripts. How would that illustrate anything to them?
BTW: It's really fucking lame to take a solution that you could never have done yourself and then spend 24 hours since it was posted trying to pick at it.
why didn't you post a solution yesterday and end this thread?... Because you couldn't.
Stop acting like a jealous fagot. It will not make you a better webmaster.
Now I'm done. Gotta go do something more productive than listening to stupid shit.
Comment