Skip to content

[DOCS] Update document to include security model of RPC server #17377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MasterJH5574 merged 2 commits into from
Sep 17, 2024
Merged

[DOCS] Update document to include security model of RPC server #17377

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d90022c
[DOCS] Update document to include security model of RPC server
tqchen Sep 16, 2024
5c53e85
More clarification about RCE
tqchen Sep 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/reference/security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,10 +34,16 @@ The private security mailing address is: `security@apache.org <security@apache.o
Feel free to consult the `Apache Security guide <https://www.apache.org/security/>`_.


Considerations
Security Model
--------------
The default binary generated by TVM only relies on a minimum runtime API.
The runtime depends on a limited set of system calls(e.g. malloc) in the system library.


TVM RPC server assumes that the user is trusted and needs to be used in a trusted network environment
and encrypted channels. It allows writings of arbitrary files into the server and provide
full remote code execution capabilities to anyone who can access this API.


AutoTVM data exchange between the tracker, server and client are in plain-text.
It is recommended to use them under trusted networking environment or encrypted channels.