|
|
so what's up with mnet this time?
7 responses total.
that's what i'm wondering.. i try fingering it from over here, and it says host unreachable. and when i try to telnet it won't let me in, i haven't tried dialing in tho.
can't dial in either. rings and rings and rings...
it's broken. I'm about to go fix it. yay me
Last night around 2:30, M-Net started doing some whacky things. For example, sending a tel would give you a system panic, typing !w would give you a message that said there was no memory, and standard UNIX commands (ls, ps, etc) could not be found. Also, if you left party, and came back, you were in as a number (and, not your UID). I think the user vj2 has something to do with it.
yeah, I was there when that funky shit starting happening.. just wondering if m-net was really down, or i just couldn't reach it.
well, it looks like we got hacked again. the popper that we installed must not have been securified. but, we're restoring as we speak, so things will be up just as soon as possible.
Why not run without popper for awhile, until we're sure that we have a version that has all of the holes plugged? Sure it's an inconvenience, but much less of one than having the entire system down and unavailable... not to mention all of the work that you've had to put in rebuilding the system. Food for thought
Response not possible - You must register and login before posting.
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss