Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The idea initially was to have online games managed by a Steam on a VM that's online, while the host would be segregated from online activities. Then, I thought I can probably manage to deny Steam from updating its client, so there would be no danger an online client would pose to the single player library - that is, the danger that some update, in some dystopian near future, would ask me to log in a manner I do not intend to use (wink-wink).
But, if I can block Steam client from updating, then I could technically be online and swap libraries.
Maybe you're right. Maybe I don't need security that much hardened. If I can stop the client itself from updating, then I don't even need segregate libraries.