Did you know your ears are as unique as fingerprints?

I didn't.

Well, that's what researchers are claiming, says this story appearing over the weekend in the London Sunday Telegraph.

According to the Telegraph, Professor Mark Nixon, from the School of Electronics and Computer Science at the University of Southampton, says that:

"There are a whole load of structures in the ear that you can use to get a set of measurements that are unique to an individual."

In addition, since ears age "gracefully," Professor Nixon says, you don't have potential aging issues that can affect facial recognition systems, for example.

The Telegraph says that Professor Nixon and his team "tested 252 images of different ears and found the system was able to match each ear to a separate image held in its database with 99 per cent accuracy."

In comparison, in 2008, researchers at the University of Glasgow claimed they had developed algorithms that achieved 100%  facial recognition. I don't know if that technology has been proven in practice.

The professor believes that scanning ears could pose less of an issue than using facial or retinal recognition systems where many people need to be checked quickly, such as at airports. The UK Identity and Passport Service has been piloting facial recognition at Stansted Airport since 2008, the paper says. 

There must be something about ears and biometrics security at the University of Southampton.

Last year, I blogged about attempts at the University of Southampton to use a person's ear noise as a biometric recognition approach. No word on how that research is going.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less