#adcs

the operating system is Kingsolution HE DESIGNED IT

present day is 1996

this is a fully accurate terminal readout and stuff which is cool

like whoami is a real command (modern day example attached) and that infopanel is roughly what you would see if you accessed a system via telnet (also a real remote access protocol!)

5. CAIN WAS WRITTEN IN LISP 6. BUBBLE TOO

7. We also have the source code for Caine's Wacky Watch. Amusing that it's the only part written in C.

8. this command, as far as I can tell, is utterly illegitimate

amusingly, the way you'd typically do that is with the kill command. (this example on my computer stops the discord process)

Might've been a bit too on the nose for queen gooseworx

9. this is very funny and utterly false in typical systems, though it would make sense that caine would've modified the system.

10. this is such a fucking deep cut and I love them for it. Kinger is trying to use a piece of debug software to force access to caine's software in the ACTUAL manner one would do that and with a REAL DEBUG TOOL

11. The above image is where we get the first instance of something that kinda minorly annoys me but it's far from important. As shown by Kinger's 'whoami' right after gaining access, Kinger is an administrator. As such, he should be able to override the 'operation not permitted' errors by just running 'sudo' (i.e. 'sudo /usr/bin/gdb /usr/local/bin/clisp 1337', and thus override any complaints, because theoretically sudo power can't be denied (correct me if i'm wrong about this please).

12. Also caine's process ID is leet in leetcode. Iconic.

13. ok now THIS line is very confusing. chmod is a command that modifies a file's metadata. Specifically, Kinger is modifying the file's permissions so that nobody with anything less than root authority can access caine's interals in any way. It makes no sense to me why he'd do that. He could still override it with 'sudo' (because sudo overrides everything) but it seems counterproductive.

14. this is just quite funny. Kinger tries to remove the 'paraphernalia engine' and not only does it deny him, it tells him off for intentionally trying to torment caine when 'torment must be 100% accidental'.

15. Next we have a break to see caine tormenting the others, but when we cut back we get a whole new screen of text, and what's more, it appears kinger has been successful on accessign Caine's system internals. We know this because we can see his debug messages and all other logs. Of course, this means caine can quip about everything Kinger's doing.

16. Also, Caine starts a lockout sequence, which turns up the heat on Kinger, making him more likely to do something rash or panicky (hint hint)

17. Because Kinger is in Caine's internals, he can see this sequence beginning, and instantly tries to shut it down

18. Kinger responds by being a sneaky bitch: this is a fully custom executable that kinger made so we can't know entirely what it does but based on a general understanding of system terminology the --daemon flag means that Kinger is telling to run in the background as an idle process which would make it probably harder for Caine to fuck with

19. Caine is suitably impressed with Kinger's handiwork.

20. it also reveals that Kinger has had preparations for fucking with caine—probably since before getting put in the circus.

21. this doesn't particularly make sense to me—there's an argument flag -u first, but it would be that kinger is just too cool to run executables the normal way because if you put the ./securitysweep_stealth at the front you'd be running another custom executable, and just setting the user (what -u typically refers to) to kinger, which'd make sense.

22. this is funny as fuck to me: somehow, despite being an administrator, kinger doesn't know the admin password, and in guessing admin1234 he gets mocked ruthlessly by caine

23. ok so the next thing kinger tries is paraphernalia, which reinforces the importance of it as a concept. Definitely gonna see that one again

24. this is kinda hard to see but it looks like kinger's overriding caine with a backup, and then selecting an empty backup location. I'm sure I don't need to explain what overriding caine with an empty file would do.

25. However, it's confirmed here.

26. When the system states it's gonna take this as deleting caine, he backs out, however. (> Confirm deletion of current unstable [hidden] >N)

27. eventually, we get to this shit which is FUCKING heartbreaking. in trying to continue from a different angle, kinger is presented "with do you want to delete caine? [Y/N]". In a moment of inattention, Kinger selects Y. The IMMEDIATE next command is an attempt to rollback and undo the previous line

27. and then afterwards an attempt to cancel the process that's killing caine.

28. But it's too late.