Is there anywhere that describes what is necessary to run a matrix node or data haven? Does it require a mainframe or 'server' and what are the prices for the tech?
Basically looking at my decker running a virtual node with security (programmed IC from the Matrix SB) ect, that is tailored to the decker world. Similar to common datahavens and decker 'hangouts'.
Any help & page #s appreciated.
'Nix
Not that I know of.
Figure it takes a cyberterminal with a Matrix OS like the PCC's Dreamcatcher or Fuchi Standard -which would just be high rated programs.
How about this: The rating of the base program as the security value (4 to 16), then figure that the code (Blue to Red) is the multiplier:
not a bad system.
Kinda related but not entirely:
I wanted to know how to go to Shadowland. Like Role Play something like that for a decker. (I'm sure one of my players is going to want to do something like that.)
What Shadowland would be like, that kinda stuff. Any descriptions from books and stuff of how it actually is in there?
Thanks for the help, Kanada. I'm gonna look for some sculpured iconography tidbits around the books I've got here. We're still stuck back in 2061 and our GM was a bit wary when I bought SSG. Game shop down here is sold out of SOTA anyway.
252: A Shadowland node detailed description starts on page 27 of Target: Matrix. That should answer any questions you have. Target: Matrix is really a great fluff book for deckers and there's some excellent material in there.
If anyone wants to add anything, hey, keep this thread going. From how you'd hide the node and other hoops to anything else related to running your own site in the 2060's.
'Nix
| QUOTE (Nix1261) |
| Target: Matrix is really a great fluff book for deckers and there's some excellent material in there. |
http://www.shadowrunrpg.com/resources
This has a few none non-published Target: Matrix things though still cool things. I guess I know the next book that I got to get, now to just figure out how to get it for dirt cheap and half the time of this other stuff. Oh well time isn't too important.
2:52:16
-I'm jacked in tortoise style, I'm still here though.
jumped the gun.
Kanda has some good ideas, let me expand on them. First off I changed the blue and red multipliers. In my mind blue is very easy and red is very hard. The program size and then cost are relative to this. I also included costs for memory and speed. I haven’t filled in all the gaps yet.
Security and ACIFS program multipliers are listed, the ACIFS multipliers is relative to color. Running costs was a list of things that would cost money per month to keep it running. You need enough active memory to run the security and ACIFS programs and IC like Kan said. Right now I am not convinced that you need extra memory for users, but by all means convince me. I do thing that there should be an I/O factor in there though.
gaps gaps gaps....
This is what I have written so far:
| QUOTE |
| Running pirate sites is illegal. Governments try to shut them down, find the physical servers and arrest the operators. Because of this operators find various ways protect themselves and there sites. Regulating access to the site, changing MXP addresses and setting up passwords are only a few of the trick operators use. The two biggest obstacles to running an illegal site remain matrix access and hiding the physical location. The cycle of most sites goes as follows: The site is set up on a boosted MSP account; it slowly gathers a following until at some point the authorities become aware of it. They infiltrate the site, locate its physical location, burst in the door, size all electronics and arrest everybody around. Server Software Security protocols Blue: 2 Green: 8 Orange: 12 Red: 20 Operating programs (ACIFS) Blue: 2 Green:3 Orange:4 Red: 5 Server hardware Active memory mp*7.5 Storage memory mp*6 I/O thingy speed*35 Running Costs Maintenance, sota rules? MPS account<- high-speed matrix service 100Y(300Y) a month. (pg 36 matrix on hacking this) |
a large part of the sysad's job would be securing bandwidth, and planning contingencies for what to do if the current bandwidth is discovered. he'd either spend all day hacking MSPs, setting up bulletproof fake accounts, or hiring other deckers to do it for him.
Hacking MSP is a good start , but what about physical location? All jackpoints have serial numbers (M. p39), so the physical location can be traced, no matter how many MSP accounts you hack. And on top of that spoofed jackpoints don’t last forever (also page 39.) how do we get around that?
My thoughts lead me to believe there is a way to re-rout signals in some way to hide the actual jackpoint. But beyond the idea I have nothing to back it up. Granted though, the more deckers you have signed on the easier it will get.
Contingency plans are good, maybe you could elaborate on that? Give us some.
as i recall, you don't need a jackpoint if you're using a sat uplink--get about ten of 'em, and you should be good. alternatively--or, if you want, do both--make a legitimate server of some type, and hide your datastore inside. maybe create your own low-end MSP company, provide services to a few hundred low-lifestyle Seattleites, and keep the company host on a virtual machine; to access the real machine, you'd need to either deck your way out of the virtual machine, or pick up a passcode that changes every week, posted to some sort of hangout for in-the-know deckers. set up your SAN on a seperate box from your actual datastore, and put a few hops in between them (like setting up a conference call; basically, you're setting up a PLTG). five or six times a day, hack into one of the hosts you're hopping through and do a Redirect Datatrail operation. that way, if somebody traces you, they hit a roadblock that you control.
contingency plans would mainly be alternate MSP accounts that you've already hacked and hidden, waiting for when you need them. depending, you might also set explosive charges in your actual datastore box, with command codes that only you know--that way, if they bust down the door on you, you can destroy the evidence. the uber-paranoid might even set up capitance wire around the box, primed to set off the charges if anyone gets close; you'd have a remote control of some sort, so you could shut the explosive system off when you need to access the box yourself.
I had given satellites a thought, but it still seems that if a decker can log into the site then the authorities can still track it. I just haven’t figured out how yet. Hiding the site on legitimate front host is a great idea, and if caught the operator can always plead ignorance to what evil deckers were putting on his server. This works real well if the front company is a MSP. MSP are likely decker targets.
That got me thinking, and I came up with this. This is one way to run a site, this method would be good for new decker organizations who don’t have the cash to buy equipment or skills to hack the mail or banks.
| QUOTE |
| Multi-MSP accounts. Server-less “Geotown” method. This method removes the need for an actual central server, and instead scatters the information across various hacked and expendable MSP accounts. Utilizing free or low cost web publishing services such as “Ey-you, Geo-towns” and Novatechs “Nova-sites” information is uploaded across individual sites then linked with a few central “main page accounts.” Information is often mirrored several times for redundancy. The benefits of this system are that accounts are not set to a fixed jackpoint, and this information can be uploaded from anywhere. This makes the operators hard to track down. Several mirrors can be set up using the same service and be “on call” in case the current system is shut down. The down side is that most free sites have a limit to MP that can be stored on a page, limiting the size of files available for trade. The more costly the service is, the more MP it can store, but is also harder to crack Personal Matrix page services: Ey-you Geo-towns Free . Blue /average. 20mp limit per account. Geo-town sites are usually loaded with advertisement pop ups. These sites are really nothing more the decorated billboards. However the ease of the hosts leads most deckers to simply turn them off. (Control slave) Novatech Nova-sites 50Y a month. Green/average 150mp limit. |
not a bad idea.
| QUOTE |
| Target Matrix: 24 Data havens commonly rolocate their SANs and change their access codes on a random basis. Other common concealment measures include trap doors, vanishing SANs, virtual hosts and simple concealment. Furthermore, data havens are usually linked to grids and hosts illegaly or employ cadres of deckers to thouroughly eradicate all system records. Consequently, determining the physical location of a data haven via its Matrix presence is vitrually impossible. |
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)