bugtraq - Re: Defeating Citibank Virtual Keyboard protection using screenshot method

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1179096294.4B0A1AE@fn13.dngr.org>
Date: Mon, 14 May 2007 08:44:50 +1000
From: Paul Foote <pfoote@...il.com>
To: Bugtraq mailinglist <bugtraq@...urityfocus.com>
Subject: Re: Defeating Citibank Virtual Keyboard protection using screenshot method

On Sunday, 13 May 2007 2:25 am, Hugo van der Kooij wrote:
> In fact the system used by the major Dutch banks is audited rather 
> extensively. The OTP system is based on an external smartcard reader 
> and a smartcard application on the bank card. They have no physical 
> connection so the web interfcae will present you with a challenge and 
> you must use that challeng, your card and your pin to generate the 
> proper response. Then you have to type in this response.
>
> It is a combination of:
>  - What you have (the card with the smartcard application)
>  - What you get (the challenge from the server)
>  - What you know (your pincode)

A few banks in Australia are using a similar idea: Bank of Queensland 
offer a device that every time you press a button it gives a code that 
their website expects in addition to your net banking username+password. 
Commonwealth Bank do the same thing but instead of a device they do a 2 
stage login, first stage being username+pass the second being a code 
sms'sed to a pre-registered mobile phone number.

--
Paul Foote