oebb-ticket
i reverse engineered oebb payment so i can buy oebb tickets on a nokia n9 with claude "ai". i don't know if it works for other banks than n26, but hopefully it does, claude states so. be advised that tickets purchased this way cannot be returned as a pdf is generated automatically. you can generate a fingerprint in your browser on your pc that you can store in the app to send it to n26 with an html. when captcha is triggered it takes about 1min to solve it on this phone with this implementation, i don't know if it can be done faster. you cannot edit payment and you cannot edit travellers, but it lets you select already created travellers and add adults or children without discount, i couldn't implement that. as always you need python3.11 from wunderw repo. you can find the source and an html to generate a fingerprint for n26 if you go to talk.maemo.org. the password is harmattan.
Category:
Keywords:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 oebb-tickets_3_11_0_armel.deb | 126.24 KB | 19/12/2025 - 19:44 |
| oebb-tickets_3_13_32_armel.deb | 141.6 KB | 29/12/2025 - 17:24 |
| oebb-tickets_3_13_35_armel.deb | 124.8 KB | 03/02/2026 - 00:03 |
| oebb-tickets_3_13_36_armel.deb | 97.99 KB | 03/02/2026 - 00:25 |
| oebb-tickets_3_13_37_armel.deb | 103.03 KB | 03/02/2026 - 10:09 |
| oebb-tickets_3_14_0_armel.deb | 103.65 KB | 05/04/2026 - 22:51 |
| oebb-tickets_3_14_3_armel.deb | 106.8 KB | 25/05/2026 - 03:54 |
| oebb-tickets_3_14_7_armel.deb | 111.91 KB | 25/05/2026 - 12:44 |
| oebb-tickets_3_14_10_armel.deb | 115.52 KB | 10/06/2026 - 18:41 |
| oebb-tickets_3.15.0_armel.deb | 127.38 KB | 07/07/2026 - 16:38 |
Changelog:
oebb-tickets (3.15.0) unstable; urgency=high
* v2 Full-Login ueber Mind2-Xvfb-Browser
- OeBB Login-Captcha ist jetzt FriendlyCaptcha v2 (activate/quote/
redeem, Solver in cross-origin iframe). Alter lokaler Solve-Weg
gibt HTTP 401 - das redeem_token ist an die Keycloak-Session des
loesenden Browsers gebunden, laesst sich nicht in die App-Session
uebertragen.
- Neuer Weg: echter Firefox unter Xvfb (headless=False) auf dem Mind2
faehrt den KOMPLETTEN Login. email+password gehen an den Service
(POST /solve), fertige OAuth-Tokens kommen zurueck.
- login_via_service() in auth_helper.py; wird am Anfang von do_login
versucht. Bei Service-Ausfall Fallback auf den alten lokalen Weg.
- Erst-Login ~90s (v2-PoW rechnet im Browser-WASM auf RK3588).
do_refresh danach ohne Captcha, haelt Session am Leben.
- SOLVER_TIMEOUT default auf 150s erhoeht (v2-PoW braucht ~85s).
- Serverseitig: frc-solver.service auf Mind2 neu (Xvfb + Playwright-
Firefox), Restart=always gegen TERM-Kills.
Recent comments