Introduction
So, you need the .exe file to open port 104, maybe the Junebug mission is leaving you stumped, or maybe you never did it and are now stuck, unable to unlock a vital server, if so, keep reading
The legitimate way
Note: You don`t specifically need to have the mission active to complete it.
If you can`t start the mission and don`t know the objectives, here is the E-mail sent to you upon accepting, I`ll try and get proper screenshot at some point:
Project_Junebug
CSEC Hub Services
Project Junebug
Hacker,
This isn`t a normal request and we`re not going to treat it as such. We`ve been asked to perform a euthanization.
Obviously, we sent out a few others to dig up data on it (and a few from outside groups, so as not to raise suspicion) some time ago, and largely speaking it`s come back all clear - it seems the man in question, one “Elliot Whit” is hospitalized in considerable pain and, against his wishes, has been denied the option of death.
A failed attempt by his family earlier has prevented them from performing subsequent efforts, until a member proposed this option. It seems the pacemaker he is fitted with allows remote access, with proper authorization, and they believe this may be an avenue to fulfill this request.
Naturally, given the nature of this request, we can accept that you may not want to be involved. Reply with “deny” in your response and we will remove you from the project.
If you do decide to help us with this matter, you should know that it will likely take some amount of investigation and testing, given that as far as we know, this has never before been attempted.
We recommend starting with the target`s medical record, identifying the chip, looking for it`s manufacturers and going from there.
-CSEC Admins
When the offer comes in to accept the Junebug mission, accept it and connect to the medical database, if you don`t have that connection you should be able to connect to it via “208.93.170.15” I`m pretty confident that this IP is static (if not let me know in the comments!), if not you can apply the solution below; break into the server and search for Elliot Whit, when the system finds his file, scroll down and you`ll see 2 IPs, one for the Pacemaker, one for the server with the support details, make a note of them and connect to the support server.
Hack the server, look in the /msgboard folder and find the “firmware and patching notes” and open it, you`ll find another IP inside, scan the network then connect to the IP from the .txt file (remember to rm * the logs before leaving).
Get inside, find the “projects” folder and open the “kellisBT” folder then open the “tests” folder and grab the “kbtpm_test_suit.kbts” and “PacemakerFirmware_cycle_test.dll” using the scp command, next go into the /internal folder and read the Eidolon_security_notes.txt and write down the login inside, you`ll need it to log into the pacemaker.
Now connect to the server you found by scanning the first server, it`s called “Kellis Biotech Production Asset Server”, get inside and navigate to home/Production/Output here you`ll find the kbt_portTest.exe this is what you need to open port 104
Now you got everything you need, so connect to the pacemaker IP we found in the medical database, hack the pacemaker using the KBT_portTest.exe, then navigate to the /KBT_pacemaker folder and upload the “PacemakerFirmware_Cycle_Test.dll” you found earlier using the Upload command. Now click “view Monitor” Then “Login” and use the login we found ealier hint: User: “EAdmin” Password: “tens86” click “Administrate firmware”, then click on “PacemakerFirmware_Cycle_Test.dll” and then “activate firmware”, confirm it and consider you just killed someone, reply to the mission E-mail and you`re done.
Confused?
This guide has a easier to follow version:
Walktrough Hacknet (Step by Step)
I made this guide for those who think they`re completely stuck. I don`t recommend you to read this too much if you seek some challenge 🙂 All missions available now!
Just getting the .exe for 104
Don`t care about the Junebug mission and just want the port 104 .exe?
- Connect to this IP: 66.96.148.1
- Probe it, hack it
- get inside navigate to home/Production/Output here you`ll find the kbt_portTest.exe
- copy the file
- rm the logs and disconnect, you`re done.
Help to future self-help
This solution involves a bit of fiddling with your game files, so as always DO A BACKUP OF THE FILES YOU`RE EDITING I am not responsible for any damage you may cause.
Browse to: Steam\userdata[YOUR STEAM ID HERE]\365450\remote and open your save file, (it`s the one called save[name].xml in notepad (or preferably notepad++.)
Search the document [CTRL+F] the document for “[PC you are looking for, or other identifyable data, like a file you know is on the PC]” without quotes, you should find an entry and the IP attribute immediately to the right of that, copy that IP down and use the connect command ingame, you`ll be connected to the server and can now find whatever file you need.
In closing
I hope this guide helped you, if you had any trouble or any additions/corrections feel free to drop me a line in the comments!
Source : Steam Community