> Plain text protocols suck. They give you the illusion of readability...
They don't, and the readability is a feature.
I'm not sure how you conflate XML and JSON as synonymous to "protocol" and also requiring tools to filter, but than imply that a "good tag/length/value" format would somehow be superior to the former.
No, but a bank (either local or foreign) has a duty of care to ensure that a loan will not be used to finance an investment that potentially violates local or foreign laws placing said loan at higher risk of default.
After reading through that blog post it seems that David himself still has some serious doubts as to whether Bluetoad was the source of the breach.
Reading through his analysis, it almost seems that he may have fallen victim to log file pareidolia as he doesn't make it clear how a device named "Hutch" or one named "Paul’s gift to Brad" a anything more than coincidences in a very large data set.
Doing some quick analysis of the file shows that there is a UDID that has the alternate names; "Hutch Hicken" (Bluetoad CTO), "Bluetoad Support" and "Customer Service iPad" among others, but could this also be representative of an older iPad that has been a pass-me down through the company?
Somewhat more interesting and possibly more revealing are the UDIDs 'ffffffffffffffffffffffffffffffffffffffff' (occurring three times) and the small number of records not conforming to the field size and format of other records (UDIDs > 42 characters, no APNS, device/iOS version number as fourth field).
For anyone interested the following ugly and slow one-liner will print out a summary of non-unique UDIDs along with their APNS and names.
They don't, and the readability is a feature.
I'm not sure how you conflate XML and JSON as synonymous to "protocol" and also requiring tools to filter, but than imply that a "good tag/length/value" format would somehow be superior to the former.