Welcome! These forums will be deactivated by the end of this year. The conversation continues in a new morph over on Discord! Please join us there for a more active conversation and the occasional opportunity to ask developers questions directly! Go to the PS+ Discord Server.

Specific IC Advice for a new hacker...

7 posts / 0 new
Last post
Baalbamoth Baalbamoth's picture
Specific IC Advice for a new hacker...
So I need some help, I have a player in my game who is running a hacker, the player is unfamiliar with the setting, tech, and rules, and seems a bit unfamiliar with computer hacking in general. I know in-character dialog is meant for a different forum but I think it would help my player immensely if her character could get some key advice from other EP hackers. So, assuming you are a skilled EP hacker what advice would you give a noob just starting out? What critical knowledge would need to be imparted for a noob to become a successful and respected hacker? How should she manage rep? How should she set up a successful run? What activities should she engage in to protect and aid her firewall team? Any advice no matter how complex or simplistic would be appreciated....
"what do I want? The usual — hundreds of grandchildren, complete dominion over the known worlds, and the pleasure of hearing that all my enemies have died in highly improbable accidents that cannot be connected to me."
Wyvernjack Wyvernjack's picture
- Bit lenghty, but I hope it
- Bit lenghty, but I hope it helps with some of the basics. Core 225 has a sort of guideline to hacking and 259 has all the tables giving examples of what devices can do what and modifiers. The modifiers don't apply if the hack is successful, because then you count as the owner of the device. Hacking someone's mesh inserts successfully will allow you total control until they manually lock down the connection. If you succeed at first hack test and use moxie to make it a critical success, you will gain +30 for all actions inside that device and stay hidden with full admin access. - All right, let's sum up the basics again. First and foremost, we want to keep our software up to date, there is plenty of sources out there (software section, grants +10~+30 modifiers which degrades over time if not kept updated). Then, we practice our scripts, these things can make you a downright menace when used right (programming/10 amount of hacking actions at preset times), which allow us to effectively set up a time bomb. Remember to Take Your Time(+10 up to +30 per extra minute) when trying to get into a system. Like they used to say it, "Steady does it." And for gods sake, don't forget your Muse. It can and will help you, make use of it. I never leave my place without two Ectos I can toss. The simple reason is Mesh ID, by going trough an ecto, you'll be using it's ID, and if you use a script to remove traces of your own ID, it'll be so much harder to trace you down. Once spotted, you run the script and toss it. Sometimes we just don't have the time or chance to physically destroy the ecto, and shoddy job can leave information to be salvaged. You can always work on a few Fake ID's to throw off any links to yourself when buying gear or dealing with shady people, and helps keeping sniffers off your scent, constantly shifting ID's and using encryption. Remember that most devices are slaved to one source, sort of like a bottleneck. When on a person, it's called PAN(personal area network), that means that everything is connected to one device. For example, this Pulsar, Ecto and Gnat are all slaved to my Mesh Inserts, meaning that if anyone tries to hack them, they have to go trough me personally, and might not be prepared for the softwares and scripts I personalized. It took a while for my team to trust me enough that they slaved their mesh inserts to mine for protection. Before you try and hack someone, go into Privacy Mode(core 252), making our signals harder to detect and less likely to reveal our real location. I've seen people with radio boosters do some pretty good work. Any information we send or receive should be done using Public Key Crypto. It's not as powerful as Quantum, but is the next best thing and requires like a week to crack, so having the team generate each their own key once a week is a pretty good security measure. If getting spotted isn't your biggest concern, a rushed Brute Force hacking might be your only choice if time is running out. You'll be spotted at once, but you might get what you wanted, or at least create a distraction for your friends. There's always one trick we can do better than others. If there's a nanoswarm closing in and you're out of EMP granades, turn your Ectos into radio jammers. With luck and skill, you and everyone else will be locked out from the Mesh, but if the nanoswarm doesn't have microwave or laser links, they will be effectively unable to get close. It's not perfect, but better than nothing. You can also use your Mesh inserts this way, but the ecto can be left behind to block a door for a short while. As for Augments, my personal favorite is Multi-tasking. I hear people love using Mental Speed, but it's more of a VR game gimick if you ask me. Yes, you can do basically same thing, but you still have to do it in order, where a multi-tasker can be hacking three devices at once, or fight and hack at the same time. Besides, being in constant slow-mo can become really boring after a while as you're somewhat isolated and dependant on time buffering to communicate with people. Electrical Sense and Wrist Tools can be really good for getting into those hardwired servers and devices. As for gear, a Splash Granade filled with a Taggant nanoswarm is both cheap and a great way to mark enemy targets for your allies trough the Tacnet. A Gray Box(panopticon 150), while usually illegal, will allow you to make hardwired devices, such as airlock controls outside a hab accessible wirelessly, as once connected, it will send stealthed signals to you.
Baalbamoth Baalbamoth's picture
Hey that was awesome, good job...
can anybody give me a "know your role" type advice write up? Something like a list of job duties for a firewall hacker? IE 1) team support, 2) intellegence gathering, 3) etc, and what that would entail, (if not I'll write it up myself but as I havent had much expirence aka any playing a hacker in EP I'd rather hear it from you all... )
"what do I want? The usual — hundreds of grandchildren, complete dominion over the known worlds, and the pleasure of hearing that all my enemies have died in highly improbable accidents that cannot be connected to me."
NewtonPulsifer NewtonPulsifer's picture
Just a quick note that all
Just a quick note that all those teamwork, take your time, and software bonuses are available to the defending/countering infosec roll too. EDIT: Also the +60 bonus cap.
"I fear all we have done is to awaken a sleeping giant and fill him with a terrible resolve."- Isoroku Yamamoto
Baalbamoth Baalbamoth's picture
PM from private user.
From: Slide To: LuLKats Re: Welcome to Firewall Wow, so a little friend told me you’ve gone from a corp computer security expert and asset tracker, to a Firewall hacker and your looking for somebody with a little expirence to give you some headers… I’m not exactly sure what your looking for but I’ve been running with a Firewall team for the last four years, and I sure do have some pointers for you… First off a Firewall team by its nature is extremely unpredictable, every job your going to do will revolve around predicting the unpredictable and planning for every unseen eventuality. Sounds impossible I know but hear me out. First off, intelligence gathering. Wherever your Firewall team goes, and whoever they talk to you should have some kind of basic dossier on. If you know your team will be acting on a specific hab for an extended amount of time, you should find out as much as you can about the hab itself, its systems, security stations and check points, high crime areas, red markets, etc, alternative routs to move through it, etc. you should also know the key players, do a little research into whos been doing what, and any one you believe your team might have lenghtly encounters with you should get as much data as you can… background, financial records, known associations, past crimes, rumors, etc,. Your team will always be needing information like this and a little background checking can make the difference between walking into a trap and setting one for the mark. Next your going to be doing a lot of survaliance and counter survaliance. You should be using the mesh to scout ahead of anywhere you team is in route to, identify possible ambush and choke point. You should also be keeping track of any important people the team as worked with or identified, where their going and what their doing. (anybody want to continue this for me?)
"what do I want? The usual — hundreds of grandchildren, complete dominion over the known worlds, and the pleasure of hearing that all my enemies have died in highly improbable accidents that cannot be connected to me."
Raoul Raoul's picture
Wyvernjack wrote:- If you
Wyvernjack wrote:
- If you succeed at first hack test and use moxie to make it a critical success, you will gain +30 for all actions inside that device and stay hidden with full admin access. -
We agree this is only possible on an unmonitored node? If the node is monitored, you still have to be lucky, so that the monitoring unit misses its roll?
Wyvernjack wrote:
Then, we practice our scripts, these things can make you a downright menace when used right
Do you have a practical example about a great use of a script? What is the point of having a script cleaning after you leave, as you could do it yourself? Can't a security account user simply check all what your account did and discover you launched a script? Same for a backdoor actually... if they saw you, can't they simply have a look at the logs? Thanks for your answers,
Raoul
eaton eaton's picture
Late to the game...
I'm late to the thread, but my understanding is that the script can perform actions while you're doing other things, after you've bailed and logged out. The combination of well-crafted Backdoor scripts, and scripts that collapse common hacking tasks to a single trigger, can conserve critical complex and task actions when time is tight.