Monday, 18 September 2017

My name is Cariad Keigher and I am transgender

One of the things that I've struggled with is an overall dislike for myself. I've dealt with it since my teens, resulting in anger, depression, and anxiety. Treating it as a mental illness has only either made me numb to life itself or caused others around me that I hold dear to find me frustrating or exhausting to deal with. This is not healthy; and earlier this year I opted to address it head on.

My name is Cariad Keigher and I am a transgender woman. I've been aware of this since 12-years old and this year I started to transition. My preferred pronouns are "she" or "her"--simple as that. If you're curious about the name, it's Welsh (meaning "sweetheart" or "dear") and I chose it because I wished to keep my first initial but was rather dismayed with the options for Irish names, so a short hop across the pond I went.

"Caoimhe" was a consideration but I already have enough problems with my last name!

Hi! I may not seem super feminine-looking but trust me, I am a girl.

I've always been jealous of other women. The experiences they have, the ability to socialise as one, the acceptance to present as one, and the "normality" to be called one have to me for as long as I can remember been a distant thought. I always thought of it as ludicrous, that this was just me being ill, and that I was a "creep" because I never fully understood what I am.

For many years, it never occurred to me that transgender women can in fact be lesbians and it wasn't until I fully separated the concept of gender and sexuality myself did any of that make sense. I felt caught in a trap until then; thinking that my thoughts and desires had to be something else. Experiences as a teen in terms of the women I'd date and how I felt about myself never added up and as a result took me decades to come to this conclusion.

There are of course lots of consequences for my choosing to transition. Men are very much dominant and hold privilege in the technology sector, something of which I benefited greatly from. I may lose friends, family members may object, and there many in the general public that hold disdain for those that identify opposite that of what they were assigned at birth. Transgender persons have found themselves accosted, discriminated against, assaulted, and even murdered just because there are members of society that are unable to keep their prejudices in check.

It has meant a lot of changes in my personal life that have not been easy to accept. This is not a topic I wish to dive into in this entry though.

Studies point out that at least a third of all transgender persons contemplate suicide compared to 5-15% of the youth population--and this is just for Canada, a country that has transgender rights enshrined in federal law. Suicide is a difficult subject for me to discuss however; I will refrain from discussing it further.

The point here is simply this: I didn't choose to be born this way. Nobody chooses their sexual orientation, gender identity, skin colour, or the place they're born. I don't get why I was born nor why I am the way I am, but what I will say is that I will live life as honestly as I can.

I have my foot on the accelerator pedal and so far I have no desire to take it off.

I highly recommend reading Julia Kaye's Up and Out web comic. (Source)

One anecdotal story I'll share is how during Pride Vancouver this past summer, I saw three teenage girls hanging out together. Two of them appeared to be cisgender whereas the third was seemingly "different". There was no indication whether or not she was transgender and it's irrelevant to the story why she stood out from the others, but the point was that she was accepted by the other two and they were having a good time at Pride.

While I will never get to experience what she has, I will say that I am happy to see that those younger than me have resources available to them that were otherwise unthinkable when I first became aware of myself. There are many out there who have opted to accept others for what they are and I feel that this is the best way as a species to move forward.

There are a few things you can do to help me here:

  1. Please do not refer to my former name as I will not answer to that. My former e-mail address is still valid and will remain so for the foreseeable future. If you have me in your contact list under this name, please change it. You can shorten it to "Cari" if we know each other personally.
  2. The use of pronouns is important.
  3. I am not "transgendered", "tranny", "transsexual", or whatever--these are terrible terms and you should avoid them. If you can, call me a "trans woman" or even better, a "woman".
  4. Don't feel bad if you somehow make a mistake here. I still do.
  5. I don't need any financial support so if you want to do something to benefit me, please donate to your local LGBTQ+ group. I live in a country that offers help to transgender persons in the healthcare system so I will never be asking for help there.

Many people have helped me over the past year and I want to pay it forward as that seems to be the best way considering my privilege. Much of what I am dealing with is being documented just so someone else doesn't have to be as blind as I have been in trying to sort out things.

Sarah is an excellent person and you should follow her Twitter.

Additionally, I am paying it forward by offering ten free copies of Queer Privacy, a book compiled by Sarah Jamie Lewis. I cannot recommend the book enough if you're a queer person and are interested in privacy in the digital age. These books are already prepaid for by me so do not hesitate to use the details below to get yourself a copy. I want everyone to read this book.

At the time of this writing I don't have the details ready but I will make it available via Twitter!

Lastly! If you're still following my old Twitter account, it has been retired. I plan to delete its tweets over the coming weeks and have migrated to a new account under the name @KateLibC. It'll still cover my antics and others' in information security, but I guess you'll be seeing more gender and sexuality-related content as well.

Last lastly! The use of "Kate" in my online handle has nothing to do with my name. It's a play on the name "Kate Libby" from Hackers. You should get the rest if you've dealt with programming or a UNIX-like operating system.

For certain lastly! You can always send me questions you may be embarrassed to ask by visiting my CuriousCat profile. I will pick and choose which questions I answer however.

Monday, 1 May 2017

Working with the McAfee Web Gateway API

If you ever find yourself in a situation where you need to work with this device via its API, be prepared to hate everything about it.

With nothing in the way of things like API keys or anything remotely close to it, you're stuck using a username and password to do any sort of remote commands. To add to this, you'll also need to make sure that you do not use an account that you want to log in with manually because the appliance cannot discern between multiple sessions for whatever reason. Also, if you find that you've accidentally lost your session and then want to do anything further, you'll have to go make a cup of coffee, do a little of yoga, and then hopefully after ten or so minutes it'll allow you to work once again.

That is the magic of the McAfee Web Gateway REST API. And because I do not wish to let anyone else experience the nauseating pain that this appliance gave me, I have been a nice person and wrote an entire Python interface so you can save yourself the frustration provided by its terrible, inaccurate documentation.

Some of the features I wrote into it include the following:

  • Listing appliances
  • Listing lists
  • Viewing list entries
  • Inserting into lists
  • Saving data
  • Avoiding a stroke

I gave it a thought to write some more features into it but opted not to because I was just interested in blocking content.

Also, if you do decide to make it block content, make sure that you do not have any sort of short timeouts on whatever you have because if you have any appliances that are connected via a slow network link (like less than 10 Mbit), you'll have to wait until they're updated because when you talk to the central appliance it pushes out the new XML config you just created to all of them and then gives a response.

Anyway, hopefully this saves you a few grey hairs.

Tuesday, 14 March 2017

Beating BSides Vancouver 2017 CTF using a search engine

A group separate from the BSides Vancouver organizing team put on a CTF the past two days (archive) with a prize of a four-month SANS Netwars Continuous Subscription. However, it appears that the CTF organizers (who are separate from the conference organizers) have been engaging in some shenanigans with regards to the challenges.

This came on my radar when a TinyCTF challenge from 2014 showed up and I ended up looking at the other challenges to see what was done. The ones that were not borrowed from TinyCTF were most documentation or forensics-related which I assume was created by the CTF organizers.

Challenge Name Type Points Flag Details
Choo Choo! Puzzle 50 snc 52 Link
Fore! Web 250 it's_a_h0le_in_0ne Link
Undocumented Instruction in x86 Puzzle 75 LOADALL Link
BFF..or P? Puzzle 100 esolangs_for_fun_and_profit Link
It's OK to be a CISsy! Puzzle 250 3,8,7,4,9,5,6,1,2 N/A
Hail Caesar Crypto 50 ITSHAPPENING N/A
Crypto for you sir! Crypto 100 no_this_is_not_crypto_my_dear Link
First time flag test Crypto 100 hello_world Link
János the Ripper Crypto 250 ev3n::y0u::bru7us?! Link
Movie Time! RE 100 poppopret Link
Ooooh! What does this button do Dexter? RE 250 w4nn4_j4r_my_d3x Link
Gandalf! RE 500 s0me7hing_S0me7hinG_t0lki3n Link
Sound Bites! Misc 250 infosec_flagis_sound Link

The annoying aspect of this is that with 'Crypto for you sir!' it ends up being wrong when you solve it. Here is the ciphertext:


When decoded it comes out as this:


You'd assume that based on that you'd want to use flag{no_this_is_not_crypto_my_dear} as your flag, but nope, get rid of the "flag" and curly braces as well. This lack of flag formatting behaviour repeated itself across all of the other answers that were borrowed from TinyCTF.

Now in their defence, they did say in the challenge that you are to submit it without the braces, but why not just write your own caesar cipher? Automated deciphering was used here, so why not just use a generator to create something original?

Of the 2,325 points I list above, 350 were solutions that they likely created themselves--I did not bother attempting the rest of the challenges. In the case of Choo Choo, it was literally watching a YouTube video and looking at the markings on the second train to come up with an answer. Of course, since there was inconsistencies across the flags where you either used underscores or you didn't and since there were at least three markings on the train, you pretty much stood a good chance to get it wrong because they only gave you four chances to get it right.

Actually, take away 50 more points because as I was writing this I decided to just look into Choo Choo further and it turns out to have been used for Ghost in the Shell Code. Really, could have they just looked for some other railfan video? This explains the further flag inconsistencies going on here.

In fairness, there were challenges put in place to allow for all backgrounds in information security to partake, which explains why you'd get questions like PCI-DSS questions about whether VoIP is in play in an assessment (which is asked twice) or how to order CIS controls (CISsy), but then why turn around and ask about undocumented Intel instructions to access extended memory?

Reading documentation for a CTF is not unusual but this just reeks of laziness.

At this point I would like to say that I am done covering the problems here, but then it gets worse: even the list of tools they suggest in the CTF are borrowed from AwesomeCTF without any attribution. Granted, the list is licensed in a manner where zero attribution is required, but it just goes to show the level of originality put into how things were being done by the CTF organizers. At least the rules appear to have been written by them.

But since one of the rules is to not share the flags, doesn't that mean that the CTF organizers themselves are breaking their own rules?

Also, how long did they take to put this together? The hints are baffling me.

Almost a year? Surely they could have at least changed the flags or come up with better content than whatever this was. Did they use these challenges for another event? It is my understanding that the same team ran something similar for BSides Calgary.

In full disclosure here, I was previously a conference organizer for BSides Vancouver and in 2015 I helped coordinate the first proper CTF using challenges we actually wrote ourselves with anticipated solutions for each of them. I know that it is fact that the conference organizers are again not the ones who oversaw the event (I did speak with them about the matter), so blame for the reuse of these challenges should not fall on them.

However, for the CTF organizers, why did you do this? Was this a mistake? How? If you're going to offer up a prize, put some thought and originality into your work.

Friday, 10 February 2017

Running AFL on Bash for Windows

Recently I wrote about using Virtual Machine Manager in Bash on Windows (or Windows Subsystem for Linux aka "WSL"), and since then I have been playing around with getting other utilities I use in a native Linux environment.

One utility is American Fuzzy Lop (AFL), a fuzzing tool for finding vulnerabilities within Linux ELF binaries. It has been since ported to fuzz Windows PE binaries natively, but since we're able to run ELF binaries within WSL, why not fuzz them too?

If you're running Bash on Windows and have tried to compile AFL before, you probably have run into this problem:

shmget() failed

This error results from WSL having limitations on shared memory--specifically the lack of /dev/shm. By default, AFL will outright refuse to compile because these system functions simply do not exist.

One of the most recent builds of Bash on Windows includes support for shared memory functions that AFL requires in order to compile.
Along with support for the following shared-memory syscalls which are widely used by a number of Linux tools including PostgreSQL.

  • shmct
  • shmget
  • shmdt
  • shmat
The catch here is that the mainline Windows 10 version of WSL has yet to be updated to address this problem so you must be in the Windows Insider program in order to reap the benefits of these functions. Once you've enrolled and have updated, you can confirm the version of WSL by checking the version of Linux using uname.

If you're up to date you should see this version:
Linux mycomputer 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux
If you're not up to date then it'll show the following:
Linux mycomputer 3.4.0+ #1 PREEMPT Thu Aug 1 17:06:05 CST 2013 x86_64 x86_64 x86_64 GNU/Linux
Assuming you're successful you should be able to follow the instructions provided by AFL and begin fuzzing.

I'm still testing it out but at least we now know that it should compile and run fine on the surface. You will notice that the way the screen is drawn that it will look a bit wonky while running.

One thing I feel the need to add is if you're using an SSD, AFL is definitely a great way to reduce the lifespan of your drive. Instead, I recommend creating a RAM disk within Windows and then accessing it normally. I have tested ImDrive and it works just fine within WSL.

Friday, 27 January 2017

Anti-virus is worthless

I get a kick out of reading reactions by the anti-virus industry, rose-coloured glasses views from academia, or anecdotes from those who work in the IT industry whenever someone writes a constructive criticism of anti-virus solutions.

Let me put it out there before I go any further, Robert O'Callahan is correct when he says that you should disable your anti-virus solution--unless it came with your operating system such as it does in Windows 10. And for disclosure here: I did briefly work for an anti-virus vendor.

Whenever an argument is made for the value that anti-virus doesn't provide, you are bound to get the following reactions from anyone I mentioned before:

  • [Insert testing programme here] has given [AV product] the best detection rate in the industry for [year]!
  • I use [AV product] and I have never gotten malware.
  • [Software vendors] should open up their APIs to make anti-virus much easier to work with.
  • The anti-virus industry creates the malware.
  • If you went without anti-virus for [period of time] you'll eventually catch malware!
I could go on and on about these reactions but I think this well summarizes the absentmindedness that certain pro-anti-virus persons give:

It's obvious which light bulb a sane person would choose.

Tavis Ormandy has demonstrated extremely well through Google's Project Zero initiative (and before that with Sophail) that anti-virus applications have ticking time bombs sitting within their suites. From remote file retrieval, installing shady remote access tools, improper sandboxing, Node.JS debuggers, to permitting possible collisions in SSL certificates are just a sampling of the nearly five dozen vulnerabilities discovered by one single human being. 

That is just what is being published in the open. If you are aware of an anti-virus vulnerability, Zerodium will pay for remote code execution attacks. There have been suggestions that they go for at least $20,000 to $50,000 USD.

So let's pretend now that the problems with anti-virus being typically poorly coded just simply don't exist: are they still worth using?


The commonly forgotten trait about anti-virus is that it either has to predict the malware's existence through heuristics or it has to have knowledge of its past artifacts via signatures. Both of these require teams of people to write the protections to handle either approach while at the same time being mindful of the fact that for every detection they make, they could be missing a thousand others. The dirty secret that the AV industry really hates to talk about is how their approach simply cannot scale.

Part of the approach that a majority anti-virus industry has opted to go about deflecting this is to add more value to their product by redefining themselves as "endpoint solutions". In the past decade, we've seen features like application whitelisting, web content filtering, and physical device control in order to make it seem like their product is more useful than if it was just simply doing AV.

Another angle to take is come out with outlandish claims that your product can detect everything using some new obscure method that nobody else in the industry has come up with. 

This is sort of the approach that Cylance has taken where they claim that their magic algorithm can stop malware even if they haven't seen it before. Unfortunately, there are lots of anecdotes that their product has an extremely high false positive rate which sort of makes sense if they can predict future malware: detect everything and anything without pause. 

However, testing their product and being open about what your experience with them is difficult because they require an NDA to get a proof of concept demonstration going in an enterprise environment. In one instance, a friend of mine was demonstrating it, posted about it on an open forum, and apparently Cylance responded negatively, citing the agreement. 

This job posting by them reveals a lot however:

I guess all of these contractual restrictions make sense seeing that the engine is likely coded in C#, as suggested in this job posting. The whole anti-virus industry relies on obfuscation of their practices and it's either going to be done by being closed source which is really everyone or by making it so nobody can actually poke around by stipulating such in a contract.

No vendor has a better approach than the other; they're all the same. You either have it never firing on actual malware or have it fire on everything as if it were Chicken Little.

So let's make some useful suggestions here on how to actually protect your computer:
  1. Use the anti-virus your operating system provides. If it doesn't have one, don't install one. Likely if it doesn't have one already, it's either a Mac, you run Linux, or your Compaq from 2005 needs to be replaced with something running Windows 10.
  2. Keep the operating system up to date. If Windows 10 rebooting on you is so inconvenient, you're a lost cause--the most recent update lets you defer up to a month by the way.
  3. Install ad blockers and use something other than Internet Explorer or Edge such as Chrome which sandboxes things fairly well.
  4. Don't follow random guides on the Internet to allow you to make changes to your system that somehow make things go "faster". More often than not they're done by people who don't know what they're doing.
  5. Don't use pirated software or pirate any content. Netflix is cheap, Spotify is free if you tolerate ads, and honestly there are tonnes of open source solutions for whatever you need to do.
Don't waste your money or bandwidth on an anti-virus solution that will just create more holes.

Anti-virus is worthless.