How to use this website
In order to get the statistics of all ECUs, you need to make a GET reqest of the form:
The server response then contains a
https://asoasecurity.seceng.fim.uni-passau.de/data/statisticsThe server response then contains a
json file containing the configuration statistics.
In order to get the endpoint statistics (statistics on service outputs), you need to make a GET reqest of the form:
The server response then contains a
https://asoasecurity.seceng.fim.uni-passau.de/data/endpoint_statisticsThe server response then contains a
json file containing the endpoint statistics. Those statistics are shown on the
ECU Overview page in the Dataflow Statistics section.
In order to get the configuration file of a single ECU in plain text, you need to make a GET reqest of the form:
Here
Note: The ECU ID for the Stammhirn on the R5 is set to 5000 to distinguish it from the A53.
https://asoasecurity.seceng.fim.uni-passau.de/data/configs?id1=databaseIDHere
databaseID is the unique database id of the queried ECU. The server response then contains the ECU's configuration in plain text.Note: The ECU ID for the Stammhirn on the R5 is set to 5000 to distinguish it from the A53.
In order to get the configuration file of a single ECU in JSON format, you need to make a GET reqest of the form:
Here
https://asoasecurity.seceng.fim.uni-passau.de/data/configs?type=json&id1=databaseIDHere
databaseID is the unique database id of the queried ECU. The server response then contains the ECU's configuration in json format.
In order to get the configuration file of several ECUs in JSON format, you need to make a GET reqest of the form:
Here
https://asoasecurity.seceng.fim.uni-passau.de/data/configs?type=json&id1=databaseID1&id2=databaseID2&id3=databaseID3&...Here
databaseID1, databaseID2, databaseID3 a.s.o. are the unique database ids of the queried ECUs.
In order to get the configuration file of a single ECU in a debian package, you need to make a GET reqest of the form:
Here
(Note that there is no option to get debian packages for several ECUs at one time. If id1, id2, ... are given, only the first one (id1) is returned as a debian package.)
https://asoasecurity.seceng.fim.uni-passau.de/data/configs?type=deb&id1=databaseIDHere
databaseID is the unique database id of the queried ECU. The server response will then contain a debian package, which when installed puts the ECU's configuration file under /etc/.(Note that there is no option to get debian packages for several ECUs at one time. If id1, id2, ... are given, only the first one (id1) is returned as a debian package.)
In order to get the configuration file of a single ECU in a rpm package, you need to make a GET reqest of the form:
Here databaseID is the unique database id of the queried ECU. The server response will then contain a debian package, which when installed puts the ECU's configuration file under
(Note that there is no option to get rpm packages for several ECUs at one time. If id1, id2, ... are given, only the first one is returned as a rpm package.)
https://asoasecurity.seceng.fim.uni-passau.de/data/?id1=databaseID&type=rpmHere databaseID is the unique database id of the queried ECU. The server response will then contain a debian package, which when installed puts the ECU's configuration file under
/etc/.(Note that there is no option to get rpm packages for several ECUs at one time. If id1, id2, ... are given, only the first one is returned as a rpm package.)
In order to get the underlying
json file of the ECU Overview page,
i.e. the summary of all configuration warnings for all ECUs in json format, you need to make a GET request of the form:https://asoasecurity.seceng.fim.uni-passau.de/data/index