For More Information?

Your Name (required)

Your Email (required)

captcha
Please enter the 4 letter code into box below.

Food for thought

IMG_6995The IAP were invited to attend the Food & Drink IT Summit at the National Motor Cycle Museum last Tuesday as an Associate of the event.

We were very happy to be associated with this industry leading meeting.


The event had many speakers discussing various aspects of IT in the industry, mainly discussing supply chain processing, energy and big data.

Interestingly Greggs the high street bakers/cafes are going through a £25 Million set of system changes and even in year 2 out of 5 are already reaping the rewards. They capture 50 million bits of sales data a day (BIGDATA) and use this to adjust buying of the materials and the production of shop stock.Another company were working with clients to look at power usage in their business processes. Interestingly some of these clients had the technology to monitor the use of power in their processes but failed to actually look at the reports. When they did start, a 10% power saving was found just by turning off the power switch at the end of the business day, instead of leaving equipment on.

IMG_7012
IMG_7007On the subject of Big Data, Dr. Christopher Brewster, Aston University, hit the nail on the head.It is alright capturing this data, but if you are not going to use it then it is just creates a Data Lake that everyone will drown in. You need to consider carefully what you want to capture, whether you need to and then use it.There were many other speakers and I will try and put up some of the content from them.

It was a great time to see what exciting ideas are going on in the industry and I hope the IAP will be able to do a presentation at this event next year.

Internet of Things – Wi-Fi powered devices around the corner?

This article appeared on the BBC news web site and I thought I would share it with you.
Power beamed to camera via ambient wi-fi signals

Passwords

My Bank asked me to set up an 8-character password. So I chose Snow White and the 7 Dwarves.

I can’t remember whose line that is. Tim Vine, maybe.

Anyway, IAP President, David Morgan, recently raised the password issue in a LinkedIn post. That’s prompted me to describe the system I’ve been using for several years now.

First, I select an alphanumeric sequence of half a dozen or so characters that’s meaningful to me but impervious to a dictionary attack. Let’s suppose I choose the initials and birth date of a relative, which generate:

mrd310817

Now I perform some simple arithmetic on the date component to avoid attacks that expect a date to be present. Adding 30 to each of the day and month components will do:

mrd613817

That now forms the root of all my passwords. Then I add a component that reflects the account I’m setting up. Let’s take a shopping site, Not On The High Street, as an example. Suppose that I extract the last letter of each word:

tneht

Now I divide the keyboard into two roughly equal groups. Let’s say the top row (Q – P) and the rest (A – M). Letters that appear in the top row are upper case, the rest lower case. We now have:

mRd613817TnEhd

for the whole password, unique to Not On The High Street.

Finally I add a couple of special characters, choosing a pair that appear on the same key (for a reason that will become clear in a moment). Let’s choose ‘?’ and ‘/’. Now I adopt the rule “the rightmost lower case character is followed by ‘/’ and the rightmost upper case character is followed by ‘?’”. This gives:

mRd613817TnE?hd/

Finally, I add month and year data at some arbitrary place in the string so that I can change the password every month:

mR12d613817TnE?hd/14

which would be my password for December 2014.

So I end up with a password that’s around 20 characters long, contains upper and lower case characters, digits and special characters and has no components that have dictionary or similar vulnerabilities. To save me the bother of remembering a password string, I maintain a spreadsheet that generates it automatically from my set of rules (which, it goes without saying, aren’t the ones I’ve listed here). The spreadsheet is, of course, itself password protected. I can log into a site by copying the relevant cell and pasting its text to the password field. That frustrates any attempt at keylogging.