xyl2k / tsa-travel-sentry-master-keys

3D reproduction of TSA Master keys

3D TSA "Travel Sentry" master keys

Recently, pictures of TSA master baggage keys got leaked by the Washington Post and also PDFs hosted on TravelSentry's Website. This repo is a reproduction attempt

Security researchers have long warned of the dangers of using master-keyed locks

The TSA has issued an official statement making it known that they don't even care that we've done this, as the now-pointless locks affect theft prevention, not airline safety.

[!] Important: These keys have not been widely-tested, though we do have reports that many do work from at least one source. 006 May never work, as we're not sure of the depth of the "dimples," and also consumer-grade 3D printers may not be up to such finely-detailed tasks.

Added the stubby versions of the keys by MS3FGX, which appear to still work fine !

Thanks:

• Special thanks to @darksim905 and @irongeek_adc and some anonymous others who all sent us images and information surrounding these keys. Also, @j0hnnyXm4s for his key size ratios and issue management / advice.

3D TSA "Safe Skies" master key

Safe Skies manufactures TSA-approved locks under their own standard, competing with Travel Sentry, and has even sued Travel Sentry for patent infringement. They have a much smaller market share than Travel Sentry. These locks can be identified by noting the words "Safe Skies" next to the keyway, in a similar location as the Travel Sentry "TSA00N" notations. All available information indicates only one override/master key exists for their entire system. Armed with this knowledge and a large hammer (no, really), @darksim905 and Nite0wl reverse-engineered the master key bitting, and created 3D files suitable for printing. They presented their findings along with @j0hnnyXm4s at the 11th Hackers of Planet Earth conference in New York City, in July of 2016.

PROBLEM REPORTING

If you print a key and it doesn't work:

• First, use a caliper or other highly-accurate device to make sure the key you printed is accurate to the model. Humidity, expansion & ambient room temperature can have serious effects on print size accuracy.

• If it IS accurate, open an issue on the github, specify the problem file, and what problems exist (i.e. "Too wide for the keyway," "Too tall for the keyway," etc.).

• Upload a picture of your lock's keyway.

• If you have the original keys for the lock, provide a measurement of the key from shoulder to tip, total height of the shoulders, and width. (i.e. X, Y & Z axes of the blade). Some keys only have one shoulder.

LICENSE

This project is released under the Creative Commons Attribution-NonCommercial 3.0 Unported License.

You are free to:

• Share — copy and redistribute the material in any medium or format
• Adapt — remix, transform, and build upon the material
• The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

• [!]Attribution — You must give appropriate credit to all contributors to this project, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

• [!]NonCommercial — You may not use the material for commercial purposes. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

Notices:

You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.

No warranties are given.

For the full text of this license, see LICENSE.md.

tsa-travel-sentry-master-keys's Issues

Which unit was used?

Which unit was used to create your stl files?
Are they in inch, mm, cm?

regards

007 is Too Thick

While you can certainly cram it in there with some fiddling at the current 2.0mm, the actual key width for 007 is 1.6mm.

002 Appears to need a groove on the other side

Per this tweet

This is congruent with the way I would expect the lock to be laid out.

Key 3 too thick

I had to sand the key 3 down quite a bit before I could use it in my tsa 003 lock

Collection of working keys

Can someone reup or relink all working keys again in the right dimension? I'm a bit confused by all these files. A link would be very helpful because I want to print the keys with a metacrylate photopolymer gum and don't have a CAD programm right now.

I want to try a better printer and better material, maybe then the keys work on more locks.

Thanks, G.

TSA002 slightly inaccurate? TSA006 too small

I have just recently tested TSA002 on 2 locks. Curiously, it worked once on the first lock - unlocking it easily - but hasn't worked again (the key goes in but doesn't turn in the other direction). It only went halfway into the second lock. Seems like there's a bit of inaccuracy on the model, but I'm not sure if it is really the model or the print that is broken.

TSA006 was also way too small (but mentioned already in #22). I'm currently also printing an updated one from johnnyxmas's repo for a test later.

I can provide pictures and measurements later if necessary, since I'm a bit busy right now.

key no.2

What printer head is recommended?

Because of the fine size of the keys, what size of the printer head is recommended? And which printing material to avoid getting the smaller printer head clogged

Scaling issue?

IDK but these doen't seems to be right for me.

Rimowa tsa006 too small

My wife doesn't know how to operate her luggage and decided to spin the number wheels and set a new code.

I printed out the current stl on my prusa using PLA and also on a DLP resin printer.

I found that the key was too small.

I know my wife is going to pull the same stunt again, so I am committed to drafting a working key.

I believe if I scale the current key, it should have a good chance of opening the lock.

Enclosed are rudimentary pictures of the keyway.

-m

Tried on actual Luggage?

Did anyone of you ever tried to use the keys on actual luggage locks? I made a 007-Key and it works well with a padlock, but it didn't with a suitcase lock. Any ideas?

Print settings

Hello,

What are the best print settings ?

Which type of support ?

Thank you.

Key Dimension are to small

I just print your TSA002 Key, and they are too small, TSA002 is JMA LAS2 or Silca LS13R Key Blank,
Your 14mm lenght is in original about 22mm

http://www.aldridgesecurity.co.uk/p-3699-silca-ls13r-to-suit-las.aspx

Image for README

7

Y

where's the license?

May I suggest you use the CERN open hardware license?
http://www.ohwr.org/documents/294

Please make suggestions for what materials are suitable

I've tried contacting some local printers, and haven't been able to find one nearby who is confident that their printer will:
a) Achieve the desired resolution to print function key teeth
b) Use a material compatible with use as a key. Some materials will be too soft or brittle.

If folks could post printers/materials that have worked so far, that would be greatly appreciated. This info could be merged into the README.

TSA_004_stubby.stl

PrusaSlicer is showing numerous errors in the TSA 004 stuby STL file. It seems like netfab is able to repair it easily.

**

**

Just a heads up

These are posted for sale here: https://cults3d.com/en/tool/cle-universelle-tsa

Not sure if they are identical to what you have on here but thought you would like to know.

Repo layout suggestion

I've been following this repo, wondering if it makes sense to use a Git-Flow style of repo branches to support merging and testing. I'm thinking out loud here, but think some organization is needed. I've done a lot of Github based OSS development, but never on an STL files so I think the problem is slightly different. If anyone has an alternative, please suggest in this issue - and maybe the maintainer will consider.

For those not familiar with Git-Flow, info here: http://nvie.com/posts/a-successful-git-branching-model/

Heres what I'm thinking:

• Master: contains full stable releases of all keys
• Develop: contains unstable releases of all keys
• Release/[key number]: contains stable version of specific keys for testing
• Feature/[key number]: contains unstable development versions of specific keys

Pull requests should happen on Feature/[key number] branches from which these would be alpha versions. Once there is some confidence of stability - merge with develop to make it beta. Then as we think the keys are ready for release candidates, merge into release/[key number]. Once enough feedback has been submitted, the release keys can be merged and tagged on master.

Also STL's should be just STL's - for specific printing guidance for specific printers, I'd say use the Wiki features to document how to print a set.