Unwired page 95 has rules for Proprietary File Formats. I'm not all that tech-savvy, but I understand PFF to be akin to the phenomenon of not being able to get iTunes on a PC. I'm also of the understanding that the rules essentially imply that a mega will protect its data from public scrutiny by putting it in a format that can only be handled by the operating systems that they sell ... to the public as much as anyone.
Are those understandings right?
Almost. A proprietary format is a format that can only be read/edited/created by certain programs. Maybe it's one program, maybe some programs can read it but not write it, or maybe many programs can do it, but the format itself is still not 'open'.
In terms of SR4 rules, PFF means a specific security measure that a corp can use. They use formats that only they can read (not the public, necessarily—if they're smart, it's a special internal-only OS). To beat this, you must buy emulator 'patches'.
Honestly, the idea of 'just use an OS from that company' is kind of a mistake on Unwired's part. If they really wanted to keep it internal-only, no public-release OS would work, period. You'd have to acquire a copy of the internal corporate one.
Yeah, DRM formats of today are a good example, although a very different purpose.
I think it's bad game design. First they make an abstract Matrix ruleset, where OS compatibility and all that is handwaved with "that's boring and way too detailed for a game", and then the nerds creep out of the woodwork and start adding this kind of thing back in.
I mean, I'm not against a less-bland Matrix ruleset, but this is really a fish nor fowl thing.
By the way, same for your topic about studying exploits. Studying exploits and needing specific-brand software are cute and could have some setting flavor, but it's way too late to put it into the rules as an afterthought.
Or, is it exactly not too late enough? (This is a joke.)
I'm fine with giving the corps another security feature, which is all this is. It's essentially an extra level of weak encryption. Exploits are just another kind of legwork. It's all optional, of course. Nothing wrong with options.
Uh, don't be so quick folks. I'm sure you youngin's out there don't remember it, but proprietary file formats have been around for a long, long time. Back before MS Office became the "Industry Standard", every office suite (Or individually sold!) program had it's own file format that was not compatible with any other. And the only reason that MS Office became the standard was because Windows (Bundled with MS Office) became the standard for businesses in North America for the average computer user. This was the early/mid/late-90s, when office workers were looking at a computer mouse and going, "What's that? It doesn't look like something I saw in my Typewriter Class."
One of my tech jobs was migrating an old (Ancient by computer standards. Some of the files dated back to 1983!) database to an HTML-Based version that had a (*GASP*) search function available. Unfortunately, the programming company that sold them the database system swore up and down that it would convert the files automatically even if they were that old, and were extensively tested to ensure that 100% of data migration happened. ... ... Yeah, it was marketing talking out their hoops and having no idea what the hell they were saying. My team literally had to manually move over the files one at a time into a very bad HTML Text Editor. In Internet Explorer (You know, the #1 web browser for downloading a better web browser?). Despite the headaches, it was fun.
With Megacorporations being countries and the only standard being "It has to work with The Matrix", I could easily see computer companies going back to PFFs aimed at working with only one OS, especially if it ensures that AA- and A-Level Corporations are reliant on their OSes on all systems, their programs, their mass data storage devices... You get the picture.
I'm not saying PFFs are unrealistic, I'm saying they're too low-level, technical to fit with the high level abstraction of the Matrix rules.
They'd have made more sense in a rule set where for example, the choice of operating system had any impact on game mechanics.
Which is why it helps to treat them as an encryption layer. I'd require the team to steal the software/hardware to open it, possibly on a separate run. It'd be fun.
Wasn't there an official run where the Runners had to find a way to get Data of a CD?
Including needing to find somebody with that kind of vintage Hardware?
"On The Run", packaged now with the new Runner's Toolkit.
Which is apparently on a *VERY* slow boat from China!
That's exactly right, Nezumi.
Now imagine a school that uses... I think we had four different word processing programs on the computers at one time, not including different versions. I ended up saving everything as ASCII, then edited it when it was time for the final printing. That worked great unless I was stuck with a PC-Formatted disk and the only labs available for printing were the Mac Labs. Then Hotmail came out and things got a lot better. ASCII worked on PC and Mac no problem, and Web-Based Mail (A new thing back then) made sending files to yourself so much easier.
It's great to throw in as a WTF moment when they get through the encryption, only to find that the file is complete and utter garbage, and the Hacker has to try and remember if that file type is proprietary or if they accidentally tripped a Databomb.
Just think of it as a secret handshake between gang members. Do it right, get in. Do it wrong, get left in the back alley as a bloody pulp...
And hell, its from the book of expanded matrix rules. You did not expect that to be nitty gritty?
There's back alleys in the Matrix as well that you can be left, beaten to a pulp, as the Feral AIs come crawling out of the virtual walls to come and eat at your digital flesh...
Some clarification of reality.
Just about any organization with it's own programmers has data in a proprietary file format. When the data is only used by, at most, a few programs, it's very easy to just shove the data into the file, one field after another and then pull it out again. Someone who gets their hand on this file may have a lot of valuable data, but it's not much use unless they can figure out what that data means.
Addresses, dates, names are pretty easy to figure out, however what the date is the date of can be a nightmare. A simple piece of data can have a lot of dates in it. Trying to find an account number can be extremely difficult. It shouldn't be, but years of working with credit card data stored by Cobol programs have taught me otherwise. Trying to understand the meanings of all the flags (Y,N) or settings (A-Q,1,2,3) can be impossible without a lot of work.
Note that the data, the file format, and the meaning of the data are often stored as far away from each other as possible because things aren't stored in a way to make it easy to learn. The file format is stored with the file formats. The data is stored with the data. And the meaning MIGHT be in the software but it's just as likely to be stored in some other piece of software and this file is just passing data from the previous file to the next file.
The takeaway piece from this is that what you may have for paydata is DATA but not MEANING. It's only valuable to the people who can convert that data back into information by applying meaning to the data. A list of names is just a list of names. A list of spies, people that need to be eliminated, employees at other organizations that are being headhunted, customers with unlimited credit who store their passkeys here for easy installation/delivery, all of that has a lot more value than a list of names. Data by itself is not as valuable as data with meaning.
I was a Clerk. Don't even get me started on Dates.
Big part of the y2k scare was that to save memory, both ram and storage, on those old COBOL programs they basically shaved off the front 19 and handled the year part of the date as a two digit number.
I'm a lazy programmer and making my life easier with code shortcuts makes all the next guys suffer! Hahahaha!
Seriously though, just today I was working with a little excel macro that broke (~400 lines) and even though it's commented all the way through, it still took a few hours to figure out what all it was doing. But hey, it's job security, right?
That context is mighty important.
We had problems galore with our database, but, because I was an "Expert Computer Tech" (With a useless degree and out-of-date information), my boss was scared I'd go in and try to "Fix" something.
Every time something breaks at work, it's"Shut in the Tech-Support, don't let them near it, we have to let the bureaucracy run it's course and they would fix it before that can happen!"
Erm, if you were wondering where this came from, it's rather in-cannon. Can't remember the damn title, can remember the illustration of the gimp ninja-shadowrunner-with katana, though)
Anyhoo: In the book...
Way back when, someone nicely uploaded a copy of an internal Fuchi memo (Fuchi! Fuchi! Fuchi! For all your computer needs) in dealing with shadowrunners, if you're a corperate suit. Miles Lanier was featured, lots of colour text there:)
Thing is, they had to type the damn memo in, as it was in a corperate format that melted this guy's top-of-the-line deck when he tried to access the company files, so he had to use a POS turtle the he lifted from a terrified corporate wallflower to read the file (the mechanism being an inbuilt company-only hardwired chip in the POS deck- they didn't go into it, but it sounded like he couldn't get it out or it'd fry said deck, as well.)
This new optional effect sounds like a lot less hardware-intensive and logical progression, especially for Omega-level security level/Company nobility info. And a great reason for your minions to loot like mofo's during a run.
-Tir
It's not just tech support that suffers from ignorance-generated fear. I was fired from a cashier job at a gas station because I took notes throughout the night as I set aside the money for the next shift's till. The friend that got me the job had told the manager I was really good at math. Clearly readin' + writin' + 'rithmatic = stealing. It didn't matter that there was no money or inventory missing. Luckily it was a completely different economy and McJobs were a dime a dozen.
More like a case of the Supervisor being a low-end user. She knew the systems that she was supposed to use for work, check her webmail, run Internet radio, and play Flash games, but more than that, forget it.
But, yeah, PFFs are good for the occasional WTF scenario to throw off the group. Especially if you're dealing with some high-end paydata that might require the Sixth World equivalent of a Dongle to prevent the Deck/Commlink from being fried by security software.
Aha!
Shadowrun Companion 3 - page, er, 52.
"How to hire a Shadowrunner"
And here I thought all that book was good for was the racial modifiers for Night ones and Minotaurs:) I kid:)
Incidently, it was also the section where "Nadja Daviar has luscious gams" came into canon, it being a passphrase into the fileserver backdoor (watch out for that Tarbaby ![]()
-Tir
Dammit, where's some History when you need him?![]()
Of all the places to put it...
I think (so far in this thread) you are close with your analogies about PFFs, but not exactly correct. Unwired is talking about PFFs on a operating system, not just a program file. They are not talking about a word file or excel (although, its close). It more akin to Windows vs. OSX vs. various flavors of GNU Linux. Try running an .EXE file on any OS other than Windows. .DLL, .COM, .BAT files are also good examples. Try running a .TAR file on something other than GNU Linux.
In the above examples, you more often than not, need a specific OS installed on your hardware in order to make use of the file. You might be able to open something with a low-level editor and kind of figure out what the file is, but you can't run it in its native OS.
Unwired opens up the door to having your commlink multi-boot with a variety of different OSs.
Well, doesn't it just say 'buy a cheap emulator'? You're right, it's a generic 'does not work here' effect for files and programs… without the emulator.
Isn't it a bit of a bummer showstopper in an era where any kind of encryption is (magically) breakable in practical time?
Also, why is the only specific effect of operating system brands? I think that's a missed opportunity - instead of trying to differentiate Nodes with sculpting, give the various OS brands different approaches to computer security perhaps? Much in the way that Linux and Windows are quite different, security-wise?
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)