![]() ![]() ![]() ![]() |
|
richms: Also the support costs and added bad-will because of people getting locked out because they don't understand what case sensitivity is would be huge compared to the small chance someone may see someone type their password but not know if that was a capital or not and get in before locking the account out.
richms: Can we just PM you our customer ID to get in on anything new and improved instead?
ASBBank: ......Thank you again for all the frank feedback and comments on this thread, and we look forward to sharing the changes with you when we are able to.
- Fiona Colgan, General Manager Digital
insane:
Given the awareness should we expect your website to be updated to remove mention of case sensitivity being employed?
Thanks for your question. That particular wording you’ve linked to in the first post on this thread actually refers to FastNet Business, our internet banking platform for business customers. Our website is correct - those passwords are case sensitive and should be 8-10 characters in length. Our primary focus in the programme mentioned above is on FastNet Classic. We’ll keep you posted! Thanks - FC
Talkiet: I raised the issue with Westpac a while ago and didn't let go... Their "security people" ended up staunchly defending the case insensitivity of their online banking passwords saying that it was "entirely secure"
I know all about how legacy systems can cause unbelievable password constraints, but I would have thought a bank might have the funds to sort it... After all, it's not like they are that poor.
Cheers - N
Kyanar: I've literally only ONCE been challenged by Online Guardian - it even ignored when I did a bunch of transactions in Australia despite never having left the country in my life!
kendog: Why do strong passwords matter when you only get four attempts to login before the access is locked?
My password is not strong, but I can't see how my banking is at risk.
kenkeniff:kendog: Why do strong passwords matter when you only get four attempts to login before the access is locked?
My password is not strong, but I can't see how my banking is at risk.
I have to agree with 'kendog'; passwords need only be sufficiently entropic to withstand until brute force detection measures kick in (assuming these measures are adequately in place - i.e. unlikely to be guessed in 4 attempts).
Any backend use of these passwords (authentication / encryption) should be restricted to a sufficiently randomly individually salted derivative of the original password (i.e. a HASH).
I suspect the answer to be much more mundane along the lines of "that's all the plain-text fixed-length fields in our 50 year old COBOL system can handle"..
kyhwana2: ...
The issue is if you don't make them complex enough, you end up where people just reuse crap passwords everywhere and the whole storing them in plaintext thing doesn't help this
(Or crap passwords like "password1" that are easily cracked if you don't use bcrypt/scrypt/PDKDF2) when sites get their login databases "stolen" and publicly dumped.
ASBBank: We currently have a programme underway which will address many of the concerns raised here. At present we don't have concrete delivery timeframes that we can share with you, but we undertake to do this when we are able to. Password security is a complex area, and as it affects nearly all of our customers, we want to make sure when we introduce changes that we get it right ....
ASBBank: We acknowledge that customers want to be able to use longer passwords and passwords that are case-sensitive. As a few of you have already pointed out, two-factor authentication is available either by SMS or token if you'd prefer an extra layer of security each time you log in ....
nzkc: They're also restricted to 8 characters. I brought this up with them on Twitter - got nowhere with them.
Time to find a new industry!
|
![]() ![]() ![]() ![]() |