This commit is contained in:
2024-06-28 23:49:16 +02:00
commit 86f60da6ec
107 changed files with 25057 additions and 0 deletions

View File

@@ -0,0 +1,16 @@
# Needed Metadata
- _Must_ contain IP address of *IoT* device
- _Can_ contain IP addr of capture host
# Options
## tcpdump options
see [[tcpdump]]
## kybcap options
| Option | Desciption|
| ------- | ---------- |
| `--setup` | Go through guided setup process |
| `--meta-config` | Go through guided meta data setup |
| `--mdevice=` | _Metadata_ : Specify device name |
| `--mipdev=` | _Metadata_ : Specify device ip address |
| `--mmac=` | _Metadata_ : Specify device MAC address |
| `--to-csv` | _post_processing: extract pcap into csv |

1
notes/testbed/scope.md Normal file
View File

@@ -0,0 +1 @@
What is scope if testbed as a system?

View File

@@ -0,0 +1,14 @@
FAIR data + privacy metric evaluation algos.
Dataset offers some schema.
Privacy metric requires some set of features.
**Case 1**
dataset schema = required features by privacy metric
**Case 2**
dataset schema $\subset$ required features ->
_2.1:_ feature extraction algo(s) exists, which can computed missing features
_2.2:_ missing features CANNOT be computed form available schema/data
**Case 3**
dataset schema $\supset$ required features -> project schema down into relevant feature space/ leave out uneeded data
**Case 4**
Unknown relationship -> further investigaton needed
Is this realistic case?