doc: Add WARNINGs about lack of security in protocols
Change-Id: I72c0b797fda220b9efcc86bd08717585063db591
This commit is contained in:
parent
e18069aa81
commit
ddbe43a366
|
@ -26,6 +26,11 @@ and monitoring of the entire osmo-remsim system.
|
|||
|
||||
The API currently has version 1, and the URL prefix is /api/backend/v1
|
||||
|
||||
WARNING: The RESTful/JSON Web API operates in plain-text,
|
||||
There is no authentication or encryption built into the protocol. It is
|
||||
assumed that the protocol is only spoken over trusted, controlled IP
|
||||
networks, such as inside a VPN or a closed / private corporate network.
|
||||
|
||||
==== /api/backend/v1/clients
|
||||
|
||||
*GET* obtains a JSON list where each element represents one currently
|
||||
|
|
|
@ -8,6 +8,11 @@ It is specified in ASN.1 syntax (see `asn1/RSPRO.asn` in the
|
|||
`osmo-remsim` source code) and uses BER (Basic Encoding Rules) on the
|
||||
transport level.
|
||||
|
||||
WARNING: RSPRO and its underlying transport layer both operate in plain-text,
|
||||
There is no authentication or encryption built into the protocol. It is
|
||||
assumed that the protocol is only spoken over trusted, controlled IP
|
||||
networks, such as inside a VPN or a closed / private corporate network.
|
||||
|
||||
=== Underlying Transport Layer
|
||||
|
||||
RSPRO uses TCP as an underlying transport protocol. As TCP doesn't
|
||||
|
|
Loading…
Reference in New Issue