Heart%-secure

WillDrens: I know no one really cares, but here's the current Heart-Secure% as I see it now, including potential optimizations, though these might just be minor set-ups, and more research is needed in several key areas, namely shell commands and CSEC jobs.
[11:17 PM] WillDrens: After the opening tutorial quick end (type 'ps' after initialization complete, press enter when you see the 'Launching Tutorial', then type the kill command when you regain control of 'terminal')
[11:17 PM] WillDrens: Shell your own CPU, go to /bin, rm *
[11:17 PM] WillDrens: reply to 'First Contact' email.
[11:19 PM] WillDrens: When you hack into Viper Battlestation, there are three things you need to do.  run a shell, scp * in bin, and open the file in /home marked asdf, which leads you to the entropy test.
[11:19 PM] WillDrens: Hack into that, (shell overload before you probe
[11:20 PM] WillDrens: prepare an scp * while porthacking, and then, after using it on /home, run a shell on that.(edited)
[11:23 PM] WillDrens: News Site: Same deal, though prep a rm * for the msg board while porthacking.  The only file you need to delete is config.sys, which is the first file deleted.  Also, run a shell, bringing your total up to four.
[11:24 PM] WillDrens: When you enter Entropy, you do not need to scp FTPBounce in order to enter, just reply to the email, make sure you mark the asset servers as you'll need FTPBounce for most every hack.
[11:25 PM] WillDrens: Now we get into the fun bit of routing, the kind that saves seconds.
[11:29 PM] WillDrens: Every single command besides PortHack and eosDeviceScan works without you having to be directly connected with the server, however, it seems to be a crapshoot on whether the ports close or not if you aren't connected.  All I can say for 100% certainty is that if you run a program, disconnect, and return BEFORE the program has finished, you should be fine.(edited)
[11:31 PM] WillDrens: Accept 'Back to School' mission (the only one that only has one port to crack), and while SSH is running, download FTPBounce.  While porthacking, prep ***, open the file marked pw_something.log, reply.(edited)
[11:31 PM] WillDrens: Pointclicker is next, I think everyone knows pointclicker, just remember to prep rm Mengsk.pcsav(edited)
[11:32 PM] WillDrens: After that, there are two missions at the bottom, whos names are randomized.  Pick one, (2 Ports to hack, no shell), and rm * in /home.(edited)
[11:34 PM] WillDrens: Phone mission, for those playing Heart-Secure%, all that's really here to remember is to go in, while running FTPBounce and SSHCrack, to look at the followup email that marks the password (ya, you need to show it on screen), and download eosDeviceScan from Entropy asset server, then run porthack and eosDeviceScan, getting the password from the /eos/mail file (tintin7), and continuing.(edited)
[11:36 PM] WillDrens: The last mission is the other randomly named mission at the bottom to remove something.
[11:37 PM] WillDrens: Aggression Must Be Punished
[11:37 PM] WillDrens: Well, that should help.
[11:41 PM] WillDrens: Ok, the first proxy node, I have no idea, as this one closes ports on you as I mentioned above, as well as proxy-blocks you.  What I've been doing is this.  Overload > FTPBounce > scp SMTPoverflow (req. 3 ports) > reOverload > SMTPoverflow > SSHcrack > Porthack (prep rm * for /home).
[11:46 PM] WillDrens: Afterword, go to your log, set up a proxy node trap (it has to be from your own CPU), then wait for Naix to come on, trap trigger, wait for the borders to stop flashing red.(edited)
[11:48 PM] WillDrens: Proxy Node 2 connect via the logs provided, then you should only need SSHCrack to succeed.  make sure to download WebServerWorm from the bin before proceeding.
[11:48 PM] WillDrens: Naix-Battlestation-Name Hack into this one, making sure you use the following commands, FTPBounce, WebServerWorm, then close two of the shells, then SSHCrack
[11:50 PM] WillDrens: Remove the macrosoft thing, but don't (UNDER ANY CIRCUMSTANCES (unless it's proven to be faster, which I doubt)) delete anything in the sys folder.  That leads to /el, which takes a helluva lot longer than CSEC's three challenges.
[11:51 PM] WillDrens: Remember, you can run programs through a firewall, so make sure to run them before using analyze.
[11:53 PM] WillDrens: CFC: I don't know how really to save time, though I might have a feeling that the developer had it so it only checked to see if one is uploaded, so it might, MIGHT, only check if pt. 2 was uploaded.
[11:57 PM] WillDrens: CSEC I don't have a list ready for any of this, order isn't really been researched by me, and this is the area for most improvement.
March 3, 2018
[12:06 AM] WillDrens: The Job List is as follows: Academic quests (replace Marketing w/ Security for John Stalvern, rm Jacob Stevens), that's two down.   Find/Create a Decryption Software, Track an Encrypted File for the executables.  Check out a suspicious server, then, and this is the only one that I'm unsure about, Decrypt a secure transmission, ending with Investigate a Medical Record.
[12:09 AM] WillDrens: Taking into account SQL_MemCorrupt download and Sequencer download, as well as running PortHack on the Crossroads server, a few minor optimizations could probably save around 3 minutes in CSEC alone.
[12:11 AM] WillDrens: Project Junebug: Use the recent medical server to connect, use /notes to add the IP starting with 202 (unless you write it down before hand), then connect to the other one.
[12:15 AM] WillDrens: Proj. Junebug cont.: After the hacks, scan, connect to the server mentioned in 'Security' message, hack that, and in those two servers contain everything you need to connect to the 202 server and complete the mission.  Reply when HB drops to 0
[12:18 AM] WillDrens: Bit All you need to know is that you don't need to download tracekill, and you don't need to connect to the drop server to continue, all you need is the password.  When booting up sequencer, shell everything
March 7, 2018
[5:46 PM] WillDrens: ADDENDUM: Entropy reply email: all you need is admin status on the entropy asset server in order to reply.