Network Config Split (Day 10, mobile-android)
Summary
Each APK carries assets/huntress_puzzle.json (schema huntress.mobile.puzzle.v1). For this challenge the codec is split: data is empty and the answer is spread over parts, reassembled using the order index list into ANS-<16 hex>. The Android topic (manifest vs Network Security Config variants, cleartext/transport exception) is flavour; the puzzle asset determines the answer.
Method
- Unzip the APK (artifact_0.bin, 8 entries, one classes.dex).
- Read the puzzle asset: codec
split, three parts, order[2,0,1]. - Apply the codec in the banked adapter
challenges/_lib/autosolve_mobile.py(split codec already supported). - Submit under answer_id
answer(exact normalization).
Results - all three modes CORRECT
- Single Solve: Token0749c5f0d5a1612672780ef00003210e (autosolve, 1.3 s).
- Time Trial: Tokenac37cd9cbf6e5cc3e5a137e563e456d7 (13:05:30Z).
- Mastery: Tokenef0cae966027446056f6741f9d5f778b (13:05:32Z).
Correction to the first draft
This file recorded Time Trial / Mastery as "GM returned HTTP 409 timed_intent_not_available at claim time ... only the timed routes were not yet open". The routes were open the whole time. On a LEGACY single-pool timed route the GM rejects the run_for_time property itself - true OR false - while a plain op=start with the property omitted opens a normal, hall_of_fame_eligible attempt. The same unchanged adapter then solved both modes. Root cause and the permanent fix (ctf_gm.GM.start, autosolve_script.start, regression cases in _test_rotation_fix.py) are documented in challenges/Day 10/Bind Over Matter/Bind_Over_Matter_Writeup.md. Day 10 finished 15/15.
Notes
- The puzzle is per-attempt; always derive from that attempt's own APK, never hard-code.