Actions
Feature #5126
closeduse 'filesystem' class hierarchy for protocol traces
Start date:
04/22/2021
Due date:
% Done:
100%
Spec Reference:
Description
When using SIMtrace2 for passive sniffing, we currently only have very minimal decoding in wireshark.
It would be rather useful to make use of all the information we now have in the pySim 'filesystem' class hierarchy for protocol trace analysis
- input could be GSMTAP (live socket or pcap file open)
- we can passively trace the position in the filesystem hirarchy and know which path/file is selected
- we can print symbolic names of the files as they are selected
- we can decode the binary/record data as it is read or written
- we can decode the status words
Checklist
- logical channel support
- think more about the data model of the various decoding "layers"
- some kind of visualization
Updated by laforge over 1 year ago
- Checklist item logical channel support added
- Checklist item think more about the data model of the various decoding "layers" added
- Checklist item some kind of visualization added
- Status changed from New to In Progress
- Assignee set to laforge
- % Done changed from 0 to 20
Some initial work for this is in laforge/apdu_decoder
branch: https://gitea.osmocom.org/sim-card/pysim/src/branch/laforge/apdu_decoder
Right now the next TODO is to add support for logical channels as the traces I work with make use of them. Each logical channel has its own currently selected file, so the RuntimeState needs to be split up somehow.
Updated by laforge over 1 year ago
- Checklist item logical channel support set to Done
Updated by laforge over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 20 to 100
Applied in changeset commit:pysim|1268ed5f3f8babe57a5d59f311149e0eb4c7592f.
Updated by laforge over 1 year ago
- Checklist item think more about the data model of the various decoding "layers" set to Done
Actions