5e5514a11f
Fix key_input blocking shutdown
...
Discovered in #351 where restart would hang forever.
key_input.rs never properly implemented shutdown because it didn't have
to do anything interesting on shutdown.
Wire up oneshot channels so that it falls in line with other services.
I do wonder though if there's a more clever way of handling this. For
example I could just not use the task_tracker, use tokio::spawn and let
the task get cancelled by tokio.
2025-06-21 23:57:54 +02:00
9904b74d21
basic ui
2025-06-20 11:47:40 +02:00
d166dfc13d
get config and set config
2025-06-20 11:47:40 +02:00
9b759e6b42
add basic restart endpoint
2025-06-20 11:47:40 +02:00
5614c725a0
Merge pull request #418 from EFForg/tplink-hotfix-v9
...
Fix broken installer on TP-Link M7350 v9
2025-06-20 08:09:40 +00:00
5a7fc2a063
Merge pull request #387 from oopsbagel/wingtech-ct2mhs01
...
feat: support Wingtech CT2MHS01 hotspot
2025-06-20 08:00:56 +00:00
e601320b3f
Fix broken installer on TP-Link M7350 v9
...
TP-Link v9 was inadvertently broken via https://github.com/EFForg/rayhunter/pull/390
2025-06-20 02:01:55 +02:00
0b05d1617c
enable null cipher heuristic by default in config
2025-06-18 13:32:37 -07:00
e7ba02173a
update heuristic docs
2025-06-18 13:32:37 -07:00
0b0dd4ed43
add file extensions to downloads, fixes #397
2025-06-18 13:32:37 -07:00
f2ff1be2ec
Disable input keys by default
...
People say it's too easy to press, see #404
2025-06-18 08:44:26 -07:00
9f9adea5a1
Debounce key input events
2025-06-18 08:05:35 -07:00
cb2092d14f
Fix last_message_time showing as 1970 when capture is 0 bytes
...
This is the same bug as #224 , but regressed in the new UI
2025-06-17 16:38:49 -07:00
76cdb3ecf1
re-add warning again
2025-06-17 16:30:22 -07:00
bee5152381
re enable null cipher test
2025-06-17 16:30:22 -07:00
2634271715
re-enable null cipher and update docs
2025-06-17 16:30:22 -07:00
58913314aa
helpful comment
2025-06-17 16:30:22 -07:00
4f5bf4aa78
silence logging and point to specific revision and re-add warning
2025-06-17 16:30:22 -07:00
bfc85c5103
re enable null cipher test
2025-06-17 16:30:22 -07:00
7923327ba9
update binary name. Fixes #128
2025-06-17 16:30:22 -07:00
3ff714972c
fix(installer/wingtech): parse json login response
...
Use serde via reqwest to deserialize the login response from qcmap_auth
when obtaining an authentication token instead of golfing based on the
specific token length.
2025-06-16 00:38:28 -07:00
a5d8e601d9
Merge pull request #399 from oopsbagel/fix-blame-ignore-rev-file
...
chore/fix: fix blame ignore rev file rev
2025-06-16 03:42:57 +00:00
5272a99fb5
chore/fix: fix blame ignore rev file rev
...
Due to rebasing, this pointed to a nonexistent commit.
2025-06-15 20:40:50 -07:00
5d61ad53b4
Merge pull request #394 from EFForg/readme-404
...
Fix broken CI badge in README
2025-06-16 03:32:22 +00:00
88ee4fc87e
Fix broken CI badge in README
2025-06-14 17:13:30 +02:00
8aadfc20f2
fix(installer/wingtech): remove duplicated struct
2025-06-13 22:00:20 -07:00
a234df1e1e
fix(installer/wingtech): only say ok if telnet connected
2025-06-13 21:39:12 -07:00
de25008742
Merge pull request #392 from EFForg/ci-restore-main-workflow-call
...
fix(ci): restore deleted workflow_call trigger
2025-06-14 02:45:25 +00:00
185da9cb36
fix(ci): explain why workflow_call: is needed
2025-06-13 19:42:38 -07:00
c366eb9e4d
fix(ci): restore deleted workflow_call trigger
...
This is required to call this workflow from another workflow, such as
the release.yml workflow.
2025-06-13 19:38:49 -07:00
5dfbeaef64
Merge pull request #390 from EFForg/m7310
...
Add support for TP-Link M7310
2025-06-14 02:36:14 +00:00
62e4c15eb5
Merge pull request #391 from EFForg/fix-workflow-main
...
Do not publish docs from any branch
2025-06-14 02:34:35 +00:00
02c98a8e8e
Do not publish docs from any branch
...
Documentation was being pushed from an unrelated PR that I opened,
because that PR was created from a branch pushed to efforg instead of my
own fork.
2025-06-14 02:10:56 +02:00
6c02f56250
Add support for TP-Link M7310
...
The device is very similar to the M7350, and might as well just be
another hardware version.
2025-06-13 16:04:13 +02:00
f56acdf89d
fix(installer/wingtech): better Response variable
2025-06-12 12:46:08 -07:00
cb6f79f67a
ci: build wingtech
2025-06-12 01:11:01 -07:00
95951c5c38
fix(display/mod.rs): remove "no device" check
...
This check is unnecessary, cargo will not build if fn update_ui is
undefined.
2025-06-12 01:04:29 -07:00
241fb2789b
fix(display/mod.rs): remove "many devices" check
...
This check is unnecessary, cargo will not build if multiple versions of
fn update_ui are defined.
2025-06-12 01:01:05 -07:00
3a3adb055b
fix(installer): wingtech adb error message
2025-06-12 00:45:52 -07:00
3ae2636d9e
chore(installer/build.rs): cargo clippy
2025-06-12 00:44:36 -07:00
79b2628d2f
chore: cargo fmt
2025-06-12 00:43:00 -07:00
cba898daf6
feat(installer/util): telnet functions in util.rs
...
Add installer util wingtech-start-telnet command.
Add installer util wingtech-start-adb command.
2025-06-12 00:39:27 -07:00
cb1df974e4
feat: support Wingtech CT2MHS01 hotspot
...
Add support for the Wingtech CT2MHS01 hotspot, a Qualcomm mdm9650-based
device with a screen available for US$15-35. This device is often used
as a base platform for while labeled versions like the T-Mobile TMOHS1.
AT&T branded versions of the hotspot seem to be the most abundant.
The device has a framebuffer-driven screen at /dev/fb0 that behaves
similarly to the Orbic RC400L, although the userspace program
`displaygui` refreshes the screen significantly more often than on the
Orbic. This causes the green line on the screen to subtly flicker and
only be displayed during some frames. Subsequent work to fully control
the display without removing the OEM interface is desired.
2025-06-11 18:06:50 -07:00
86e08f9a85
Allow enabling/disabling analyzers from config file ( #382 )
...
Co-authored-by: Will Greenberg <willg@eff.org >
2025-06-10 21:37:38 +02:00
fb2149f0c8
Loosen up issue templates
...
A lot of the bug report we receive are about the web UI or the installer
failing, and there things like capture date just don't matter. We could
create separate templates for these types of bugs, but I'd think it's
probably better to just have one textbox with a few "reminder" questions
that are all optional.
Feature request template I think doesn't have this issue.
Also allow the creation of blank issues, because some issues are more
related to CI or devenv and don't neatly fit in any category. Let's just
hope nobody abuses that?
2025-06-10 11:49:56 -07:00
bf2b00ce47
doc(faq): send commands with installer util shell
2025-06-10 11:49:20 -07:00
fd453900c2
doc(faq): format code correctly
2025-06-10 11:49:20 -07:00
3d29c5f306
doc: add re-enabling USB tethering to the FAQ
...
Fixes issue #294
2025-06-10 11:49:20 -07:00
74623dea02
doc: Fix instructions for mac quarantine bit ( #385 )
2025-06-10 00:33:12 +02:00
48e73a0a41
revert accidental futures upgrade
2025-06-06 12:44:39 -07:00
Markus Unterwaditzer