Laws of infosec

In the past I posted what I called a law of a threat hunter, but thought we could probably generalize and expand it a bit more, and in the end I came up with this list:

The law of a threat hunter

For every two most distant technologies there exist a developer that will bring them together.

The law of an end user

The end user is not a security control.

The law of a mind blowing / disrupting product / service offering

Congratulation on your Quality Assessment of an unfinished product opportunity.

The law of a vendor promise

It works in our lab. We have it on our roadmap. Defo in our next release.

The law of a infosec certification

You are certified to have a certification.

The law of an infosec advice

It’s most of the time a subjective, biased opinion.

The law of an Infosec Though Leader

“Actually”

The law of a novel cyber idea

McAfee did it first.

Beyond good ol’ Run key, Part 126

This is another quick post — this time about QT framework plugins; in fact, there is not much to write about it as it’s already fairly well documented on QT page.

The basic idea is that you can load additional plugins to programs written in QT by using either an environment path QT_DEBUG_PLUGINS or by editing a qt.conf file (creating if it doesn’t exist). If you are using IDA you might have noticed that qt.conf can be found a program’s main directory.

Luckily, plugin development has a lot of constraints and they will fail if these constraints are not met (read the article I linked to).

There is a growing number of QT-based applications hence this could be useful one day.