1,438 karma · joined September 8, 2010
Funny you mention this - when I was an undergrad, the first complex group project in my EE/CE curriculum (second year; first year was all individual) had us building a web server.
I can think of two situations where design dictates you need passwords to be recoverable, but even though they exist you can (and I do :)) argue the design is wrong:
- Online aggregators like Mint/Yodlee/etc. that pass through your credentials and use screen scraping to get your data. Obviously a faulty design but in the financial aggregator case it's kind of your only choice and many customers are willing to accept the tradeoff.
- I've heard policy enforcement (e.g. "Your current password must not contain any of your N previous passwords and must meet [set of strength criteria]") used as an excuse but I don't really buy it. Not having access to the original password limits your choices for future policy enforcement (to what you could derive from the password when first set) but with a little foresight and extra work you can do fine just with hashes.
This article strikes down (1) almost by definition.
This just means the password is easily convertible to plaintext - either because it's stored in plaintext or because it's encrypted and their support folks are able to decrypt it. The former is completely indefensible, the latter is "just" very very bad.
They're only trying to do the same thing in the most superficial way. Passport was Microsoft's attempt to do single sign-on across the internet by centralizing authentication. It never really caught on. The only place I saw it was on eBay for a few years, nowadays I think it's mostly for MS properties.
Their total 2009 revenue was much higher, $23.6B (URL: http://investor.google.com/earnings/2009/Q4_google_earnings....) making non-US revenue a pretty big chunk at 53%.
Like I said, there's no requirement for credentials to be STORED in plaintext. They just need to be readily convertible to plaintext when they pull your data. I'm thinking about a system where credentials are encrypted and access to the keys are locked down (either via software or hardware) so that engineers and operations don't have unimpeded access.
> Just change "Yodlee" to "your bank" and the same exact problems happen. There is nothing special about Yodlee here.
Two things:
1a. Like I already said, many banks protect their users from losses incurred if someone gets hacked while using the bank's online portal. They'll bail me out if someone gets access to my account and takes all my money. Will they bail me out if Yodlee is used as an attack vector? That would be nice but I'm not convinced that banks/brokerages/etc. will step up and help me out in that situation. Ideologically I don't even know if banks should be expected to.
1b. Will Yodlee bail me out if an attacker uses them to steal all my money? Nothing on their website indicates that they will. Even if they did, implementing these risky features just adds more risk and uncertainty to their business for a feature which isn't ultimately that worthwhile.
2. Yodlee is special because they're an aggregator. That makes them a significantly more valuable target than one bank alone. I have various accounts at various places, if someone got access to one of them at least the damage is contained. With Yodlee they get everything at once.
> And when Yodlee asks them for their bank's password they don't realize what's going on?
You'd hope so but can't assume, you're not just selling to technical and security-conscious users. Most of Moneycenter is looks like it's dedicated to read operations. There are just a few innocuous-looking links in the account management section which opens up this whole can of worms. I came to Yodlee from Mint, who doesn't expose anything in their UI which would allow writes. That was my expectation because write access via this kind of service is unthinkable to me. After I explored a bit and realized this I removed all my accounts.
> It's exactly the opposite of what you think - by letting you know they have the password you will be more security conscious with them. If that feature did not exist you might think that they were a "read only view".
I get where you're coming from but I think this is a stretch. If they're really trying to be upfront with their users about what can and can't be done they would be more explicit than two links for "auto-login" and "show my password".
Maybe the disconnect is that I want a read-only financial aggregator (i.e. Mint) whereas Yodlee tries to do more... but from my brief experience with Yodlee I didn't really even see many things that directly did writes. Most of the value I saw was in the reading/reporting.
> Do you think it works by magic? How do you think it logs you in to the other site? It uses your password! It makes an auto submitting form that has your password in it, in plain text, right there in the javascript!
Sorry, I wasn't really clear in my haste to edit the last reply. I know auto-login is only trivially and superficially different from showing a plaintext password. That's why I didn't even mention it at first.
EDIT: Actually I think the current implementation of auto-login may be worse than showing the password in cleartext. IIRC the user doesn't have to provide Yodlee credentials a second time like they do to view their bank password.
I realize that my credentials need to be efficiently convertible to plaintext at runtime within their service. They still shouldn't be stored in plaintext (it shouldn't be easy for engineering and operations staff to see my bank password by just looking at a database dump) though. In any case, I took the leap of faith that I trust Yodlee to keep my bank credentials secret when I signed up for their service in the first place. This is not what I was talking about.
I realize they force you to enter your password first. This is good but doesn't mitigate the threat I had in mind in the first place. It's Yodlee's responsibility to minimize the risk their service poses to their customers. Unless they can be 100% sure that the person signing in with my Yodlee credentials actually is me they need to consider the implications if it's not. Off the top of my head here are two obvious situations where Yodlee's "display plaintext password" feature puts users at higher risk:
1. User accesses Yodlee from a computer (maybe theirs, maybe their friend's, maybe a public terminal) which has a keylogger installed on it.
2. User is not security-conscious and doesn't realize the implications of this feature. Thinking Yodlee is read-only (like most other competing services) they use a weaker password than they should or even use the same password for Yodlee as on other sites. They shouldn't but it's a fact of life that they do.
In both cases the attacker can get the user's Yodlee password and then all of their bank passwords. They steal all of the user's money. Banks are generally willing to play ball and cover users for their losses if their account at that bank is hacked. Will they step up in the same way if they're hacked via Yodlee? I'm inclined to believe the answer is no. I don't even know if the bank should be expected to.
When choosing whether or not to build a feature, you need to consider whether its benefits outweigh its risks.
Trusting Yodlee with my bank credentials to aggregate financial data is a risk but doing so is the entire basis for their service and provides me with a huge amount of value. It enables scenarios which are otherwise completely impossible.
This "show plaintext password" feature is a small convenience which doesn't enable any new scenarios and has some pretty significant risks.
EDIT: I'm aware of the auto-login feature but didn't bring it up because it's almost the same as displaying plaintext passwords. Practically speaking it's a tiny bit less bad because an attacker can't directly view the password and use it on other services (assuming again that users make poor decisions and use the same password everywhere). Either way I think both should be gone.
Their product, Moneycenter, has this convenient "feature" which lets you display your bank password in plaintext! It's unthinkable that someone you trust with your bank credentials would let their website be a two-way street for plaintext bank passwords.
Things like this remove any confidence I may have had in their product. The fact that a feature like this exists at all is strong evidence that they're neither thinking in a security mindset nor paranoid on behalf of their users. If someone proposed this "feature" where I work they would be laughed out of the room.
If that wasn't bad enough their support folks politely ignored me when I raised the issue and pleaded with them to turn it off. They either don't get it, don't care, or don't know how to escalate issues to people who do:
Please be assured that Yodlee considers account/data
security as highly critical and hence will not be revealed
to any other source.
We suggest you not to reveal your account login credentials
i.e answers to security questions & password, to anybody.
This will ensure your account will not be compromised.
Thank you for your feedback on the product. We appreciate it.
We are marking this Service Request as Resolved. Please let us
know if you have any questions in this regard.I didn't like it but it had a full graphical environment that was pretty accessible to students. I liked that our particular IDE/interpreter was called WinOOT (Windows Object Oriented Turing) - OOT pronounced like the stereotypical Canadian pronunciation of about, "aboot". If that's not patriotic enough, it also had a built-in graphics function named drawmapleleaf.
Re: the GSM network, I thought it was kind of ridiculous at first for the two carriers to build an entirely new 3G network when their CDMA works just fine. The speculation I heard was (1) they wanted to sell the iPhone (2) roaming revenue for the 2010 Olympics. Neither seemed like enough reason for such huge expense though. I can't find much solid information but I'm willing to bet you're right and their GSM network is available in a few places nationwide.
- Shaw is the cable monopoly in the west. Shaw used to have a presence in Ontario but they did a big asset swap about 10 years ago.
- A few areas have different cable monopolies but they're vastly smaller than Rogers/Shaw. Cogeco and Videotron, I think.
- Beyond Rogers (who bought Microcell a.k.a. Fido) and the smaller players, Bell and Telus actually teamed up and built their own GSM network. I think it went live shortly before the 2010 olympics.
- As far as I know Bell and Telus both operate their own CDMA networks across Canada. In Ontario, at least, you've been able to get CDMA service from both for a long long time.
# How long will it take before you have a prototype? A beta? A version you can charge for? Prototype - done in Feb. Version I can charge for: 8 weeks maybe? (ed: hahaha)
Just another example of how optimistic developers can be (I know I'm guilty of the same).
From what I remember it was briefly licensed to third parties but was never commercially successful. I'm really glad it was open sourced instead of being killed entirely. If nothing else would be great to use in some educational settings.
One technical caveat: it's called the ".NET Micro Framework" which implies it's language-neutral (like the rest of .NET) but it's actually interpreted and understandably only supports C#.