tag:blogger.com,1999:blog-6582576671449934617.post1394605785608353435..comments2008-07-16T17:03:22.113+01:00Comments on Masabists: Two Factor Authentication (2FA) - Opportunity and ...Ben Whitakerhttp://www.blogger.com/profile/03756835399810128882noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-6582576671449934617.post-79447809389619172662008-07-16T17:03:00.000+01:002008-07-16T17:03:00.000+01:002008-07-16T17:03:00.000+01:00belated response to Anonymous question about "The ...belated response to <B>Anonymous</B> question about "The problem is that when the<BR/>user types in the code to sign,they have no idea what transaction they are really signing"<BR/><BR/>This is about when you are not using transaction signing, but only using a time sync, or other simple OTP to authorise transactions<BR/><BR/>i.e. "type your time generated OTP to allow this visa transaction"<BR/><BR/>it allows a man-in-the-middle can use that OTP to authorise any transaction at that time or sequence, and the end user cannot be sure that the details on screen are the same as the details being transmitted to the bank, if his screen, or network connection are under someone else' control.Ben Whitakerhttp://www.blogger.com/profile/03756835399810128882noreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-17911417468101782322008-07-16T16:56:00.000+01:002008-07-16T16:56:00.000+01:002008-07-16T16:56:00.000+01:00You are right 80n that the Pin Sentry, if used in ...You are right 80n that the Pin Sentry, if used in "transaction signing" mode, where the user types in the account and amount into the device to create a one time signature for the transfer, can beat a man-in-the-middle attack.<BR/><BR/>The caveat is that we have no idea how the Pin Sentries are creating their hashes/transaction sigs, and the generation of their time-synced login codes are not looking like anything standard/approved, as the start of each "one time code" is very closely associated to the previous codes, and is definately not using any secure hash that I've ever seen. <BR/>This means that if the code is not created in a safe way, someone may be able to adjust the details. Unless the spec for the pinsentry is published for public scrutiny, we can't be sure. (NOT FUD! It may be just fine, we just don't know! Without public standards, we have no idea, and no approved OTP standard would ever produce a sequence of codes as similar as those created by Pin Sentry.)<BR/><BR/>From the point of view of shoulder surfing, it's still vulnerable.<BR/><BR/>From a user convenience point of view, it's <A HREF="http://www.m4tt.net/barclays-pinsentry/" REL="nofollow">frustrating</A> to many users to have to carry the pin sentry, or it's peers, around with you everywhere that you want to use e-banking. <BR/>("after 15 years, pin sentry was the final straw, I'm leaving Barclays" <A HREF="http://natalian.org/archives/2007/11/08/barclays-pin-sentry/" REL="nofollow">link</A>)<BR/><BR/>We'd still maintain that bank customers should be <B>given the option to use a mobile token if they chose</B>, so that they don't have to remember and carry additional hardware. (It's a greener solution too!)<BR/><BR/>p.s. If you know which hash standard Pin Sentry uses, please let us know, at least to settle the nay-sayers.Ben Whitakerhttp://www.blogger.com/profile/03756835399810128882noreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-31964198456992266202008-07-16T16:05:00.000+01:002008-07-16T16:05:00.000+01:002008-07-16T16:05:00.000+01:00The Bait and Switch attack doesn't work with the B...The Bait and Switch attack doesn't work with the Barclays PinSentry because the user has to enter both the transaction amount *and* the account number into the PinSentry device. A MITM attack could use intercept and alter the sort-code, but not the amount or the account number. So unless you run your own UK bank where you own all the accounts (now there's an idea) then it can't be done.<BR/><BR/>PS Actually it can, but I'm not telling :)80nhttp://www.blogger.com/profile/02326276707556263139noreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-62407110505357408512008-06-17T11:34:00.000+01:002008-06-17T11:34:00.000+01:002008-06-17T11:34:00.000+01:00Very impressive article.But, I could not catch the...Very impressive article.<BR/><BR/>But, I could not catch the point<BR/>of the sentense in OTP Attacks section that <BR/>"The problem is that when the <BR/>user types in the code to sign,they have no idea what transaction they are really signing"<BR/><BR/>Please give the additional <BR/>explanation about this context.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-75325371202268098592008-04-13T10:41:00.000+01:002008-04-13T10:41:00.000+01:002008-04-13T10:41:00.000+01:00Hello anonymous from MultiFactor,It's well known i...Hello anonymous from MultiFactor,<BR/><BR/>It's well known in the security community that simple biometrics like thumb-prints have been compromised for years. (Even ultra expensive 3D thermal scanners have been <A HREF="http://www.engadget.com/2006/09/22/digital-fingerprint-door-lock-defeated-by-photocopied-print/" REL="nofollow">defeated by a photocopy and saliva</A>)<BR/><BR/>The whole point of soft-tokens for 2FA, (and innovations for the workflow of these soft-tokens, such as GrIDsure, made to overcome the hackability of software,) is to create additional security without additional hardware.<BR/><BR/>Additional hardware is expensive, in cumbersome to the users and operators, and in the case of biometric scanners, can become a huge waste of redundant hardware once someone publishes straightforward means of defeating it using <A HREF="http://www.heise.de/ct/english/02/11/114/" REL="nofollow">selotape</A>. <BR/><BR/>I'm not saying that biometrics is pointless - security is a journey, not a destination, and each component, although defeatable, adds up to make it harder to circumvent. <BR/><BR/>We'd like to get the best out of cheap, rapid to rollout, non-hardware ideas first, before trying to re-equip every user, ATM or PC in the world with hardware that may only a few years later just choke another land-fill (which are probably already receiving their first big batches of expired plastic SecureID OTP keyfobs already!)Ben Whitakerhttp://www.blogger.com/profile/03756835399810128882noreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-52681756712340185862008-04-11T05:48:00.000+01:002008-04-11T05:48:00.000+01:002008-04-11T05:48:00.000+01:00Well there is always room for improvements with te...Well there is always room for improvements with technology and when it comes to <A HREF="http://www.multifa.com" REL="nofollow">two factor authentication</A>, I believe that technologies incorporating biometrics is the future for TFA. Tokens, passwords, etc, all have large holes in their respective technologies and have been circumvented one to many times. Thumbprints and things belonging to an individual are nearly impossible to copy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-22743620440776666202008-01-23T11:51:00.000Z2008-01-23T11:51:00.000Z2008-01-23T11:51:00.000ZJust an update with news stories that show how eas...Just an update with news stories that show how easy it is to take users to rogue sites that look as if they are your real secure bank or commerce site, if you aren't using 2 channel checks to prevent MiM:<BR/><BR/><A HREF="http://www.theregister.co.uk/2008/01/23/pharming_attack_in_the_wild/" REL="nofollow">home routers hacked to redirect users to phishing sites</A> <BR/><BR/>"Given the simplicity of the attack and the potential widespread implications, we always felt that it would simply be a matter of time before it happened,"<BR/><BR/><A HREF="http://www.theregister.co.uk/2008/01/21/bt_home_hub_voip_hijacking/" REL="nofollow">VOIP systems tricked into falsifying the callerID on incoming calls, and routing phny calls via internet to ask users for confidential information</A><BR/><BR/><A HREF="http://www.theregister.co.uk/2007/12/11/dns_liar_attack/" REL="nofollow">DNS servers reporting false addresses for bank servers</A><BR/><BR/>And there are more. Clear ways for end users and banks to verify that their communications are not being subverted are definately required out on the Wild Wild Web.benhttp://www.blogger.com/profile/03756835399810128882noreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-31816360928981404502007-10-04T15:50:00.000+01:002007-10-04T15:50:00.000+01:002007-10-04T15:50:00.000+01:00Just a minor comment ... CAP readers seem to actua...Just a minor comment ... CAP readers seem to actually be perfectly capable of verifying the transactions. From 26 November 2007, for example, the use of PINsentry (Barclays CAP reader) is required when setting up a payment to someone for the first time only (or if the details of the payee are not saved), and the user is specifically asked to enter the account number of the person they are paying to as well as the actual amount. The PINsentry then generates a signature for these specific transaction details. So the user does know which transaction they are really signing but the user experience is far from optimal with the user having to key in all details manually which takes time and is prone to errors. <BR/><BR/>Of course, there is only that much that the user can possibly be asked to enter, and the user can still be tricked into signing fraudulent transaction if the attacker modifies the web page and displays a "slightly" modified account number next to the instructions, or uses, for example, the same account number but a different sort code. Thus potentially MITM attack could still be executed although with much more difficulties.<BR/><BR/>As far as getting the cryptography right :-) - we believe we have the best people in charge :-)Elena Punskaya, Cronto Ltdhttp://www.cronto.comnoreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-70151856841306075472007-09-21T23:09:00.000+01:002007-09-21T23:09:00.000+01:002007-09-21T23:09:00.000+01:00Congrats on boiling a sometimes complicated subjec...Congrats on boiling a sometimes complicated subject down to a few concise, clear paragraphs.<BR/><BR/>A Point of Clarification: Authentify does provide the ability to repeat transaction details back to the user via telephone to thwart man-in-the-middle (MITM) attacks. If the user hears transaction details differing from the expected amounts, he or she can easily cancel the transaction before fraud occurs. Several current customers choose to employ this option to solve MITM.<BR/><BR/>For the demos on the Authentify web site, we feature a simplified version that best addresses our various customer sectors and their wide variety of authentication challenges.Authentify, Inchttp://www.authentify.comnoreply@blogger.comtag:blogger.com,1999:blog-6582576671449934617.post-10134238857557320792007-09-21T11:14:00.000+01:002007-09-21T11:14:00.000+01:002007-09-21T11:14:00.000+01:00A good summation of the state of affairs, HSBC hav...A good summation of the state of affairs, HSBC have gone with Authentify, a move in the right direction, but still flawed. Most folk do not realise how much CNP fraud is costing us each year, or how easy it is.Anonymousnoreply@blogger.com