Okay, maybe the doc was exaggerating a little to get a point across to a foolish teenage kid. But it was a bad burn, charred most of the back of his hand, took off about a millimeter of flesh at some points.
No insurance. The kid's buddy drove him to the doc's office. The doc gauzed it, gave the kid some ointment, told him to come back if it got infected.
$25 from the guy's newspaper route profits in a day when $25 was a good day's pay for the kid's college student older brother, and about a half of his monthly take on the paper route. Oh, yeah, and he had to fold the papers carefully for a week or three, to avoid getting blood on them and hurting the healing skin. (No, the newscarriers' insurance didn't cover foolishness involving lighter fluid and fire crackers and old water heater tanks. And matches. Mustn't forget those.)
Yeah, that was like, 35 years ago.
It's a different world. I tend to forget. I also tend to blame much of the change for the worse on the universally insured attitude.
Okay, a broken leg. Usually, the broken leg doesn't need an ambulance. Unless, I suppose, the bone is piecing the skin and no one with first-aid training is around.
I personally think universal first-aid training would have significant advantages over universal insurance.
But, yeah, ER is going to change an arm-and-a-leg for that. Of course, if you have a family doc, you might call them and see if they're equipped to do the job. They often are, you know.
How about cancer? I could tell you a little about that one, too, but the woman in question probably wouldn't have had cancer if it hadn't been for genetically engineered foods. But that's going down another path that I suppose you might not be interested in. And it's beside the point.
Where does the money come from? Insurance companies can't operate in the red, you know.
I'd rather pool money to help the neighbor down the street with an emergency that s/he can't deal with. Although, back in the day when insurance companies were often just a bunch of neighbors looking ahead and pooling, that would be a different kind of insurance company. But I guess that's a bit beside the point, too.
The point is, the original poster's example of living on under $10,000 a year might be a little extreme, but it points in a good direction. We shouldn't be making fun of it.
Having seen both Macintosh API code and MSWindows95 API code circa MSW95's debut, I can tell you that I can't see how any court in the land with any technical training could have ruled in any way but that Microsoft had borrowed significant portions of Macintosh source code and done little beyond converting it to x86 code.
If they're so power efficient, why do they need much of a cooling system at all?
If the efficiency means a reactive cooling system, are we going to waste the saved energy pumping the coolant?
Yeah, I'm being facetious, but I get the feeling someone is checking of boxes on a feature list instead of slowing down to do real engineering. The only company that has succeeded with that is Microsoft, and they only succeeded in bleeding the industry dry and abandoning us for the highwaymen.
Way back from the days of the 8080 and 6800, I still remember the Motorola batwings logo and the iNTEL inverted caps logos. You still see the batwings, but I guess you don't see the inverted caps.
There was something appropriate about those inverted caps. Maybe that's why they eventually dropped that logo.
Wireless USB is iNTEL's chance to flog their brain damaged Wimedia UWB. It was also iNTEL's final blow to the good stuff from xStremeSpectrum and Freescale.
Trying to work around iNTEL's tactics and tantrums, Motorola tried putting their UWB into USB controllers and calling it wireless USB or something like that.
So, of course, iNTEL had to define the "real" wireless USB in the USB spec.
(You used to be able to find some of the story on wikipedia, but iNTEL has managed to scrub most of that. You may still be able to see some minor references in the Wimedia article, but that's about it. Oh, and, just in case you're curious, all that hype about Apple"s switch and all the talk of roadmaps and chipsets and junk was actually due to iNTEL lobbying Apple. Motorola and iNTEL were in talks to put the xStremeSpectrum UWB in the iPod and in their notebooks, but Apple just couldn't wait, what with all the iNTEL lobbying, bribes, promises which are now broken, etc. iNTEL rightly saw wireless as the new infrastructure, and in their anxiety to own it they have destroyed it.)
iNTEL knows one thing well, and that's how to kill good hardware.
ssl -- you can only trust your bank if your bank can trust you. They have to see your certificate, too. Where do you get your certificate?
1. I'm talking about pools as in, your ISPs main and backup DNS servers are one pool. The openDNS servers you can choose to reference form another pool. The third pool would be like openDNS, but managed separately.
The servers within the pool regularly check each other and flag and sequester rogues. When a client gets a mismatch, it would report that mismatch to all three pools, and the pools would send messages around to all servers to unwedge their caches for that IP address.
If the pools don't end up in agreement, that IP gets effectively DOSsed until a human admin can clear it.
Rogues in one pool would have to somehow gang up with rogues in each of the other pools to defeat the agreement requirement.
(Yeah, I need to think this out some more, but that's the general idea.)
2. Of course not under the same management.
3. Yes, each bank supplies a dedicated browser for its own customers, which means most people would have one browser for each bank they use, in addition to the general purpose surfing browser. Not a big deal, you can get cross platform browsers with most of the necessary functionality as library classes in Java and Perl, and probably other languages.
The most time intensive part of the implementation is generating either the list of one-time passwords or customer certificate that the customer takes home with the browser install mini-CD.
Yeah, and I'm not sure how to fit dyndns.com's services into this idea, either.
But certificates are not really appropriate for DNS when you're just surfing, even if Verisign hadn't trashed the current authorization space. Not unless ISPs start making server certificates part of their basic package. (In the end, everyone is going to have their own web server to take messages and host bulletin board/blogs.)
Certificates can only work vertically (hierarchically) within an organization. In public, certificates have to function peer-to-peer to have any real meaning at all. (Witness that huge clot in your browser cert cache.) Identity doesn't work by remote.
It may be that this multiple polling scheme is only useful for secure connections
iNTEL (wimedia) submarined the xStremeSpectrum/Freescale UWB, which was better tech, just so they could own the patents on all the pipes. That, even though Freescale offered theirs royalty-free.
Now, iNTEL insists on pushing their non-standard UWB into the USB spec.
USB is one of those "We spec our tech conservatively. Our specs are 100% better than you will obtain." technologies. Wireless USB will spill your data into the ether and USB 3, while bursting to n-gigabit, will barely be able to sustain half a gig continuous with only two devices on the line. And multiple bus controllers is an upgrade, still on the drawing board.
Save your money. If serial SCSI is overkill, and your device is not on a LAN, get Firewire. Buy printers with ethernet connectors.
Use USB for keyboards and mice and maybe scanners, like it was intended in the first place.
There is a difference between charging for a service and charging for the right to do anything close to what the service you are providing does.
The best way to kill the fud is to just simply get out there and start making money on a small scale selling pre-configured boxes the way the corner PC guy has been doing with MSWindows for years. When people see that we aren't waiting for the next big thing to make money, they'll be more likely to jump in the pool with us.
And if we are waiting for the next big thing, remember, it's likely to have the shadow of somebody's bad patent hanging over it.
What I've seen of KDE4 so far, anyone who doesn't know how to do all that on a Mac just hasn't been using the Mac.
I may change my mind, but, right now, I'm not really impressed with Fedora 9, either. Too much pseudo-innovation intended to make it easier for newbies, but missing the point. Maybe a little back-swig from sugar?
(Nothing against sugar. If they can get it to work, it's probably the best way to present Squeak as a platform for general users, although I wish they had gotten the Squeak licenses straightened out first so they could have been focusing on other things than re-inventing Squeak in Python.) But Sugar is not appropriate when super-imposed over Fedora.
Some on-line game my daughter is playing has the hero, a cute little girl's pet hamster or something, shooting love shots at penguins in one of the, what do they call those? game corners, maybe? and collecting the love-struck penguins in a line by the cute little girl.
I'd link to the game, but the wife is watching. (She hates computer games on principle.) And, if I remember right, you have to go through the candy jar (shades of Alice) and/or the album, so the link might not work anyway. Besides, my daughter would get mad at me if the site got slashdotted, and taken down or pwned.
The site has some other interesting alternative games -- cake baking class, ride the snowmobile to save the monkeys by finding them a new hotsprings, fly a broomstick through a snow storm and collect clouds like cotton candy,... . I didn't like this one at first, because of the candy jar, but I must admit, it's better than the one my son found, where mounds of something that looks vaguely like poorly baked creampuffs engage in sumo wrestling matches in various villages. And that isn't as bad as the mario look-alike in javascript that lets you create and share your own games, and that is much better than the real mario, simply because you can create your own games, and, no, I'm not a fan of games either, just an addict to watching my kids play.
Digital keychain? Don't use them. Don't let the browser remember my passwords, either. (Note that I recognize that I am trusting the browser not to cache things I tell it not to cache.)
Money? I don't bank on line.
The OS? Root can't log in from the net, you don't know the user names I can log in to get sudo access. I don't surf from those accounts, either. There's two factors, right there, for all that's worth.
I also don't go hunting for updates or packages using the surfing account.
Getting the point yet?
The internet changes nothing, really, except to add to the amount of time the device is exposed without the user thinking about it being exposed.
Actually, it does change one thing. We must disable remote login for root, must put passwords on all accounts even if the physical location is not exposed to attackers.
A weak password and a PIN? Are you joking? Or just not thinking things through? (Don't want to give you too many clues about how that goes down, in case you're a script kiddie trying out social engineering.)
If you really can't remember your strong passwords, write them down. Just remember not to keep them where people who you don't want logging in with them can find them.
In the house, I don't mind that the kids can log in. They know now that they aren't smart enough to keep my from checking what they've done, so they behave themselves. In another couple of years, I'll have to re-think things. Hopefully, I can teach him how to admin the boxes, and then it's the same question as whether I can trust him with the car keys.
At the office, it depends on what I'm working on. I usually re-install the OS when I take on something that requires keeping the secretaries and co-workers from seeing my passwords. Again, the passwords are mostly for the net side.
If I need to really lock logins down a bit, I keep the passwords in my pocket scheduler, with a bit of obscurity and steganography. Usually, I find that after three days, I remember them, so I can overwrite the entries in the scheduler. And I keep the scheduler with me.
A smart card is not significantly better for me than the pocket scheduler, although I know people for whom it would be. If the office requires me to use the smart card, I'll make sure I know where it is all the time, preferably not plugged into the card reader while I'm working.
If keeping the strong passwords in the scheduler is not good enough, the next level for me would be doing the sensitive work on a notebook that I can put in a safe when it's not in front of me.
I've thought about using an ultralight as a strong smartcard, but costs and the physical access problem always kick in before you can get any real useful protection out of such arrangements.
But when you split the token string up, you really need to think about whether you've just made the job that much easier for the attacker or not.
Maybe it makes it easier for some to remember, especially if they know someone in the picture.
(Hey, that's me! and that's {somebody I have a crush one}. There are two people that'll be easy to remember!)
Actually, even if you choose the picture, I don't see how it would be fundamentally different from a password. In the end, it's just a string of symbols, and a static one at that.
A bank account is not a nuclear bomb. It's not fun to be pwned, but it's much worse to be mass-vaporized or subjected to black rain.
Different kinds of authentication for different resources, just like the key to your house is not the key to your bicycle, is not the key to your car (if you have a car), is not the key to your locker, is not the key to your safe deposit box... .
Second, on-line, you can just effectively catenate the tokens. The attacker stores them all in her database and feeds them to some script that handles the dirty work. Sure, that the pieces are stored in different places adds a speed bump of sorts, but, in the end, it's all effectively one token.
Using out-of-band transmission for part of a challenge response could fundamentally alter the game, but maybe not, if the out-of-band medium turns out to just get on a different lane of the internet. (Telephones, anyone? Raises another speed bump, but does leave race conditions.)
Someone needs unobscured access? As in a root user, or as in the owner of the resource? (That's two separate issues, unless you can make root be the resource owner.)
That is, it would be if a few conditions can be met:
First, can everyone who needs a bank account afford a cell phone?
Second, can you load arbitrary games and other software on your cellphone? (Yeah, the race could be brutal, but if one blackhat wins it once, everyone is going to have problems.)
Third, can you make sure everyone always has their cell phone with them? What happens when someone needs to use the bank and doesn't have his cell phone? Is there an alternate route, even, perhaps just meeting the case that you're at home and your cell phone is not charged?
Fourth, is there some way around the evil Smart Card connection?
The problem here is multiple conflicting requirements.
Slashdot Mirror
Somehow, the message got through anyway.
So if we don't see a bunch of "Mine crashed too!" comments we should get worried?
Some kind of new bug in the kernel? ;-/
How about a 3rd degree burned hand?
Okay, maybe the doc was exaggerating a little to get a point across to a foolish teenage kid. But it was a bad burn, charred most of the back of his hand, took off about a millimeter of flesh at some points.
No insurance. The kid's buddy drove him to the doc's office. The doc gauzed it, gave the kid some ointment, told him to come back if it got infected.
$25 from the guy's newspaper route profits in a day when $25 was a good day's pay for the kid's college student older brother, and about a half of his monthly take on the paper route. Oh, yeah, and he had to fold the papers carefully for a week or three, to avoid getting blood on them and hurting the healing skin. (No, the newscarriers' insurance didn't cover foolishness involving lighter fluid and fire crackers and old water heater tanks. And matches. Mustn't forget those.)
Yeah, that was like, 35 years ago.
It's a different world. I tend to forget. I also tend to blame much of the change for the worse on the universally insured attitude.
Okay, a broken leg. Usually, the broken leg doesn't need an ambulance. Unless, I suppose, the bone is piecing the skin and no one with first-aid training is around.
I personally think universal first-aid training would have significant advantages over universal insurance.
But, yeah, ER is going to change an arm-and-a-leg for that. Of course, if you have a family doc, you might call them and see if they're equipped to do the job. They often are, you know.
How about cancer? I could tell you a little about that one, too, but the woman in question probably wouldn't have had cancer if it hadn't been for genetically engineered foods. But that's going down another path that I suppose you might not be interested in. And it's beside the point.
Where does the money come from? Insurance companies can't operate in the red, you know.
I'd rather pool money to help the neighbor down the street with an emergency that s/he can't deal with. Although, back in the day when insurance companies were often just a bunch of neighbors looking ahead and pooling, that would be a different kind of insurance company. But I guess that's a bit beside the point, too.
The point is, the original poster's example of living on under $10,000 a year might be a little extreme, but it points in a good direction. We shouldn't be making fun of it.
iNTEL paid shills timed this story submission to when a shill-load had mod points.
On the other hand, I just got a server issue trying to post this diatribe. Maybe the shills didn't have to time things.
iNTEL REALLY REALLY WANTS TO 0WN UR hRdwar3z
pong games.
And the ad is not from Apple, but from a store selling Apple IIs.
I'd guess, from the content of the ad, it was a store in California. (And I don't mean from the address.)
Having seen both Macintosh API code and MSWindows95 API code circa MSW95's debut, I can tell you that I can't see how any court in the land with any technical training could have ruled in any way but that Microsoft had borrowed significant portions of Macintosh source code and done little beyond converting it to x86 code.
If they're so power efficient, why do they need much of a cooling system at all?
If the efficiency means a reactive cooling system, are we going to waste the saved energy pumping the coolant?
Yeah, I'm being facetious, but I get the feeling someone is checking of boxes on a feature list instead of slowing down to do real engineering. The only company that has succeeded with that is Microsoft, and they only succeeded in bleeding the industry dry and abandoning us for the highwaymen.
one core for the mouse, one core for the display, no, make that two. Two cores for the s/ata and four cores for the USB3.
That's the monkey goes, ...
erm, loop stream detection?
maybe this iteration iNTEL will burn for their sins.
Hyuck. and yuck.
Way back from the days of the 8080 and 6800, I still remember the Motorola batwings logo and the iNTEL inverted caps logos. You still see the batwings, but I guess you don't see the inverted caps.
There was something appropriate about those inverted caps. Maybe that's why they eventually dropped that logo.
One of their old logos that you never see any more. (8080 days.)
Not so stupid, just a little early. Check wikipedia on it (looking down a bit further to future enhancements).
Firewire over RJ45!?!
On a lot of notebooks here in Japan, you have to plug the thing in with the logo down.
Wireless USB is iNTEL's chance to flog their brain damaged Wimedia UWB. It was also iNTEL's final blow to the good stuff from xStremeSpectrum and Freescale.
Trying to work around iNTEL's tactics and tantrums, Motorola tried putting their UWB into USB controllers and calling it wireless USB or something like that.
So, of course, iNTEL had to define the "real" wireless USB in the USB spec.
(You used to be able to find some of the story on wikipedia, but iNTEL has managed to scrub most of that. You may still be able to see some minor references in the Wimedia article, but that's about it. Oh, and, just in case you're curious, all that hype about Apple"s switch and all the talk of roadmaps and chipsets and junk was actually due to iNTEL lobbying Apple. Motorola and iNTEL were in talks to put the xStremeSpectrum UWB in the iPod and in their notebooks, but Apple just couldn't wait, what with all the iNTEL lobbying, bribes, promises which are now broken, etc. iNTEL rightly saw wireless as the new infrastructure, and in their anxiety to own it they have destroyed it.)
iNTEL knows one thing well, and that's how to kill good hardware.
ssl -- you can only trust your bank if your bank can trust you. They have to see your certificate, too. Where do you get your certificate?
1. I'm talking about pools as in, your ISPs main and backup DNS servers are one pool. The openDNS servers you can choose to reference form another pool. The third pool would be like openDNS, but managed separately.
The servers within the pool regularly check each other and flag and sequester rogues. When a client gets a mismatch, it would report that mismatch to all three pools, and the pools would send messages around to all servers to unwedge their caches for that IP address.
If the pools don't end up in agreement, that IP gets effectively DOSsed until a human admin can clear it.
Rogues in one pool would have to somehow gang up with rogues in each of the other pools to defeat the agreement requirement.
(Yeah, I need to think this out some more, but that's the general idea.)
2. Of course not under the same management.
3. Yes, each bank supplies a dedicated browser for its own customers, which means most people would have one browser for each bank they use, in addition to the general purpose surfing browser. Not a big deal, you can get cross platform browsers with most of the necessary functionality as library classes in Java and Perl, and probably other languages.
The most time intensive part of the implementation is generating either the list of one-time passwords or customer certificate that the customer takes home with the browser install mini-CD.
Yeah, and I'm not sure how to fit dyndns.com's services into this idea, either.
But certificates are not really appropriate for DNS when you're just surfing, even if Verisign hadn't trashed the current authorization space. Not unless ISPs start making server certificates part of their basic package. (In the end, everyone is going to have their own web server to take messages and host bulletin board/blogs.)
Certificates can only work vertically (hierarchically) within an organization. In public, certificates have to function peer-to-peer to have any real meaning at all. (Witness that huge clot in your browser cert cache.) Identity doesn't work by remote.
It may be that this multiple polling scheme is only useful for secure connections
iNTEL (wimedia) submarined the xStremeSpectrum/Freescale UWB, which was better tech, just so they could own the patents on all the pipes. That, even though Freescale offered theirs royalty-free.
Now, iNTEL insists on pushing their non-standard UWB into the USB spec.
USB is one of those "We spec our tech conservatively. Our specs are 100% better than you will obtain." technologies. Wireless USB will spill your data into the ether and USB 3, while bursting to n-gigabit, will barely be able to sustain half a gig continuous with only two devices on the line. And multiple bus controllers is an upgrade, still on the drawing board.
Save your money. If serial SCSI is overkill, and your device is not on a LAN, get Firewire. Buy printers with ethernet connectors.
Use USB for keyboards and mice and maybe scanners, like it was intended in the first place.
iNTEL bites.
There is a difference between charging for a service and charging for the right to do anything close to what the service you are providing does.
The best way to kill the fud is to just simply get out there and start making money on a small scale selling pre-configured boxes the way the corner PC guy has been doing with MSWindows for years. When people see that we aren't waiting for the next big thing to make money, they'll be more likely to jump in the pool with us.
And if we are waiting for the next big thing, remember, it's likely to have the shadow of somebody's bad patent hanging over it.
What I've seen of KDE4 so far, anyone who doesn't know how to do all that on a Mac just hasn't been using the Mac.
I may change my mind, but, right now, I'm not really impressed with Fedora 9, either. Too much pseudo-innovation intended to make it easier for newbies, but missing the point. Maybe a little back-swig from sugar?
(Nothing against sugar. If they can get it to work, it's probably the best way to present Squeak as a platform for general users, although I wish they had gotten the Squeak licenses straightened out first so they could have been focusing on other things than re-inventing Squeak in Python.) But Sugar is not appropriate when super-imposed over Fedora.
Some on-line game my daughter is playing has the hero, a cute little girl's pet hamster or something, shooting love shots at penguins in one of the, what do they call those? game corners, maybe? and collecting the love-struck penguins in a line by the cute little girl.
I'd link to the game, but the wife is watching. (She hates computer games on principle.) And, if I remember right, you have to go through the candy jar (shades of Alice) and/or the album, so the link might not work anyway. Besides, my daughter would get mad at me if the site got slashdotted, and taken down or pwned.
The site has some other interesting alternative games -- cake baking class, ride the snowmobile to save the monkeys by finding them a new hotsprings, fly a broomstick through a snow storm and collect clouds like cotton candy, ... . I didn't like this one at first, because of the candy jar, but I must admit, it's better than the one my son found, where mounds of something that looks vaguely like poorly baked creampuffs engage in sumo wrestling matches in various villages. And that isn't as bad as the mario look-alike in javascript that lets you create and share your own games, and that is much better than the real mario, simply because you can create your own games, and, no, I'm not a fan of games either, just an addict to watching my kids play.
My password gives access to my posts on /. .
Oh, my mail? Different password.
Digital keychain? Don't use them. Don't let the browser remember my passwords, either. (Note that I recognize that I am trusting the browser not to cache things I tell it not to cache.)
Money? I don't bank on line.
The OS? Root can't log in from the net, you don't know the user names I can log in to get sudo access. I don't surf from those accounts, either. There's two factors, right there, for all that's worth.
I also don't go hunting for updates or packages using the surfing account.
Getting the point yet?
The internet changes nothing, really, except to add to the amount of time the device is exposed without the user thinking about it being exposed.
Actually, it does change one thing. We must disable remote login for root, must put passwords on all accounts even if the physical location is not exposed to attackers.
A weak password and a PIN? Are you joking? Or just not thinking things through? (Don't want to give you too many clues about how that goes down, in case you're a script kiddie trying out social engineering.)
If you really can't remember your strong passwords, write them down. Just remember not to keep them where people who you don't want logging in with them can find them.
In the house, I don't mind that the kids can log in. They know now that they aren't smart enough to keep my from checking what they've done, so they behave themselves. In another couple of years, I'll have to re-think things. Hopefully, I can teach him how to admin the boxes, and then it's the same question as whether I can trust him with the car keys.
At the office, it depends on what I'm working on. I usually re-install the OS when I take on something that requires keeping the secretaries and co-workers from seeing my passwords. Again, the passwords are mostly for the net side.
If I need to really lock logins down a bit, I keep the passwords in my pocket scheduler, with a bit of obscurity and steganography. Usually, I find that after three days, I remember them, so I can overwrite the entries in the scheduler. And I keep the scheduler with me.
A smart card is not significantly better for me than the pocket scheduler, although I know people for whom it would be. If the office requires me to use the smart card, I'll make sure I know where it is all the time, preferably not plugged into the card reader while I'm working.
If keeping the strong passwords in the scheduler is not good enough, the next level for me would be doing the sensitive work on a notebook that I can put in a safe when it's not in front of me.
I've thought about using an ultralight as a strong smartcard, but costs and the physical access problem always kick in before you can get any real useful protection out of such arrangements.
But when you split the token string up, you really need to think about whether you've just made the job that much easier for the attacker or not.
Maybe it makes it easier for some to remember, especially if they know someone in the picture.
(Hey, that's me! and that's {somebody I have a crush one}. There are two people that'll be easy to remember!)
Actually, even if you choose the picture, I don't see how it would be fundamentally different from a password. In the end, it's just a string of symbols, and a static one at that.
I see.
(My bad for not looking further up the thread.)
A bank account is not a nuclear bomb. It's not fun to be pwned, but it's much worse to be mass-vaporized or subjected to black rain.
Different kinds of authentication for different resources, just like the key to your house is not the key to your bicycle, is not the key to your car (if you have a car), is not the key to your locker, is not the key to your safe deposit box ... .
Second, on-line, you can just effectively catenate the tokens. The attacker stores them all in her database and feeds them to some script that handles the dirty work. Sure, that the pieces are stored in different places adds a speed bump of sorts, but, in the end, it's all effectively one token.
Using out-of-band transmission for part of a challenge response could fundamentally alter the game, but maybe not, if the out-of-band medium turns out to just get on a different lane of the internet. (Telephones, anyone? Raises another speed bump, but does leave race conditions.)
Someone needs unobscured access? As in a root user, or as in the owner of the resource? (That's two separate issues, unless you can make root be the resource owner.)
That is, it would be if a few conditions can be met:
First, can everyone who needs a bank account afford a cell phone?
Second, can you load arbitrary games and other software on your cellphone? (Yeah, the race could be brutal, but if one blackhat wins it once, everyone is going to have problems.)
Third, can you make sure everyone always has their cell phone with them? What happens when someone needs to use the bank and doesn't have his cell phone? Is there an alternate route, even, perhaps just meeting the case that you're at home and your cell phone is not charged?
Fourth, is there some way around the evil Smart Card connection?
The problem here is multiple conflicting requirements.