Our town library has a heavy wooden door that opens outward. When I come up to it from the outside, I pull it open and hold it for anyone about to exit.
My confusion is about what to do when I approach the door from the inside. Today I could see an older lady approaching from the outside, and my inclination is to open the door for her, but how? I would either have to try to awkwardly hold the door open from the inside so the lady could pass or awkwardly go out first so I could hold the door from the outside.
Both approaches are, well, awkward. If I try to hold the door from the inside, I’ll be in the doorway, pretty much blocking it. If I go through first I force the lady to back up.
I think the best approach may be to pretend I am heading downstairs to the childrens’ room and not trying to leave at all.
Author: stewart
Civilians killed by police
Before I start, the murder of police is not acceptable. The killings in Dallas and Baton Rouge appear to have been committed by disturbed individuals, representing no one but themselves. Parenthetically, the sole comment by the NRA about these murders was to send condolences to the families of the officers. It seems to me the least they could do is to revoke the membership of the killers.
Regarding the killings of civilians by police, I have a modest proposal.
From what I’ve learned, there are about 1000 civilians killed every year by police in America. These deaths are not tracked[1], other than by a few journalists trying to understand. What has happened over the past few years is not that many more people are being killed, but that we are starting to hear about them, and to see them by video. Sometimes, perhaps most of the time the use of lethal force is justified, but in an unfortunate number of cases it is not.
My own outrage arises from three factors:
- The people being killed are disproportionately black.
- An alarming number of killings seem to be made by ill trained, incompetent officers who should never have had a badge in the first place.
- Very little is being done to reduce the carnage. Cities try to avoid consequences and try to hide evidence until the affair fades away. District attorneys sandbag their cases (if any) against police to avoid damaging their relationships. Police unions and non-involved officers tend to support their incompetent fellow officers.
I don’t think that bringing murder charges against police is the answer. Prosecutors, judges, and juries give a lot of deference to police, and it is very hard to get convictions. When cases fail, even when they fail for good reasons, the public is outraged again, and the government shrugs and says “we tried”. I also don’t want police to be so nervous about personal liability that they can’t do their jobs. In egregious cases, sure
So what should be done?
My proposal is that for any civilian killed by police, there should be an automatic five million dollar award to the victim’s family unless the police have unambiguous video and audio evidence showing the individual presenting a clear threat and that the police exhausted every non lethal means for resolution. Further, there should be an immediate threat not created by the police themselves. No-knock warrant? Better be sure you don’t kill the residents. Broken tailight? It’s the policeman’s responsibility to make sure the occupants of the car go home safely.
What about suicide by cop? There are likely people so desperate that getting themselves killed for a large payday looks like a good idea. That’s where the video comes in. If there is clear video evidence, then no payout. In addition, as police learn to defuse situations and develop better non-lethal tools, the rate will drop.
What about the large civil penalties already paid by cities in egregious cases? They haven’t done much to solve the problem. The awards have to be immediate, public, and humiliating for the chain of command and the politicians. Too often, such awards are years too late and never reported. Perhaps the awards should be scaled according to the complaint record of the officers. That should give the chain of command incentives to remove bad apples from the barrel. If police union contracts forbid firing, fine. Bad officers should report for duty and just sit somewhere where they are not killing people.
My point is, the police have a responsibility not to kill unarmed or innocent civilians. It doesn’t really matter if the killing is not judged criminal and the officers involved are not found liable. The police have a responsibility not to kill civilians.
[1] There needs to be central reporting of every police involved killing.
Robot Killers
According to the Obama administration, between 2009 and 2015, 473 drone strikes killed about 2500 combatants and about 100 non combatants.
Last week, the Dallas Police department used a robot to kill the police shooter.
As far as I know, all of these events have had human operators, supposedly exercising human judgement.
The thing is, many reports about drones and robots leave one with the impression that these are autonomous devices, without a human in the loop. It isn’t like that.
I do not think there is a real difference between a sniper on a hilltop killing from a mile away and a drone operator killing from 10,000 miles away. Both have a human pulling the trigger. We can and should talk about ways to further reduce non-combatant deaths, but sniper rifles and drones are much safer for our guys than bayonets and hand grenades.
The real discussion ought to be about autonomous vs human-in-the-loop.
The unfortunate fact is, we already have lots of truly autonomous devices killing people on their own initiative. They are called land mines.
Email customer service
May I rant?
Many organizations offer email customer service. The problem is that the service is generally crap. Here’s why.
Slow response. Most places respond immediately to an email, with “we received it, but we’ll deal with it later.” For example, Express-scripts says
All inquiries are handled on a first-come,first-served basis and most are responded to within 24 – 72hours.
Useless answers. Yesterday I tried to use the secure email at UBS.COM. The service has no way to originate a message and no apparent way to reply to a document. (I had to print and sign something and send it back.) The eventual reply was Windows specific and told me to use the new online signing feature of Acrobat, which I don’t have.
The useless answer problem is really a symptom of email being open loop. With a telephone call or online chat you can have an exchange to zero in on the actual problem and any constraints. With email this usually doesn’t work.
When offered, I try to use online chat these days. You don’t have to actively listen to badly designed telephone hold systems, the exchange is interactive, and best of all, you can get a written record of what happened, when any promises are made.
Stingray countermeasures
A Stingray is a cell tower lookalike device. It broadcasts its presence and nearby phones connect to the Stingray thinking it is a legitimate tower. The Stingray can then log each phone or act as a man in the middle to incercept call metadata, text messages, or even call contents.
There are a number of public databases of legitimate cell towers. For example, http://opencellid.org Some databases are government, for example, the FCC license database, while others are crowdsourced.
It should be possible to modify a phone to only connect to towers which are legitimate by checking the purported tower ID against a cached copy of the database for the local area. A stingray could, of course, use the id of a real tower, but that would disrupt communications in the whole area. This might not prevent the Stingray from logging the presence of such a phone, since the Stingray could hear the protocol handshake with the legitimate tower.
It should also be possible for a phone to passively listen for tower broadcasts, and to compare the tower ID against the database, An unknown ID might be a new legitimate tower or it might be a Stingray.
It is likely quite difficult to get at and modify the low level radio software in a commercial smartphone, but there is a complete open source suite of cell infrastructure software at http://openbts.org
That code could serve as a starting point for a software defined radio device for detecting and tracking Stingrays. One could make a box with a red light on top which lights up when there is an unknown tower in the area.
In some areas, use of Stingray devices requires a warrant, but this is not universal. The courts have also determined that use of location data from legitimate cell towers does not require a warrant
.
.
PIN Escrow
The FBI has dropped their request to require Apple to write code to unlock the terrorist iPhone. Supposedly a third party offered a way in. Yesterday the FBI said they did get in, so they no longer need Apple’s help.
For those whose first instinct is to distrust the government, this looks like the Justice department realized they were going to lose in court and hastily discovered a way out. “Never mind”. This preserves their option to try again later when public opinion and perhaps law would be more on their side. I am a little reluctant to think Justice would outright lie to a federal judge, but it wouldn’t be the first time.
This morning on NPR there was a different sort of heartbreaking story. A woman and her baby were murdered, and there might be evidence on the woman’s phone, but it can’t be unlocked. So what to do?
My idea is “PIN Escrow”. Everyone should have a letter written with a list of their accounts and online passwords, to be opened by someone in the event of death or disappearance. Everyone should have a medical power of attorney and so forth as well, to give a family member or trusted friend the power to act for you in the event of a sudden disability. Just add your smartphone PIN to the letter,
In the alternative, one could write an app that encrypts your pin with the public key of an escrow service and sends it off. This facility could even be built into the OS, with opt-in (or even opt-out, after a sufficient public debate), so it would automatically track changes. The government could operate such a service, or it could be private. There could be many such services. Some could be offshore. Some could use key-sharing for the private key, so PIN recovery could not be done in secret.
Let’s leave it up to individuals whether they want someone to have the power to unlock their phone in the event of an emergency.
From a security perspective, a PIN escrow service would be a dangerous and attractive target, so such a thing would have to be well designed in order to be trustworthy. It should be kept offline, with no network connection. The private key should be in a hardware key module. Several people would have to collude in order to unlock a key, and there ought to be hardware safeguards to prevent bulk PIN recovery.
This is not a general back door for government surveillance, it wouldn’t grant remote access to a phone. It wouldn’t be useful for hacking into criminal’s or terrorist’s phones (if they are smart), but it might help in cases where the phone owner is the victim of tragedy or accident.
And if you change your mind about having your PIN escrowed? Just change your PIN.
Apple v FBI
I’m beginning to build up a full head of steam. The first step seems straightforward. I’m going to write my congressman. It may not have much effect, but if enough of us write, it might.
Here’s my letter to Massachusetts Senator Elizabeth Warren. I’ll be sending similar letters to Sen. Ed. Markey and Rep. Katherine Clark.
2016, March 16
The Honorable Elizabeth Warren
317 Hart Senate Office Building
Washington, DC 20510
Dear Senator Warren:
I write about the Apple FBI affair. Please oppose any attempt by government to weaken the security and privacy of all Americans by demanding security “backdoors” in our technology or to require the conscription of Americans or American companies to weaken their own security.
First, regarding backdoors. I hold a PhD in Electrical Engineering and have worked with computer systems and computer security for over 40 years. I am coauthor of the well-regarded book on E-commerce systems “Designing Systems for Internet Commerce.” In other words, I know quite a lot about this area. There is simply no way to create a backdoor that does not also reduce the security of the system for everyone.
Second, speaking as an ordinary citizen, I do not know how the courts will rule on the government’s request to use the All Writs Act to compel Apple to write software to unlock the San Bernadino iPhone, but my own view is that the constitution does not and should not allow it.
The government is being deliberately disingenuous when it claims this case is only about one terrorist’s phone. I have no sympathy for the killers, but the privacy and security of everyone is at risk should the government prevail. Should that happen, I expect you to propose and support legislation that outlaws backdoors and forbids the conscription of individuals or companies into the government’s service. This has happened before. In 1980, Congress passed the Privacy Protection Act of 1980 which corrected the overreach of government in Lurcher v. Stanford Daily.
Sincerely yours,
Lawrence C. Stewart
Smartphone Security
Zdziarski’s Blog of Things has an article about possible enhancements to iOS security, in the wake of the Apple vs FBI affair.
Another idea is one I’ve mentioned before: Duress Passwords
If you are asked to unlock your phone, you could use a different finger, the duress finger, and the fingerprint sensor could appear to accept it, but erase the phone. If you enter the duress password, the phone could erase itself or, perhaps, just start recording what is going on and uploading it to the cloud.
Another idea are Landmine Passwords. These are passcodes whose purpose is to defeat brute force searches. If you avoid landmines within hamming distance one or two of the correct passcode you would have litle chance of hitting one while trying to enter the correct code, but any searcher would be very likely to hit one before hitting the correct passcode.
The obvious missing feature
I think there are great opportunities for sensible people to make money doing usability analyses of web based systems.
Let me give some examples of well intentioned systems with the obvious feature left out.
Email addresses
I have a Capitol One credit card, and in my user profile, there a place to enter an email address so they can send me stuff. (In another post I will rant about email addresses further) Recently I happened to log in to set up alerts for spending and so forth. The email notifications were disabled because, they said, the email address I had entered had been refused. Yet the address was actually correct.
This is not unknown. We had a crash a while back of our cloud email server, and we didn’t notice for hours, so it is possible mail was bounced.
There was no way to tell the Capitol One system “test it now please”. Instead, I had to change the address to a different one. This made them happy even without a test. I suppose I could then change it back, but how much time do I have to spend working around a bad design?
Phone numbers
Many sites require phone numbers. They have no uniform way of entry. Some have free form fields, but limited to exactly 10 characters. Some forbid hyphens. Some require hyphens. Some have exactly three fields, for area code, exchange, and number. Is it really that hard to parse a variety of formats? Do they really think making me keypunch my number is helping their image?
Notifications
I have my bank account and credit cards set up to send my text notifications when there is activity. One bank only allows notifications for amounts above $100. Why does that even make sense? They can handle small deposits, but they can’t handle sending a text for a $10 charge? At least the text on the page explains the limit.
A credit card company has the same feature, but allows texts for any transaction amount, except $0! If I want notificications on all transactions, what limit value should I use? I telephoned, and the agent suggested $0.01.
I’m getting to be a curmudgeon when things like this offend me.
Notifications – unclear on the concept
Tthis is a post about organizations trying communicating with their customers but getting it wrong.
I have signed up for various notifications, typically by text or email. Tragically, sometimes organizations manage to use these in a way that makes me think they are idiots.
- I just received a text from my local library that a book I’ve had on hold forever has come in. The problem is that I picked it up last night.
- I got an email from my Honda dealer that my minivan is due for service – two days after the service was done, by them.
- I get both emails and texts from Target that my store credit card payment due date is coming up — even though my balance is zero.
To me these seem like violations of a simple and obvious design principle: don’t send a notification that is moot. All it does it point out to your customer that your systems are broken. And that means that your organization is clueless and really should not be trusted with my business.
Delay is also important. I have my Bank of America profile set so that I get texts notifying me of ATM withdrawls. I should get them when I do a withdrawl, but never at other times. Often, these arrive within minutes, but sometimes, they take 6 hours or so to arrive. The immediate feedback ratchets up my confidence that I would find out immediately if fraudulent activity were to occur. The delayed feedback? They are having the opposite effect. I obviously cannot trust BofA systems to notify me of activity in a timely way. Should I trust them for anything else?