4 ms·
The way the no fly list was shared, it was absolutely inevitable that this would happen. A much more secure way to handle this: 1. Airlines are each given a no
by hn_throwaway_99 4y ago
The way the no fly list was shared, it was absolutely inevitable that this would happen. A much more secure way to handle this:
1. Airlines are each given a no fly list that only includes tokens, e.g. each person's name hashed with a secret key that is specific to the airline, on a periodic basis.
2. When the airline wants to check if a user is on the list, they hit a government-owned service that returns the user's token (again, the token will be unique for each airline because each airline gets their own secret key).
3. The airline would then check the token against their revoked token list.
The benefit of this is:
1. The full token list by itself is useless
2. Even if the airlines API credentials are stolen, the response from the government-owned service is useless on its own.
3. So a bad guy would need to steal the token list AND the API creds to get any value, and even then it would be easy for the government to detect unusual access patterns to their service.
Remember back in the late 90s when we all used to store passwords in plain text? Yeah, we know how that turned out, and in this case, storing the list not only in plain text but sharing it to tons of different companies willy nilly is a million times worse if you expect it to stay secret.
- mitthrowaway2 4y agoMaybe the government could also make this service available to parents, who can query it to find out if they should pick a different name for their baby? Seriously, using names for a no-fly-list is falsehood 21. https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- Scoundreller 4y agoHappens in Canada too. A 6 year old ended up on the list. Four years later; they were still on it with the government promising a fix the next year… https://www.cbc.ca/news/politics/canada-no-fly-list-kids-meeting-public-safety-minister-1.5403518 https://www.cbc.ca/news/politics/canada-no-fly-list-kids-mee... https://www.cbc.ca/news/canada/toronto/no-fly-list-canada-1.5396974 https://www.cbc.ca/news/canada/toronto/no-fly-list-canada-1....
- dosethree 4y agoSounds similar to how do not call lists are handled
- KyeRussell 4y agoMomentarily ignoring the myriad complexities of name matching, unfortunately you get no points for coming up with potentially technologically superior solutions for these sorts of problems. The people involved in maintaining this system certainly knew that there were better ways to do it. It’s an organisational / people problem. The real skill is making anyone listen to you, and pulling airlines away from a legacy system, and dealing with the inevitable claims that the government owes them $100mil a pop for “having to comply with increased compliance requirements”.
- philsnow 4y ago> dealing with the inevitable claims that the government owes them $100mil a pop for “having to comply with increased compliance requirements”. It would be amusing to announce "hey the incumbent airlines each seem to think this change is going to cost them $100M to implement, so instead we're offering $80M to newcomer airlines who know damn well they can do the integration for $100k". (not that I would want the government to do this, necessarily, I just have a mindset that is contemptuous towards the inefficiencies of ancient/giant companies)
- chii 4y agoso if you need to hit a gov't owned api for a response, then why do all the tokenization at all? Just return a boolean from that service directly to deny. It might even work better if it was off a passport number, rather than a name. The problem is that the online service is needed, and thus ties airline boarding to the service availability. Airlines wanted an offline list, so that even without internet connectivity, they can board.