docs/designs/virtual-media.md

18 ISO/IMG image mounting, and remote CIFS/HTTPS image mounting.
24 - NBDkit is being used, to serve images from remote storages over HTTPS/CIFS.
37   communicate over Secure WebSockets directly to HTTPS endpoint hosted by bmcweb
40   schemas, then BMC process connects to external CIFS/HTTPS image pointed during
54 |  |WebBrowser  +<----HTTPS------->+BMCWeb    |      +---------+  |     |  +----------+         |
66 |   |ISO/IMG    +<---CIFS/HTTPS+-->+NBDkit   |                    |     |                       |
114 Server. Browser is responsible for create HTTPS session, authenticate user, and
115 receive given privileges, then upgrade HTTPS session to WSS, through mechanisms
116 described by [RFC6455](HTTPS://tools.ietf.org/html/rfc6455). Since WSS upgrade,
121 different URIs in HTTPS server. Number of available simultaneous connections is
124 Encryption for proxy is supported through HTTPS/WSS channel and inherits
125 encryption mechanisms directly from HTTPS server, all data transactions go
134     │ establish HTTPS session │                 │                      │          │         │
174 CIFS/HTTPS images. The current implementation supports only stream mounting as
177 a separate component responsible for handling CIFS/HTTPS traffic called NBDkit.
180 nbkit instances, the number of available instances for CIFS/HTTPS is configured
184 security practices, as remote server support such (i.e. HTTPS requires SSL, and
192 │Browser│  │CIFS/HTTPS│  │bmcweb│  │VirtualMedia│           │NBDkit││NBDClient││uDEV│ │USBGadget│
194     │establish HTTPS session│            │                     │         │       │         │
202     │           │           │ CIFS/HTTPS │                     │         │       │         │
331 - Spawning nbdkit, and monitor its lifetime, for CIFS/HTTPS connections.