bd5dfb1a75
address most of wills review feedback, fix serialization and stringly error handling in DiagTask::start
2026-05-18 15:30:55 -07:00
0b91a6e5d3
PR chage requests, revision to GPS logging feature, code cleanup
2026-05-18 15:30:55 -07:00
66f0c2a336
Kismet GPS option section per packet dcriped, refactoring to reduce loc
2026-05-18 15:30:55 -07:00
adb316e2d7
GPS information included in PCAP files as comment and with Kismet proposed standard
2026-05-18 15:30:55 -07:00
5019f2a9d1
Bump Rust edition to 2024
...
Includes new cargo fmt changes
2025-06-28 00:13:15 +02:00
9fe75ac961
chore: cargo fmt
2025-04-14 11:49:24 -07:00
0b3c0de481
fix(lib/util): use better names for runtime metadata
...
- document RuntimeMetadata fields
- rename RayhunterMetadata to RuntimeMetadata
- rename RuntimeMetadata.os to RuntimeMetadata.system_os
- remove unpopulated hardware field
- remove unnecessary duplication of datastructure in analyzer harness
2025-03-19 11:48:54 -07:00
f2b5aa2743
feat: show rayhunter version/os/arch in pcap, ndjson, qmdl manifest
...
Create a util mod to provide information about the rayhunter binary and
system.
2025-03-19 11:48:54 -07:00
09d35ccec7
feat(pcap): add operating system kernel name and release
...
Display the uname sysname and release as the OS option in the pcap Section
Header Block, falling back on just the std::env::consts::OS name ("linux") in
the case of runtime errors.
Co-authored-by: Nat Budin <natbudin@gmail.com >
2025-03-19 11:48:54 -07:00
5ae186bc73
feat(pcap): add rayhunter name and version to metadata
...
Add the compile-time name and version to the pcap's Section Header Block
as the shb_userappl option, the canonical place for storing the name of
the application used to create the pcap.[0]
[0] https://ietf-opsawg-wg.github.io/draft-ietf-opsawg-pcap/draft-ietf-opsawg-pcapng.html#section-4.1-10
2025-03-19 11:48:54 -07:00
63e9c53dd4
server listen publicly
2024-02-29 15:19:25 -08:00
775cbcda1e
Transition to async I/O for most things
...
Mixing async and sync I/O leads to a multitude of complications, and
generally speaking it's much more convenient to stick to one paradigm
or the other. Since axum (and many other HTTP servers) use async,
and since async is a convenient model for performing operations like
"handle an MPSC message or file read, whichever happens first", let's
commit to an async interface.
2024-02-22 19:28:58 -08:00
87f18c0c8b
Rename directories (again)
2024-01-30 09:58:05 -08:00
Markus Unterwaditzer