1c2f842a98
Even though it has nothing to do with vnc, we keep the name of the api call for compatibility with our xtermjs client. termproxy: verifies that the user is allowed to open a console and starts termproxy with the correct parameters starts a TcpListener on "localhost:0" so that the kernel decides the port (instead of trying to rerserving like in pve). Then it leaves the fd open for termproxy and gives the number as port and tells it via '--port-as-fd' that it should interpret this as an open fd the vncwebsocket api call checks the 'vncticket' (name for compatibility) and connects the remote side (after an Upgrade) with a local TcpStream connecting to the port given via WebSocket from the proxmox crate to make sure that only the client can connect that called termproxy and no one can connect to an arbitrary port on the host we have to include the port in the ticket data Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> |
||
---|---|---|
.cargo | ||
debian | ||
docs | ||
etc | ||
examples | ||
src | ||
tests | ||
www | ||
zsh-completions | ||
.gitignore | ||
Cargo.toml | ||
defines.mk | ||
Makefile | ||
README.rst | ||
rustfmt.toml | ||
TODO.rst |
``rustup`` Toolchain ==================== We normally want to build with the ``rustc`` Debian package. To do that you can set the following ``rustup`` configuration: # rustup toolchain link system /usr # rustup default system Versioning of proxmox helper crates =================================== To use current git master code of the proxmox* helper crates, add:: git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox" or:: path = "../proxmox/proxmox" to the proxmox dependency, and update the version to reflect the current, pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0"). Local cargo config ================== This repository ships with a ``.cargo/config`` that replaces the crates.io registry with packaged crates located in ``/usr/share/cargo/registry``. A similar config is also applied building with dh_cargo. Cargo.lock needs to be deleted when switching between packaged crates and crates.io, since the checksums are not compatible. To reference new dependencies (or updated versions) that are not yet packaged, the dependency needs to point directly to a path or git source (e.g., see example for proxmox crate above).