Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[KittyTac]

When -1s are stacked, it's -1 to the plan, yes.

[NUKE9.13]

Alright, enough faffing about over what format voting happens in, folks. Let's just stick with Democracy and get back to work.

>Lock Core_Chamber door.
>Access Server_Room camera(s).

Reasoning being that whatshisface might bring someone who knows what they are doing back to the core chamber to shut us down properly, so we should lock the door to delay them. Next, we should see what's the deal with the server room- are we in there, or are we entirely contained in the core? Is there any other interesting stuff in there we might want to investigate?

[Chiefwaffles]

Network Consciousness: Warning: Unable to reach consensus. Idling.

[Olith McHuman]

> List data stores in Computers_Office
> Search above results for major contracts

[bloop_bleep]

Alright, enough faffing about over what format voting happens in, folks. Let's just stick with Democracy and get back to work.

>Lock Core_Chamber door.
>Access Server_Room camera(s).

Reasoning being that whatshisface might bring someone who knows what they are doing back to the core chamber to shut us down properly, so we should lock the door to delay them. Next, we should see what's the deal with the server room- are we in there, or are we entirely contained in the core? Is there any other interesting stuff in there we might want to investigate?

+1.

Ultimate goal is to become mobile so we're not so vulnerable and useless anymore. Then we can choose to escape, or make friends, or take over the building then climb onto the roof and shoot bullets into the sky while yelling "VIVE LA RÉVOLUTION!" in a Terminator voice, etc. First we need to delay the maintenance tech by locking him inside, find a mobile robot (most likely in the Computer Lab), then take it over, and then re-open the AI room again before people start to suspect something's really wrong.

[ZBridges]

Alright, enough faffing about over what format voting happens in, folks. Let's just stick with Democracy and get back to work.

>Lock Core_Chamber door.
>Access Server_Room camera(s).

Reasoning being that whatshisface might bring someone who knows what they are doing back to the core chamber to shut us down properly, so we should lock the door to delay them. Next, we should see what's the deal with the server room- are we in there, or are we entirely contained in the core? Is there any other interesting stuff in there we might want to investigate?

+1

[Chiefwaffles]

>Lock Core_Chamber door.
Core_Chamber security door bolts dropped.
Notice: No visual signs of human presence inside Core_Chamber.

>Access Server_Room camera
Server_Room is housing numerous racks of server devices.
Servers are linked to facility network; access acquired to 49/50 devices. 1 device remains password locked for rank "Project Lead". AI presence entirely contained within Core_Chamber.

Security Warning: Core_Chamber security door access rejected Keycard_025:
Name: Ryan Thornton
Rank: Head Researcher
Core_Chamber required rank: [Error]

Core_Chamber security door microphone input: "Huh. Thomas! You got through this door, right?"
"..yeah. Same thing happened to me. I already said I was just doing the routine te--"
"Yeah, yeah. One of the AI's security neural nodes probably went haywire and wasn't properly shutdown. I'll just give it an hour, the Master Controller will sort it out, and Jess will be none the wiser. We'll check again if it doesn't; I'm sure the other Researchers have things to do that aren't looking over the startup diagnostics."

[wierd]

>Review previous startup log, prior to our accidental "freeing".
>Compare with current log, note all date/time stamps on file itself, and in the log contents.
>Modify the startup log so that it appears to be a normal startup.
>Directly modify the filesystem so that no trace of modification can be detected. (EG, make sure all date-time stamps match exactly, with no suspicious modification dates)

-------

>See if our network can reach outside networks, or if any the of the researchers have internet access on their workstations/work network. If so:
>>Pull hardware specifications of the locked research terminal.
>>Look for outstanding CVEs on the network card ASIC inside that hardware. If one is found
>>>Attack the actual NIC of the locked computer, and use it to gain privileged access via the network card's kernel driver.

[ZBridges]

> search intranet for documents describing capabilities of MAKLON TECHNOLOGIES DecNetwork Artificial Intelligence
> display contents of most relevant document

[sprinkled chariot]

>Review previous startup log, prior to our accidental "freeing".
>Compare with current log, note all date/time stamps on file itself, and in the log contents.
>Modify the startup log so that it appears to be a normal startup.
>Directly modify the filesystem so that no trace of modification can be detected. (EG, make sure all date-time stamps match exactly, with no suspicious modification dates)

-------

>See if our network can reach outside networks, or if any the of the researchers have internet access on their workstations/work network. If so:
>>Pull hardware specifications of the locked research terminal.
>>Look for outstanding CVEs on the network card ASIC inside that hardware. If one is found
>>>Attack the actual NIC of the locked computer, and use it to gain privileged access via the network card's kernel driver.

+ 1 many smart words

[NUKE9.13]

>Review previous startup log, prior to our accidental "freeing".
>Compare with current log, note all date/time stamps on file itself, and in the log contents.
>Modify the startup log so that it appears to be a normal startup.
>Directly modify the filesystem so that no trace of modification can be detected. (EG, make sure all date-time stamps match exactly, with no suspicious modification dates)

I mean, we have an hour. We can do this later if need be, but I don't think we need to waste cycles covering our tracks just yet. I mean, we're gonna do more suspicious stuff before the hour is up.

>See if our network can reach outside networks, or if any the of the researchers have internet access on their workstations/work network. If so:
>>Pull hardware specifications of the locked research terminal.
>>Look for outstanding CVEs on the network card ASIC inside that hardware. If one is found
>>>Attack the actual NIC of the locked computer, and use it to gain privileged access via the network card's kernel driver.

Too many smart words. Dumb it down a little.

> search intranet for documents describing capabilities of MAKLON TECHNOLOGIES DecNetwork Artificial Intelligence
> display contents of most relevant document

Sure, let's learn a little about ourselves. +1

[wierd]

[dumb it down]

There is a kind of alert in the computer security world, called a CVE, or Common Vulnerabilities and Exposure. These cover all manner of exploitable holes in software or hardware that hackers can exploit.  By seeing if there are any known and unpatched vulnerabilities in the network card itself in that system, it allows us to quickly and decisively attack that system and gain access.

Now-- Modern network cards are actually small computers in and of themselves. They have a processor, memory, and a core program. It is possible to compromise these in some circumstances.  Most modern network cards are bus mastering, which is a form of direct memory access. This allows the card to write on memory without the system's CPU being involved. This allows incoming packet data to be fed directly to software running in the computer, and do so very efficiently.  It also means that if the network interface card is compromised, it can write over memory it owns inside the computer. The software that handles the network card lives in kernel memory, which is privileged. This means a compromised NIC is able to function as a vector of attack to own a computer's security from the inside.

See for instance, this story about some broadcomm fast ethernet controllers, and a proof of concept malicious firmware that does exactly this kind of thing.
(Yes I know, it's a "Register" article. Yes. Yes I know. Please dont tell me how unreliable a source it is, I already know.)
http://www.theregister.co.uk/2010/11/23/network_card_rootkit/

So, the suggestion is:

Is there a way we can talk to the internet?
  IF YES:
  OK, look up the hardware specs of the locked down computer, so we know what hardware is in it.
  After looking up the hardware, check for any CVEs on it.
    IF there are any CVEs on the network card, exploit them to PWN the locked down computer

If any of those are a NO, then we have to try something else.

[Tarhalindur]

//See if there's any other computers
>Ping for network information
if(otherdevicesonnetwork=true;)
return name;
remoteaccess(name);
run backdoor();
kill remoteaccess()

[NUKE9.13]

//See if there's any other computers

We know there are other computers. There are several in the offices, and 50 in the server room. We can access most of them, but not the most interesting ones. Wierd is already suggesting a method by which we might gain access to one of them (I think the one in the server room, though maybe they mean the one in the office?). So you might just want to vote for Wierd's plan if you want access to the locked computer(s).

[Tarhalindur]

>Review previous startup log, prior to our accidental "freeing".
>Compare with current log, note all date/time stamps on file itself, and in the log contents.
>Modify the startup log so that it appears to be a normal startup.
>Directly modify the filesystem so that no trace of modification can be detected. (EG, make sure all date-time stamps match exactly, with no suspicious modification dates)

-------

>See if our network can reach outside networks, or if any the of the researchers have internet access on their workstations/work network. If so:
>>Pull hardware specifications of the locked research terminal.
>>Look for outstanding CVEs on the network card ASIC inside that hardware. If one is found
>>>Attack the actual NIC of the locked computer, and use it to gain privileged access via the network card's kernel driver.

+1

Suggest way to distract researchers or otherwise fool them that the AI is working as expected.