Skip to main content

Books and Tech: "Evil Genius" by Catherine Jinks

 I read this in high school and randomly remembered it today. It's a book that made me want to be involved with network infrastructure.


                                                This is the Australian cover. Doesn't it look cool? 

It's very well-researched (though some of the concepts it touches on seem to have died in real life). Also, terminology kind of marches on - "computer phones" is something constantly said. Searching that in 2020...You get smartphones and various 'use your PC as a phone' links from CNET.


I won't be breaking down every section of the entire book.


"They sent in sniffing programs to intercept his access code."



The main character, Cadel, is making a dating website.

 He goes on hacker forums...and apparently, let them know about his plans.

 URL, name, and everything. 

Someone could have used WHOIS to find out the name of the owner - or the domain could have been registered privately.

 That’s a thing.

"Mostly I was doing application back doors, remote log-ins, tracking down personal keys, information gathering. No bombs or anything. No viruses."

I really like how it's clear Cadel doesn't know everything about systems and networks. 

He still has to study and learn, and he still gets things wrong. There's a dialogue between a professor who works with computer viruses, and Cadel says he's worked in backdoors, remote logins, access code-cracking - but not viruses.

So many stories think "the tech guy" can automatically do everything in the realm of tech, and that simply isn't true.

"We have a circuitry room [...] - it controls the security system and the phone system and the air-conditioning-[...] half the time, when you turn on the television, the garage door opens."

This book came out in 2005, and this is still not the first instance of a 'smart home' in media. Remember those 'futuristic' shows from the 70s?

There's a mention of network segmentation at the Institution he attends - The computers are "on a different switch, too" than the halon gas outlets. That doesn't necessarily mean a different network unless they're throwing some VLANs on it, which is possible.

"He knew that keyboard shortcuts - or mouse keys- were usually employed by disabled people who couldn't use a normal mouse, but he hadn't been aware that special keyboards were being made. And special mice, too, by the look of things."

I didn't know that either, so super cool. I wonder if I should re-read the next two books, if they talk about (late - 2000s) web accessibility.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory