createBlog Havoc. Options

[delphi]

micron's phone number is posted somewhere - i saw it a few hours ago. call him hahah.

[*disco infiltrator*]

jusun's on AIM right now. he's on a public computer though, so he's hesitant about going into the admincp.

mods can change titles of skins.

[*Azarel*]

micron's phone number is posted somewhere - i saw it a few hours ago. call him hahah.

I've already suggested it, lol. He posted a fake number, if you read through the earlier pages of this thread.

[*mipadi*]

you forgot to dimension the integers. well, maybe you'd have to make it a long.

i love being a nerd.

btw i'm kidding. i'm not obnoxious.

Yeah, I also left out my header files, a main function, and a return statement; I wouldn't try to compile this as-is.

And on most compilers, an int should be big enough to hold 999,999,999.

[*kryogenix*]

ok guys it's best if we let micron take it from here. if you have more information on who is responsible, pm a mod. it'll be easier to find them if they don't know how we're looking for them.

[*stephinika*]

wow....this topic has moved fast. and yay. my account is back. just thought i'd let you all know...

[jordanriane]

1. Do not post about any other hacked "threads" or "layouts." Simply compile whatever you find and list them in a pm, however, do not send a pm each time, just save a pm to your drafts, and as you find them, add them to the pm, then when you haven't found any, send the pm.

2. Do not post about changing the password anymore.

3. Do not post about other ways to hack, do brute force, etc.

4. This is being fixed, so calm down.

5. Do not repeat what everyone else knows.

[Jorge]

lol steph you're the only mod unbanned now?

[sheepy]

awww mang =[

[sadolakced acid]

Same with writing.
And it's blue screen of death.

blue screen of death is for regular errors. but in windows longhorn, it's rumoured there will be a new screen, a red screen of death for 'fatal errors'. what does microsoft think are fatal errors? something that will make users switch to linux...

linky:
the red screen of death

mmmm.... and also a little more relevant: if each mod only had control over one forum... a hacker with one mod account couldn't bring down more than one forum.

oh fine it's not a good idea.

[*Azarel*]

wow....this topic has moved fast. and yay. my account is back. just thought i'd let you all know...

Welcome back.

1. Do not post about any other hacked "threads" or "layouts." Simply compile whatever you find and list them in a pm, however, do not send a pm each time, just save a pm to your drafts, and as you find them, add them to the pm, then when you haven't found any, send the pm.
2. Do not post about changing the password anymore.
3. Do not post about other ways to hack, do brute force, etc.
4. This is being fixed, so calm down.
5. Do not repeat what everyone else knows.

In response to 4, yay! Good idea too, on compiling things into a numbered list so that people don't have to read the entire thread, I guess.

blue screen of death is for regular errors.  but in windows longhorn, it's rumoured there will be a new screen, a red screen of death for 'fatal errors'.  what does microsoft think are fatal errors?  something that will make users switch to linux... 
linky:
the red screen of death
mmmm....  and also a little more relevant:  if each mod only had control over one forum...  a hacker with one mod account couldn't bring down more than one forum. 
oh fine it's not a good idea.

Ah, I see. And it's cute how you won't let go of your little mod idea.

[*stephinika*]

thanks anna.
and jorge, umm well that was originally banned? i think so...nicki somehow got me unbanned. i don't know how. *shrug*

[wickedcurse]

who is the culprit? this is controversy!

[*Azarel*]

ok guys it's best if we let micron take it from here. if you have more information on who is responsible, pm a mod. it'll be easier to find them if they don't know how we're looking for them.

Is there any preference as to which mod?

who is the culprit? this is controversy!

... read the thread! Don't repeat shit!

[delphi]

well this is great. my website skin was hacked so it got deleted AFTER i had editted the topic and put my code in. then i deleted everything from my desktop and now i no longer have the code - so when i resubmit it, i'll have to code it over again. what a pain in the assssssssssssss.

[racoons > you]

WHY DONT YOU LISTEN?

DO NOT GRIPE ABOUT INDIVIDUAL PROBLEMS

THEY KNOW ALREADY. I TWILL BE DEALT WITH

[delphi]

I WAS JUST SAYIN THAT IT SUCKS. CALM YOUR ASS DOWN - IF THEY HAVE MY CODE IN THE CACHE OR CAN RESTORE THE TOPIC, THATD BE GREAT TOO. BUT THEY WONT DO IT UNLESS I EXPRESS MY DISMAY.

WHY DONT WE TAKE CAPS OFF NOW HMM?

[*mzkandi*]

I WAS JUST SAYIN THAT IT SUCKS. CALM YOUR ASS DOWN - IF THEY HAVE MY CODE IN THE CACHE OR CAN RESTORE THE TOPIC, THATD BE GREAT TOO. BUT THEY WONT DO IT UNLESS I EXPRESS MY DISMAY.

WHY DONT WE TAKE CAPS OFF NOW HMM?

The fact of the matter is your not only person this has happen to. It happen to me as well but dont see my whining about it. The staff is doing what it can, so suck it up.

[heyyfrankie]

I WAS JUST SAYIN THAT IT SUCKS. CALM YOUR ASS DOWN - IF THEY HAVE MY CODE IN THE CACHE OR CAN RESTORE THE TOPIC, THATD BE GREAT TOO. BUT THEY WONT DO IT UNLESS I EXPRESS MY DISMAY.

WHY DONT WE TAKE CAPS OFF NOW HMM?

ACTUALLY you have to re-submit your skins. eve(headstaff) said that.

EDIT;;

Okay, I'm going to explain it once so read carefully.

A hacker was on TOUCH MY MONKEY (aka Sammi's) username. The hacker was ACCEPTING skins AND THEN deleting the title and content of the skin and changing them to "you just got hacked yadayadayada".
The only way to remove those skins was to REJECT them. The content and title was lost.

Please re-submit.

[*mzkandi*]

^thanks for that Frankie...heres a cookie!

[delphi]

the staff cant do anything about it. theyve already stated they cant ipban and they cant use the ip tools. i know how ipb works, and the only people who can even track down who it is is an admin - and even after that, they wont be able to ban them if the person is using proxies. and if the person is using someone elses account, they wont be able to ban any usernames. and if everyone just changes their password, what's to stop the person from bruteforcing it again?

i dont think the staff is really handling it. it's wishful thinking. either way, theres nothing stopping me from expressing my frustration with having to code an entire freaking template again UNLESS someone can manually go into the mySQL database and add the post back if they have a recent backup of the forum.

the question is would they have known to do that if i hadnt said anything?
no. because chances are they arent recording or saving these topics before they go and delete them.

the smarter thing to have done is move them to their private forum until the problem gets fixed.




i think some of you are just looking for things to yell about and i might be an easy target to you since im "new" - im not new. i've been lurking for a while now.

hows that for misplaced anger?

edit://
and my submission wasnt rejected. it was accepted and then deleted. major difference. i just said that i had already editted the hacked topic with my code in it, and the mod could have just re-editted the topic title and left it like it was, OR saved the topic in a private forum.

i can read. can you?

[racoons > you]

oh just shut up, please

[heyyfrankie]

i dont think the staff is really handling it.

that's really not fair to say unless you know what going on... now is it? you don't know EVERYTHING.

[*mipadi*]

i dont think the staff is really handling it. it's wishful thinking. either way, theres nothing stopping me from expressing my frustration with having to code an entire freaking template again UNLESS someone can manually go into the mySQL database and add the post back if they have a recent backup of the forum.\

I don't mean to say this in a taunting or malicious way, just in a helpful way: it's a good idea to keep a backup of any important project, especially one which is being posted in a public domain. The Internet's a wild place.

[delphi]

ok. i'll stop complaining since clearly no one is going to understand. (maybe you dont know what i mean by this - i mean stop finding reasons to yell at people and read the posts more carefully - take it for what it's worth because its EMBEDDED with advice)

i'll break it down simply. im offering suggestions. the suggestions are as follows:

1. stop deleting the topics. SAVE them somewhere else so it will be easier on BOTH sides. move them back when the problem gets fixed. that's really just common sense, i think.

2. maybe an admin should disable moderators ability to edit topics temporarily.

3. make frequent backups of the ipb_POSTS table in the mysql database ONLY - saves time and space, and itd be easier to search for a particular post if you need to restore something.

that should last you a few days until the "hacker" finds some other way to screw you over - but it should buy you enough time to figure out how to get rid of him. although i dont think theres a way.


edit://

and wrong. i do know everything. i know what moderators can and cannot do on ipb, and since you guys have already stated that u cant use ip tools or ip ban anyone, then its up to the admins.

next you said that all the admins are not available. however later it was stated that micron had been notified of the situation.

BUT - if the hacker is using proxies and has a new ip everytime he logs onto cb - how will you ipban him/her?


so what exactly is being done?