@@ -29,7 +29,7 @@ To build `nexush`, `nexus-cli` and `nexus-exam` read the [following documentatio
## Obtaining nexus-clients
Precompiled nexus client binaries can be found in this git repository: [https://gitedu.hesge.ch/isc/projects/nexus-client-bin](https://gitedu.hesge.ch/isc/projects/nexus-client-bin)
Precompiled nexus client binaries can be [found here](https://drive.switch.ch/index.php/s/d89cBJBbGvpc4nO).
Two clients are available:
...
...
@@ -546,17 +546,18 @@ First, you need to create the VM that will be used by the students during the ex
## Advanced use: configuring nexush and nexus-cli
Because communication between nexus client and nexus server is encrypted, a public certificate is required. Both clients, `nexush` and `nexus-cli`, embed the right public certificate to communicate with the server. By default, they are also configured to communicate with the production nexus-server available at ISC.
Because communication between nexus client and nexus server is encrypted, a public certificate is required. Both clients, `nexush` and `nexus-cli`, embed the necessary public certificate to communicate with the server. By default, they are also configured to communicate with the production nexus-server available at ISC.
Both clients can be configured to communicate with a different nexus server and a use a different public certificate. We describe below how to configure them to do so.
Both clients can be configured to communicate with any nexus server. ISC has two nexus serveurs, one for production use and one for development. The corresponding public certificates can be found in the `certificates` directory on this git repository.
<!--
Because communication between client and server is encrypted, a public certificate is required. It is available in the `certificates` directory:
Here are the ip addresses, ports and certificates to use ISC's production and development nexus servers:
-`ca-cert.isc-nexus-prod.pem`
-->
| Server | IP | Port | Certificate |
|--- |--- |--- |--- |
| production | 10.136.26.127 | 1077 | ca-cert.isc-nexus-prod.pem |
| development | 10.136.26.125 | 1077 | ca-cert.isc-nexus-dev.pem |
Clients use two environment variables to specify which nexus server to use and on which port, and which public certificate to use:
Nexus clients use two environment variables to specify which nexus server to use and on which port, and which public certificate to use:
| Variable | Description |
|--- |--- |
...
...
@@ -565,7 +566,7 @@ Clients use two environment variables to specify which nexus server to use and o
On Linux and Mac OSX, a simple and effective way is to store these variables in a `.env` file that is sourced before running the clients.
Here is an example of `.env.nexus` file containing the following lines:
Here is an example of `.env.nexus` file configured to use the production ISC server:
```
export NEXUS_SERVER=10.136.26.127:1077
...
...
@@ -638,7 +639,7 @@ These capabilities are called "VM access capabilities":
| VM_READFS | User can export files from the VM |
| VM_WRITEFS | User can import files into the VM |
#### IMPORTANT
### IMPORTANT
- When a user creates a VM, she/he is **automatically granted all VM access capabilities**.
- No other users is granted any access to the created VM. However, the VM owner can add any access type to any users they like.
