diff --git a/README.md b/README.md index e1977aaece191eea87c977c51a4de29bb67fd2d3..d76758e69666401577dbc880cbc5379239ff73ea 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,235 @@ -# handbook +# Freeriders' Handbook (TTC Edition) -Freeriders' Handbook (TTC Edition) +`Dedicated to all freeriders, particularly [TTC fare inspector lookout], [Planka.nu] and [Flea Market Socialist]` -## Getting started +--- -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +## WHAT IS METROLINX -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +`Network of transit checkpoints for tapping targeted surveillance metro card.` -## Add your files +Or: *Metrolinx is a Crown agency of the Government of Ontario that manages and integrates road and public transport in the Greater Toronto and Hamilton Area (GTHA), which comprises much of Ontario's Golden Horseshoe region.* -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +## WHAT IS PRESTO -``` -cd existing_repo -git remote add origin https://0xacab.org/freerider/handbook.git -git branch -M no-masters -git push -uf origin no-masters -``` +`Exploitable gateways to freeriding.` -## Integrate with your tools +Or: *Presto card is a contactless smart card automated fare collection system used on participating public transit systems in the province of Ontario, Canada, specifically in Greater Toronto, Hamilton, and Ottawa.* -- [ ] [Set up project integrations](https://0xacab.org/freerider/handbook/-/settings/integrations) +## WHAT IS TTC -## Collaborate with your team +`Toronto Transit Commission` -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +## PRESTO PRIVACY 101 -## Test and Deploy +### [FREERIDERS' PRIVACY (TTC Edition)](./PRIVACY.md) -Use the built-in continuous integration in GitLab. + - `NEVER LINK YOUR IDENTITY TO THE PRESTO CARD` + - `PAY AND REFILL YOUR PRESTO WITH CASH` + - `WHEN NECESSARY, SWITCH IT ONCE A WHILE` -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) +## EXPLOITS OF TTC FREERIDING -*** +### FILMSY DISABILITY GATES -# Editing this README + -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. +#### `ONE-PERSON GATE-BRUTEFORCE` (10 SEC to 1 MIN) -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. + 1. WALK TOWARD THE GATE + 2. IGNORE THE ERROR SOUND + 3. PUT YOUR DOMINANT FOOT INSIDE THE DISABILITY GATE + 4. LEAN YOUR BODY TOWARD THE DOMINANT FOOT AND PUSH THROUGH + 5. SOME PAIN FOR FIRST-TIMER, KEEP PUSHING WHILE USE YOUR HAND TO HELP + 6. WHILE ALSO LIFT YOUR REMAINING FOOT UP AND WALK INSIDE THE GATE + 7. KEEP IGNORING THE ERROR AND KEEP WALKING. -## Name -Choose a self-explaining name for your project. +#### `MULTI-PEOPLE GATE-BRUTEFORCE` (MUTUAL AID) -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. + 1. WALK TOWARD THE GATE + 2. IGNORE THE ERROR SOUND + 3. PUT YOUR DOMINANT FOOT INSIDE THE DISABILITY GATE + 4. LEAN YOUR BODY TOWARD THE DOMINANT FOOT AND PUSH THROUGH + 5. SOME PAIN FOR FIRST-TIMER, KEEP PUSHING WHILE USE YOUR HAND TO HELP + 6. WHILE ALSO LIFT YOUR REMAINING FOOT UP AND WALK INSIDE THE GATE + 7. KEEP IGNORING THE ERROR + 8. ONCE INSIDE FIRST-PERSON STANDS AT THE GATE LASER SENSOR (INSIDE BLACK SQUARES) + 9. ONCE INSIDE LASER SENSOR BLOCKED THE GATE WILL KEEP OPENING WHILE ERROR BLARING + 10. KEEP IT OPEN UNTIL EVERYONE INSIDE. -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. +#### `SCREW YOUR GATE SENSOR` (DIRECT ACTION) -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. + 1. WALK TOWARD THE GATE WITH YOUR `[DUCT TAPE + WORK GLOVES + MASK]` PPE + 2. IGNORE THE ERROR SOUND + 3. PUT YOUR DOMINANT FOOT INSIDE THE DISABILITY GATE + 4. LEAN YOUR BODY TOWARD THE DOMINANT FOOT AND PUSH THROUGH + 5. SOME PAIN FOR FIRST-TIMER, KEEP PUSHING WHILE USE YOUR HAND TO HELP + 6. WHILE ALSO LIFT YOUR REMAINING FOOT UP AND WALK INSIDE THE GATE + 7. KEEP IGNORING THE ERROR + 8. ONCE INSIDE FIRST-PERSON STANDS AT THE GATE LASER SENSOR (INSIDE BLACK SQUARES) + 9. ONCE INSIDE LASER SENSOR BLOCKED THE GATE WILL KEEP OPENING WHILE ERROR BLARING + 10. KEEP IT OPEN UNTIL EVERYONE INSIDE + 11. RIP A SQUARE OF DUCT TAPE + 12. SLAP IT ON THE INSIDE SQUARE SENSOR TO COVER ALL OF IT + 13. PERMANENT STICKING WITH Adhesive + 14. YOU ONLY NEED TO COVER ONE INSIDE SQUARE OF SENSOR + 15. WHAT IF YOU COVER ALL SENSORS IN ALMOST EVERY STATION? + 16. ??? + 17. SOLIDARITY! -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. +--- -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. +##### BEST REAR ENTRANCE: `LAWRENCE STATION [NORTH ENRANCE]` -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. + - ✔️ Rare Fare Pork + - ✔️ Low Security + - ✔️ NIMBYs Don't Climb Staircases -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. + -## Contributing -State if you are open to contributions and what your requirements are for accepting them. + -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. +##### CHALLENGING REAR ENTRANCE: `[SPADINA STATION]` -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. + - ☠️ FARE PORK HEADQUARTER + - ☠️ MEDIUM SECURITY + - ✔️ TO STREETCARS - ACT CASUAL 🤫️ -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. + -## License -For open source projects, say how it is licensed. +##### MULTI-REAR ENTRANCES `[SHEPPARD-YONGE STATION]` -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. + - ✔️ OPEN-GATE BUS STATION + - ✔️ NORTH REAR GATE (BEHIND MCD) + - ✔️ SOUTH REAR GATE (BEHIND PRESO TEA) + - ✔️ HULLMARK CENTRE + - 🤫️ FARE PORK FREQUENTS + - ☠️ MEDIUM SECURITY + + + +### TAILGATING + +#### How to tailgate the Presto Subway Gates: + + 1. Wait for a person to tap their Presto card + 2. As soon as the gates open walk behind that person + 3. Keep following them until you get inside + 4. As long as the sensor blocked or gate forced open + 5. Tailgating works with multi-people. + + + +#### How to tailgate the Buses: + + 1. Wait for someone to get off the bus rear door + 2. As soon as the person leave hold the rear door to keep it open + 3. Let yourself into the bus and the forced rear door will close on its own + 4. Tip works better and covert in rush hours because driver would be too busy to mind. + +### OTHER TECHNIQUES + +#### CHILD PASS + +[Presto Child Pass](https://www.prestocard.ca/en/about/using-presto#faretype) is unlimited traveling time because of the transit loophole that allow children under ages of 12 to ride for free and they can be obtained at Shopper Drug Mart. + +#### Doggo's Sensor Blocking + + 1. Train doggo friend to get in and block the inside square sensor + 2. As long as doggo stay block the sensor you can get inside + 3. Pet the doggo and give your friend some treat. + + + +#### Using The Dangling Bag + + 1. Dangle your day bag on the other side of the gate to block out the square sensor + 2. Walk in when gates open + 3. ??? + 4. Profit! + + + +#### USING FOOT + + 1. Put a foot to the other side of the gates until parallel with the square sensor + 2. Once square sensor blocked out the gates will open + 3. This technique worked when they first rolled out the Presto gates + 4. Still works in some gates but longer sensor timeout has been setup to prevent this + 5. https://player.vimeo.com/video/271581411?h=cff03c7e7 + +## EVADING FARE INSPECTORS + + + +**TTC fare inspectors usually stick to main stations but there are a few routes they frequents:** + + - Fare cops start shift at `1138 Bathurst` and from there they head to others. + - Spadina Station is their HQ where they change shift & prey on people at streetcar platform. The `510` and `511` routes are frequently patrolled by Fare Inspection. + - Bathurst Station is where they prey on people at streetcar platform, usually on weekends and rush hour but also often take the `7 Bathurst` going Northbound to `St. Clair / Bathurst` to patrol the St. Clair streetcar lines. Sometime they will also get off at `Dupont`. + - Sheppard-Yonge Station at the main entrance ticket booths and rear ticket gates + - All terminal stations particularly Downtown Core. + - `Union` and `Ossington` are frequent by fare cops. + +**Communications of TTC Special Constable / Fare Inspector:** + +Before [their transition to digital Tetra](https://www.radioreference.com/db/sid/9380) after 2019, [fare cops used analog radio service that were listenable on Broadcastify](https://web.archive.org/web/20190617050518/https://www.broadcastify.com/listen/feed/8878). At the moment, the only live feed still available is the [Toronto Transit Control](https://www.broadcastify.com/webPlayer/31629) that included management, maintenance and security, but most of their Tetra comms is independent from control talkgroups. + +### STRATEGIES WHEN ENCOUNTERING FARE COPS + +#### EXITING STREETCARS + +When a streetcar arrived at a station platform fare cops (in pair of two or three) will block the first exit of the streetcar nearest to the station platform, if they patrol in three the third cop will block the middle exit. **That leaves the furthest exits free from their reach.** Act casual but walk quickly and blend with the crowd. Run when you need to. + +#### RIDING STREETCARS + +On rare occasions they will check for ticket on the transit just to fuck with people. When this happens, exit the vehicle at the nearest stop, with the closest exit doors you can find. TTC streetcar doors don't automatically open unless button pressed, or when it arrives at a stop, you will have to long press the door button beforehand to make it open as soon as the streetcar arrived at a stop. Run when you need to. + +#### TRANSFER AS TEMPORARY PASS + +:format(webp)/https://www.thestar.com/content/dam/thestar/news/gta/2019/01/03/on-new-years-eve-this-man-visited-all-75-ttc-subway-stations-in-less-than-10-hours-he-says-museum-is-his-favourite/_1_sheppard_west.jpg) + +Often people leave [paper transfers](https://www.ttc.ca/fares-and-passes/fare-information/transfers) on the ground or chair when they finished using them. These paper transfers have half/one-hour validity from the time of its purchase. Fare cops sometime will waive you pass when they don't check the validity of the transfers except on rush hour. [A list of transfer locations.](https://www.ttc.ca/Fares-and-passes/Fare-information/Transfers/Walking-Transfer-Locations) + +## HACKING PRESTO + +### RELAY ATTACK (NFC) + +#### WITH PHONE + + + +What you need: + + - `NFC TOOLS` https://play.google.com/store/apps/details?id=com.wakdev.wdnfc + - `NFC ReTag` https://play.google.com/store/apps/details?id=com.widgapp.NFC_ReTAG_FREE + - `NFC ReTag Expert Plugin` https://play.google.com/store/apps/details?id=com.widgapp.NFC_ReTag_Expert_Plugin + - DNS Ad Blocker like AdGuard (for ReTag) + +#### WITH TRANSCEIVERS + + + +What you need: + + - Presto uses `MIFARE DESFire EV1 4k` for NFC, which operates at 13.56 MHz. + - `MIFARE DESFire EV1` DOCUMENTATIONS: [1](https://web.archive.org/web/20220708142053/https://faremi.keybase.pub/MIFARE-DESFire-EV1-Product-Flyer-Web.pdf), [2](https://web.archive.org/web/20220708142147/https://faremi.keybase.pub/MF3ICDQ1_MF3ICDHQ1_SDS.pdf), [3](https://web.archive.org/web/20220708142231/https://faremi.keybase.pub/MF3ICDX21_41_81_SDS.pdf) and [4](https://web.archive.org/web/20220215170710/https://www.hidglobal.com/sites/default/files/resource_files/mifare-desfire-ev1-card-ds-en.pdf) + - NFC/SDR transceivers. The recommended budget open-source tool for this is `Flipper Zero`. + - Proxmark3 is pricier option but offers more freedom to exploit Presto freqs. + - Blank magnetic cards or programmable key fobs with equivalent frequencies range + - Or you could build an [Arduino NFC reader](https://www.allaboutcircuits.com/projects/rfid-technology-using-arduino-mega/) + +How this works: + + 1. Find your target's card + 2. Capture the signal with the NFC reader + 3. Clone the signal to programmable card/key fob + 4. Confirm your cloned batch. + +### PRESTO DENIAL-OF-SERVICE + +`THIS 0DAY IS WORK-IN-PROGRESS, FOR EDUCATIONAL PURPOSE ONLY` + +There is a bug in Presto machine that can crash all other machines on the same cluster. If you have a Proxmark3 or Flipper Zero, you can program the Presto card with null or blank input, but with valid send signal. Presto machine use `Microsoft Windows CE 7.0` and is still possible vulnerable to something like CVE-2006-6908 with BoF denial-of-service. Not every Presto machine OS gets patched regularly. + +The test way would by programming the null inputs or exploit payloads into the card signal, tap the card on a bus Presto machine and there is two ways this gonna crash: if the card get green light, this would be silent DoS, it won't show the error until the next person tap their valid card. If it shows error your card either worked or the command was denied.