| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

Last 100 entries

Re: Python's sad, unimaginative Enum; Re: Some explanation; Some explanation; Printing binary trees sideways; Atoms in python; About "Python's sad, unimaginative Enum"; Frustration Understood; Some good feedback here; this is fucking useless; I agree with you #nt; What would be imaginative?; Re: Enum; Enum; Python's sad, unimaginative Enum; Possible Fix; Work, Exhaustion, Vacation; VirtualBox with Centos 6.3 to 6.4, client; Matasano - Programming Lessons Learned; PDF to HTML; Alternate Substitution; Why RSA Works; Trigger; Dreaming of Death; Example: Tracing; Using Coroutines In Protocol Simulations; Python 3.3 Only; Pure Python SHA1 and MD4 Implementations; Ubuntu on VirtualBox; Starting TOR as a service on OpenSuse 12.3; 1001 Albums; Using fail2ban on OpenSuse 12.3; PPPoE on OpenSuse 12.3; Good Article on Unified Physics; It's Police (Carabineros); Linux Software for Listening to and Exploring Music; Android is Pretty Bad; Lucky Number; 3D Printing for Casting; Cover Art for MPDroid; Who'd a thought the French were so bigoted?; PS Input Signal; Small Problem with Roksan K2 Amp; Roksan K2 Amp + ATC SCM7 Speakers; Do What Makes Sense; Re: Arguing About Tests, Still; Arguing About Tests, Still; Images; Good Article on NY Drummers; Related Bug Report; Getting Python 3.3 and Virtualenv Working in OpenSuse 12.3; How I Am; Awesome video about digital audio; The Difference Between Dimensional and Normalized Databases; The rise of the new Chinese bogeyman; Updated Syntax; Very First Steps to C-ORM; The Ideal User Interface For Music Exploration; Can The Republicans Be Saved?; Rate Limiting Calls to EchoNest; Mods to Cache; Comparing UYKFG and UYKFD/E/F; Someone Else is Concerned; EchoNest-based Playlist Generator for MPD; Example Voting Results; A Heavyweight Python Cache; Identifying Artists with EchoNest; Notes on Pregalex / Pregabalina / Lyrica; The Neil Cowley Trio; Drake - Make for Data; A Reliable Python Web Service; Useful Python Date/Time Library?; Need to Sleep, But this is Good; Command Line Set Difference; Little Details...; Linux Command Line Tricks; AutoTools Tutorial; Hangman Tactics; A Tor Proxy Embedded In A Web Page; Tree (Nested Dicts) in Python; Sleeping at Parties; I Know Someone Who Hurts Other People; Light and Tea; Description of the LCS35 Time Capsule Crypto-Puzzle; Re: I can relate to that ...; I can relate to that ...; Re: It's 2012 Why Does My IDE Suck?; My Own Alternative Medicine; Nice explanation of SVM; Why and How Writing Crypto is Hard; Re: It's 2012 Why Does My IDE Suck?; Incremental Regular Expressions; BBC Map Confused at Pole; Social Media: Ground Zero in the Culture War; My Visit to the Psycho Doc; Learning Modern 3D Graphics Programming; Hope you got some crackers to go with the cheese; Re: But how easy would it be ...; But how easy would it be ...; Powerline Freq Fingerprinting of Audio; The Folly of Scientism; Cheese - Because You're Going to Die Anyway

© 2006-2013 Andrew Cooke (site) / post authors (content).

BCI Customer Service (Chilean Bank)

From: "andrew cooke" <andrew@...>

Date: Fri, 5 Dec 2008 13:42:30 -0300 (CLST)

I decide to close my account with BCI......

I call their help line, but (after waiting) I am told it is not possible
to close an account via phone or internet; I have to go to my local branch
to talk to my account manager.

I go to my branch, but the account manager is busy.  So I sit down and
wait.  The savings lady seemed to think I am suspicious and sends someone
over to check me out.  I explain that I am waiting for my account manager.

The guy he was dealing with leaves, so I approach my account manager and
tell him I want to close my account.  He asks why.  I give a vague
explanation and ask again to close my account.  He asks why again.  I
ignore him and explain I had two worries: first, that a fixed-term savings
will be OK (he says yes); second that I have outstanding debit on a
cancelled credit card.  He checks the card (while waiting on the phone he
asked me again why I wanted to cancel: "Don't you like us?").  I ask about
the remaining balance and he says I can transfer it via the Internet. 
Finally I sign some papers, am given a number to call once the account is
empty, and told to return a "multipass" (a digital source of random
numbers, connected to a timer, used to secure internet banking - quite
neat and made by RSA Inc).

I walk home and triy to move money out of my account.  The site crashes
(technical aside - it seems to only renew the session on certain pages,
not others, and if the session is bad on some pages, you get a blank
screen rather than a login prompt).

I try again and can't even login ("please try later").

I try again and transfer the money.

I call the number I was given to finally close the account.  The person
who closes accounts was busy, so they say they would call back within 48
hours.

I walk back to the bank with multipass (the internet number thing).  The
receptionist is busy, so I wait.

The receptionist, once free, won't accept my multipass.  I have to block
it first and am told to call the phone with option 3 (there are some
phones in the bank for public use).

I call option 3, but that is for savings, not cancelling things.

I call again, and try to navigate the menus.  I am put on hold.  I waited
listening to adverts.  Eventually (after 5min?) the line goes dead.

I call again, and again am put on hold.  I notice a drinks machine and get
a hot-chocolate (last cup!).  I am still on hold.  Someone finally answers
and tells me they need to transfer me.  I am put on hold again and knock
over the chocolate.  There is nothing to wipe the mess clean.  Eventually
someone answers and says that I have called the wrong number.

I return to my account manager (who is free and chatting to the savings
lady).  It turns out there are two different phones and I am using the
wrong one.

I call the other phone and am put on hold.  Eventually someone answers and
says they need to transfer me.  I wait again.  Someone answers and they
can block my multipass.  Yes!  They cancel it and say my current account
will be charged.  I say "what?".  They say there is a charge for blocking
the multipass.  I say in that case I don't want to do it.  They say I need
to talk to my account manager.

I hang up and talk to my account manager.  I try very hard not to shout. 
He takes the multipass.  I leave and walk home again.

That's it so far; still no reply back from the person closing the account.

Andrew

Santander Security

From: "andrew cooke" <andrew@...>

Date: Sun, 7 Dec 2008 10:33:52 -0300 (CLST)

I moved from BCI to Santander (at the time I was concerned about bank
stability; I have since understood more about Chilean bank regulations and
suspect I was needlessly worried - they are much more regulated here).

Anyway, the Santander equivalent of the BCI multipass mentioned above (and
required by law, I believe), is a card called "super clave" (super key)
with a matrix of numbers.  Columns are labelled A-J and rows 1-5.  Each
cell in the matric (corresponding to a letter-digit pair that describe
column and row) has a two digit number.  These appear to be random.

When you use the web page and are required to validate your identity (for
example, to confirm a transaction), you are prompted to enter the value
for four cells (eg: G5 E4 D4 H2).

There's three interesting points here.

First, it's curious what the regulations are that allow both this and the
digital device that displays numbers.  Presumably they refer to the amount
of state required to know what the user's response should be?  Does that
include the state behind the bank's selection of which cells to request?

Second, there is a possible weakness in Santander's implementation.  Each
card (and each digital device for BCI) has a serial number.  But when you
use Santander's site they display the serial number of the card!  In
contrast, BCI does not display the serial number for the multipass.  If
the cell numbers can be predicted from the serial number (and I strongly
suspect that they can) then the person viewing the page does not need to
be in possession of the card.

Third, the digital device *feels* (intuitively) much more secure.  Even if
the two approaches are equivalent (in the sense hinted at in the first
point above), the digital device has an additional comforting "security
through obscurity".  It cannot be easily photocopied, for example.

Andrew

Comment on this post