Friday, 24 March 2017

Tips for travellers about the "Muslim laptop ban"

The "Muslim laptop ban" goes into effect today: The U.S. government has ordered airlines to prevent passengers from bringing laptop or tablet computers or other electronic devices "larger than a cellphone" (whatever that means) on their person or in carry-on baggage on direct flights between 10 airports in countries with predominantly Muslim populations in the "Middle East" (West Asia) and North Africa and the USA.

These items will still be allowed on these flights in checked luggage, where either lithium batteries or explosives pose a greater danger because in-flight fires are harder to detect or put out in the cargo hold than in the passenger compartment.

According to a report by Kaveh Waddell in The Atlantic (in which I'm also quoted), "The ban was communicated to the relevant airlines and airports at 3 a.m. Eastern on Tuesday, in the form of an emergency amendment to a security directive. From that point, the airlines and airports will have 96 hours to comply."

Many others including airline pilot Patrick Smith ("Ask The Pilot") and experts interviewed by the Guardian (here and here) and the Washington Post have made the point that the Muslim laptop ban uses "security" as a pretext for trade sanctions (no US-based airlines serve any of the airports subjected to the laptop ban, which include the hub airports of airlines with which US-based airlines have been fighting a trade war) and Islamophobic harassment (the affected flights are those on which the largest numbers of citizens of countries that President Trump tried to ban from the US, but which the courts have at least temporarily enjoined him from excluding from the US, are likely to arrive).

Aside from making the US government look more bigoted and stupid, it remains to be seen whether the Muslim laptop ban will affect travellers' choices of airlines or force carriers like Turkish Airlines to lower their fares even further to offset the disadvantage (especially for the most profitable business travellers) of not being able to work (or play games) on laptops in flight.

But what does the Muslim laptop ban actually mean for travellers?

What are the rules? There are no "rules", in any normal sense of that word. Airlines have been given orders by the DHS, in the form of "Security Directives". But those orders are secret. Airlines can, and often do, make things up out of ignorance or to serve their own profits, and blame them on the government. In this case, the orders are probably real, and certainly disliked by the airlines to which they apply (although welcomed by their US-based competitors). But, "The government made us do it," is a great excuse for anything airlines want to do -- especially when it's impossible for passengers to tell if it's true.

Is this legal? Nobody knows. It's almost impossible for travellers to challenge the orders given by the government to the airlines. Airlines have standing to challenge these orders in court, but none of them have done so. It's one more example of the craven complicity of airlines in government harassment and infringement of the rights of travellers -- including airline complicity in, and failure to challenge, President Trump's Muslim ban.

But how can I tell what I will be allowed to carry on? You can't. Even before the Muslim laptop ban, and regardless of what the government requires, airlines reserve the right to make you check your bags, including whatever you planned to carry on. Their tariff and conditions of carriage, as of the time your buy your ticket, give you a contractual right to have a certain amount of luggage transported to your ticketed destination. But they don't guarantee that any of your luggage will be transported in the passenger cabin, or even on the same plane, just as they don't guarantee that you will be transported on the original schedule or routing. As long as you and your luggage are delivered to your destination without being charged extra, the airline has fulfilled its contractual obligations even if it requires you to check your carry-on sized bag, and sends it on a different flight or different set of connecting flights than you are on.

Here's how I explained it in "The Practical Nomad: How to Travel Around the World":

What Are You Allowed to Carry On? Don't rely on this or any book or Web site to tell you which specific items you will or won't be allowed to carry on. There is no way to know for sure until you try. The "rules" can change at any time, and much is left to the discretion of the people searching you and your bags. In the USA, the TSA refused to show me the rules when I asked for them under the Freedom of Information Act, and told me that it would "create public confusion" for people to rely on TSA press releases or their Web site. If you aren't sure about something, try to ask the checkpoint staff about it before you check in, so that you can move it to your checked baggage if they say you can't carry it on.

So what am I supposed to do? Be prepared. Don't count on being able to carry any of luggage on the plane with you, or having any of your luggage or any working electronics right away when you get off the plane at your destination. Segregate the smallest amount of the most essential items (passport, money, credit and ATM cards, prescription and any other essential medications, printouts of your itinerary and other documents you would need right away on arrival if your laptop or tablet and the rest of your luggage goes missing for a few days and your cellphone dies) in a small bag or pouch that you can quickly pull out of your "carry-on" bag if you unexpectedly have to check it. Don't rely on data "in the cloud" that can be deleted by anyone who gets the password to your account. Consider carrying a backup of your data (including your contacts and any other key data from your phone as well as from your laptop or tablet) on your person, separate from your phone, on an encrypted memory card. Consider setting up your laptop to run off an encrypted memory card, so you can carry all your data with you even if you have to check your laptop. Do the same with your phone: Set it up to store as much of your data as possible on a removable memory card, so you can carry a separate backup and won't lose you data if your phone dies or is lost or stolen.

Link | Posted by Edward, 24 March 2017, 12:27 (12:27 PM) | Comments (1) | TrackBack (0)

Tuesday, 21 March 2017

Testimony in Alaska on the REAL-ID Act

I'm testifying today (by teleconference) at two hearings in the Alaska State Legislature on state bills related to the Federal REAL-ID Act.

In 2008, the Alaska State Legislature enacted a state law prohibiting any state spending to implement the REAL-ID Act.

Now, in response to Federal threats to interfere with Alaskan residents' freedom of movement if the state government doesn't upload information about all state license and ID-card holders to a national ID database, the state legislature is considering bills to authorize that spending and implementation.

It makes no sense for Alaska to call for repeal of a disliked Federal law of dubious Constitutionality, and simultaneously to authorize state spending to comply with that law, without first getting the courts to rule on whether the (unfunded) mandate for state action or the threatened sanctions against state residents are Constitutional.

Details and links to the proposed legislation and my testimony at PapersPlease.org: Alaska and the REAL-ID Act

Link | Posted by Edward, 21 March 2017, 13:06 ( 1:06 PM) | Comments (1) | TrackBack (0)

Tuesday, 14 March 2017

Palantir, Peter Thiel, Big Data, and the DHS

Edward Hasbrouck in a pussy hat outside Peter Thiel's house in San Francisco

[On the sidewalk in front of Palantir founder and Trump supporter Peter Thiel's house at 2920 Broadway in San Francisco.]

On Saturday, I joined an ad hoc group of picketers outside the Pacific Heights mansion of Palantir Technologies founder and Trump supporter Peter Thiel (photo gallery from the SF Chronicle, video clip from KGO-TV; more photos from the East Bay Express).

San Francisco and Silicon Valley are among the centers of opposition to President Trump and his fascism, especially as it relates to restrictions on movement, border controls, immigration, and asylum.

Bay Area technology companies and their better-paid classes of employees like to think of themselves as building a better world that reflects the distinctive values that have attracted dreamers and futurists to this region -- as it attracted me, 35 years ago -- from across the country and around the world. But some of these companies are key developers and providers of "big data" tools for the opposite sort of "Brave New World".

As Anna Weiner reported in the New Yorker ("Why Protesters Gathered Outside Peter Thiel's Mansion This Weekend"):

David Campos, a former member of the San Francisco board of supervisors, who emigrated from Guatemala, in 1985, stood on the brick stoop and raised a megaphone. "The reason we're here is to call upon the people who are complicit in what Trump is trying to do," he said. Clark echoed the sentiment. "If your company is complicit, it is time to fight that," she said. Trauss, when it was her turn, addressed Thiel, wherever he was. "What happened to being a libertarian?" she asked. "What happened to freedom of movement for labor?"

Edward Hasbrouck, a consultant with the Identity Project, a civil-liberties group, took the stand, wearing a furry pink tiger-striped pussyhat. "The banality of evil today is the person sitting in a cubicle in San Francisco, or in Silicon Valley, building the tools of digital fascism that are being used by those in Washington," he said. "We've been hearing back that there are a fair number of people at Palantir who are working really hard at convincing themselves that they're not playing a role -- they're not the ones out on the street putting the cuffs on people. They're not really responsible, even though they're the ones who are building the technology that makes that possible."

It's easy to rationalize the creation of technological tools by saying that they can used for good as well as evil. But you can't separate the work of tool-making from the ways those tools are being used. Palantir workers' claims to "neutrality" resemble the claims made in defense of IBM and Polaroid and when they were making and selling "general purpose" computers, cameras, and ID-badge making machines to the South African government in the 1970s. None of this technology and equipment was inherently evil. But in South Africa, it was being used to administer the apartheid system of passbooks and permissions for travel, work, and residence.

The same goes for "big data" today. To understand what's wrong with the work being done by Palantir for the U.S. Department of Homeland Security, it's necessary to look not just at what tools Palantir is building but at how and by whom they will be used; not just at the data tools but at the datasets to which they are applied, the algorithms they use, and the outcomes they are used to determine.

Continue reading "Palantir, Peter Thiel, Big Data, and the DHS"
Link | Posted by Edward, 14 March 2017, 22:57 (10:57 PM) | Comments (3) | TrackBack (0)

Monday, 27 February 2017

Friday, 27 January 2017

President Trump, Populist Politics, and the Prospects for Privacy

panel on stage at CPDP 2017

I was on a panel on Wednesday at the Computers, Privacy, and Data Protection conference in Brussels on the topic of "Populist Politics and the Prospects for Privacy".

Through no fault of the organizers, who were extremely accommodating of my last-minute proposal for this panel after the US elections, we had less time than we had hoped for. There's video of the session, but I was rushed and probably not always clear.

Edward Hasbrouck wearing a pink pussy hat

[My pussy hat -- the symbol of the Women's Marches last weekend after Trump's inauguration -- was popular at CPDP. Photo by kind permission of Wendy M. Grossman. Thanks to Suzanne and another Wendy for knitting and giving me the hat!]

By popular request, below the jump is a summary of the main points I tried to make.

(For those interested in more detail, I've posted my notes on issues I would have liked to raise, if we had more time. I've also posted a separate article at PapersPlease.org on President Trump's executive order repudiating the EU-US agreement on transfers of PNR data from the EU to the US government.)

Continue reading "President Trump, Populist Politics, and the Prospects for Privacy"
Link | Posted by Edward, 27 January 2017, 06:10 ( 6:10 AM) | Comments (4) | TrackBack (0)

Wednesday, 18 January 2017

Unresponsive "comments" from Amadeus

Exactly three weeks after a public demonstration of the insecurity of public Web gateways to computerized reservation systems (CRSs) -- a threat to travellers that I've been writing, speaking and telling the CRS operators about for more than 15 years -- one of those companies has responded to my request for comment, but without answering any of my questions.

Here, in its entirety, is the statement I received late Tuesday from Amadeus (which hosts PNR data for airlines and travel agencies and operates the CheckMyTrip.com for viewing PNR data), followed by my comments:

Continue reading "Unresponsive "comments" from Amadeus"
Link | Posted by Edward, 18 January 2017, 00:17 (12:17 AM) | Comments (0) | TrackBack (0)

Saturday, 14 January 2017

The REAL-ID Act and the TSA proposal to require ID to fly

Much of my work for the last decade as a consultant to the Identity Project (PapersPlease.org) on travel-related civil-liberties and human rights issues has focused on requirements to obtain government permission and/or show government-issued ID credentials in order to travel by common carrier.

No law in the USA requires you to show ID to fly, as I have explained to state legislators and Washington think tanks.

The TSA tells travellers they have to show government-issued ID to fly, harasses those who decline to do so, and sometimes has them arrested by local police on trumped-up (will that word now have new meaning?) charges.

But people with no ID at all fly every day. "We have a procedure for that," the TSA says whenever its demands for ID are challenged in court.

Now the TSA has proposed -- in a backhanded way calculated to evade public or Congressional debate or judicial oversight -- to impose a new official requirement for all airline passengers either to show government-issued ID or to certify that they live in a state that the DHS deems sufficiently compliant with the REAL-ID Act 2005. This ID requirement would be an additional prerequisite before the TSA will give them "permission" to pass though its checkpoints or board airline flights.

For more on what's wrong with this proposal, see the comments filed this week with the TSA by the Identity Project and this post from the Identity Project blog.

Link | Posted by Edward, 14 January 2017, 16:58 ( 4:58 PM) | Comments (2) | TrackBack (0)

Thursday, 12 January 2017

"What can I do to protect my PNR data?"

Since the recent public demonstration of some of the security and privacy vulnerabilities of airline reservations systems that I've been writing and speaking about for more than 15 years, people have been asking me, "What can I do to protect myself against stalking, harassment, surveillance, and fraud when I travel?"

Here are some answers from an interview I gave last week to Lucia Blasco of the BBC World Service:

Continue reading ""What can I do to protect my PNR data?""
Link | Posted by Edward, 12 January 2017, 21:02 ( 9:02 PM) | Comments (2) | TrackBack (0)

Friday, 30 December 2016

CRS/GDS companies and travellers' privacy

error message from CheckMyTrip.com Web server

[In the middle of the presentation by SRLabs at 33C3 on Tuesday, Nemanja Nikodijevic discovered that Amadeus had taken its "CheckMyTrip.com" PNR-viewing Web site offline to prevent the vulnerabilities of the site from being demonstrated in real time. Screen capture from CC3C video by permission of SRLabs. Click images for larger versions.]

This past Tuesday at the 33C3 conference in Hamburg, Germany, Karsten Nohl and Nemanja Nikodijevic of SRLabs publicly demonstrated that airline reservations systems still have the same fundamental insecurity, in the same ways that I have been writing and speaking about for more than 15 years.

Lest there be any doubt, while the the team from SRLabs was inspired to investigate this subject in part by an interview with me on a German IT news site, I had no contact with them and was entirely unaware of their work until they contacted me last week. They worked entirely independently of me, and had no access to any information from me except my published writing and public speeches. When they contacted me last week to let me know that they would be giving a presentation on this topic at 33Cc, their research was already complete.

I thought that expert security researchers might have found more vulnerabilities than I had found. Perhaps they did, but haven't yet discussed them publicly. But all of the attacks they demonstrated in their public presentation at 33C3 exploited the lack of real passwords on public Web gateways to Passenger Name Records (PNRs) operated by computerized reservation systems (CRSs/GDSs) for itinerary viewing, and by airlines for online booking, ticketing, check-in, changes, and cancellations.

These specific vulnerabilities have been publicly reported and discussed in print for at least 15 years, starting around the time Amadeus began its beta test of CheckMyTrip.com.

In light of some of the statements attributed to Amadeus -- the target of most of the sample exploits demonstrated by SRLabs -- in other news stories this week, it's important for the public and for government officials with authority over privacy and data protection to understand that this was not a demonstration of new vulnerabilities or anything that wasn't already well-known to Sabre, Amadeus, and Travelport (the current owner of both Galileo/Apollo and Worldspan).

Amadeus' reported responses have focused on the brute-force attack on PNR record locators, but the real problem, which has long been known, is the use of the record locator as though it were a password and without telling travellers that they need to keep it secret like a password that can't be changed if compromised. In many real-world targetted attack scenarios, the attacker will have other ways than trial and error to obtain a record locator. And real-world attacks are likely to be targetted: There are easier ways for hackers to obtain credit card numbers or money. The motivation for hacking a CRS/GDS or obtaining PNR data is to find out where someone will be, and when, so that the cyber-attacker can stalk their victim, surveil her, harass or attack her physically, rob her home while she is away, kidnap her and/or her children, or kill her.

To set the record straight, below is more detail than I would normally go into about the chronology of my reporting on this subject, followed by my recommendations for action and the questions I have asked Amadeus.

Continue reading "CRS/GDS companies and travellers' privacy"
Link | Posted by Edward, 30 December 2016, 21:13 ( 9:13 PM) | Comments (4) | TrackBack (0)

Tuesday, 27 December 2016

"Travel data: fraud with booking codes is too easy"

diagram of potential PNR attack vectors

[Some of the privacy and security threats to PNR data and the CRS network, from my testimony in 2013 as an invited expert witness before the Advisory Committee on Aviation Consumer Protection of the U.S. Department of Transportation. Click image for larger version.]

Video, slides, and blog post of presentation by SRLabs at 33C3
(27 December 2016, Hamburg, Germany)
Who's watching you while you travel?
(details of this vulnerability published on my Web site, 18 April 2002)
Flight booking systems lack basic privacy safeguards, researchers say
(by Eric Auchard, Reuters, 27 December 2016)
Reisedaten: Betrug mit Buchungscodes ist zu einfach
(by Patrick Beuth, Zeit, 26 December 2016)
Unsicherheit bei Flugbuchungen: "Greift mehr Legacy-Systeme an"
(by Hauke Gierow, Golem.de, 28 December 2016)
Une étude alerte sur les failles des réservations de vol
(by Alexis Orsini, Numerama.com, 28 December 2016)
33C3: Gravierende Sicherheitslücken bei Reisebuchungssystemen
(by Stefan Krempl, Heise Online, 28 December 2016)
Amadeus-Sicherheitsproblem: Einladung für Cyber-Vandalen
(by Frank Patalong, Der Spiegel, 27 December 2016)

Today at the 33rd Chaos Communication Congress (33C3) in Hamburg, Germany, white-hat hackers from Security Research Labs inspired by news reports in Germany about my work will publicly demonstrate their ability to access and alter other people's airline reservations (PNRs) by exploiting vulnerabilities including ones that I wrote about and called to the attention of all of the four major Computerized Reservation Systems in 2002, but that the CRSs have made a deliberate choice not to close because (a) government authorities have not enforced existing data protection laws (in other countries than the USA, which has no such laws) against CRSs, airlines, or travel agencies, and (b) these travel companies put their profits ahead of passengers' privacy and security.

There's been some advance coverage in German print (mentioning my work) and television news media. (Zeit, Handelsblatt, Der Spiegel.) But the CRS exploits discussed in these news stories are not the most serious of those that I expect the folks from SRLabs (well-known for their previous public exploits) to demonstrate at 33C3. Watch the livestream here at 21:45 CET in Hamburg, 12:45 p.m. PST in San Francisco. Recorded video will be posted later, but I don't know how soon. I'll add a link once it is available.

As I wrote in my book, The Practical Nomad Guide to the Online Travel Marketplace, which was published in early 2001 before 9/11, "Privacy is the Achilles heel of Internet travel planning." In that book (page 121), I also wrote about the vulnerability of the public Web gateways operated by CRS companies -- the vulnerability exploited in today's demonstration at 33C3, of which the first was Sabre's VirtuallyThere.com:

If you make reservations through Travelocity.com or any other Sabre travel agency, you can view your itinerary at Sabre's "Virtually There" Web site (www.virtuallythere.com) by entering your last name and the six-character "record locator"" for your reservations. This is good if you've misplaced your printed itinerary, but at present is dangerously insecure. Anyone who sees your name and record locator on an itinerary (through a window envelope, for example, or over your shoulder in an airport check-in line) can find out your home address, the exact dates you''ll be away, where you are staying, etc. Properly secured, it could be a great feature, and hopefully Travelocity.com will have secured it before you read this. If they haven't, don''t make any reservations in Sabre until they do, unless you want every detail of your trip to be public.

At the time that this was written and this book went to press in 2000, I was already in active discussions with Sabre about this issue. Eventually Sabre made some partial improvements, which I reported on in 2002, but they were insufficient and in any event proved to be temporary.

After each of the other CRS companies launched sites imitating VirtuallyThere.com, and with the same vulnerabilities, and none of them responded to my repeated requests for comment about those vulnerabilities, I went into more detail in an online supplement to the book in 2002:

What else has changed in 2001-2002, since "The Practical Nomad Guide to the Online Travel Marketplace"... went to press? Here are a few of the trends, changes, and news items I think are most significant for consumers and travelers:...

The security and privacy vulnerabilities of the three main Internet itinerary viewing services, VirtuallyThere.com (Sabre), ViewTrip.com (Galileo/Apollo), and CheckMyTrip.com (Amadeus) have not been corrected as of March 2002. I mentioned these in "The Practical Nomad Guide to the Online Travel Marketplace", but I didn't highlight them in the book because I assumed that they would soon be fixed. More than a year later, that hasn't happened.

These services currently do not use secure or secret passwords, and pose an extreme risk of severe privacy invasion. Even if you don't use these services yourself, they make complete details of your itinerary available to anyone who knows your last name and reservation number ("record locator"). Reservation numbers are printed conspicuously on itineraries, and are often visible through window envelopes, or to "shoulder surfers" in check-in lines or any other public place where you might have your itinerary in view. It's fairly obvious that no one who designed these services gave any real thought to their privacy implications (which is typical of Internet services).

Most online and offline travel agencies use either Sabre, Galileo/Apollo, or Amadeus, so you may not be able to avoid having your itinerary revealed in this way....

I urge consumers to complain to Sabre, Galileo, and Amadeus. Demand that they change their security procedures before a stalker, abuser, or kidnapper takes advantage of one of these services.

In comments submitted to a privacy roundtable convened by the U.S. Federal Trade Commission in 2009 and co-signed by organizations including the Consumer Travel Alliance (Travelers United) and the Consumer Federation of America, I wrote:

Travel records are highly vulnerable to unauthorized access....Because no logs are normally kept of access to PNR's or customer profiles stored in a CRS/GDS,... unauthorized access... could go undetected indefinitely.

CRS's/GDS's have deployed insecure public Web gateways that allow anyone who knows your name and "record locator" to view the complete itinerary from your PNR. But a "record locator" is not a password and does not provide adequate access control: record locators are printed and displayed everywhere from itineraries and tickets to boarding pass stubs (frequently discarded after a flight) and the tags on checked luggage, which are exposed to public scrutiny, unattended, while on the carousel at the destination waiting to be claimed....

The absence of access logs in the major CRS's/GDS's makes it impossible for travel companies that use these systems to comply with the fundamental principles of fair information
practices - or even, in many cases, their own claimed privacy policies. Since no access logs are kept or included in PNR's, travel companies themselves don't know who has accessed data they entered. As they have admitted in response to some of our requests, they don't know and thus can't tell consumers who has accessed data about them, which data, or from where in the world.

I'm available today from San Francisco for interviews by e-mail, phone, or video Skype before or after the 33C3 session. I'll also be in Europe for two weeks in late January and early February, possibly with some time in Germany. I'd be happy to participate in public discussions of this issue, or to meet privately with anyone from a CRS or data protection authority who wants to talk about what can and should be done. If you are interested, please get in touch.

In the meantime, here are answers to some of the most frequently-asked questions I've been getting in the last few days:

Continue reading ""Travel data: fraud with booking codes is too easy""
Link | Posted by Edward, 27 December 2016, 02:54 ( 2:54 AM) | Comments (10) | TrackBack (0)