2020-05-10 20:37:31 +00:00
|
|
|
# guacamole
|
|
|
|
|
|
2020-05-10 23:36:10 +00:00
|
|
|
## secrets
|
|
|
|
|
|
2020-08-28 20:54:34 +00:00
|
|
|
* postgres-password
|
|
|
|
|
* postgres-user
|
|
|
|
|
* postgres-db
|
2020-07-15 09:38:14 +00:00
|
|
|
|
2020-08-11 12:17:35 +00:00
|
|
|
## initial deployment
|
|
|
|
|
|
|
|
|
|
initialise database
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
docker ps | grep guacamole-postgresql.1
|
|
|
|
|
sh init-postgresql.sh $ID
|
|
|
|
|
```
|
|
|
|
|
|
2020-07-15 09:38:14 +00:00
|
|
|
## using ssh keys
|
|
|
|
|
|
|
|
|
|
guacamole does *not* work with the standard openssh format for private keys. ie:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
-----BEGIN OPENSSH PRIVATE KEY-----
|
|
|
|
|
[key goes here]
|
|
|
|
|
-----END OPENSSH PRIVATE KEY-----
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
you need to generate the public/private key pair using:
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
ssh-keygen -m pem
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
this will give you a private key that looks like:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
-----BEGIN RSA PRIVATE KEY-----
|
|
|
|
|
Proc-Type: 4,ENCRYPTED
|
|
|
|
|
DEK-Info: [dec info goes here]
|
|
|
|
|
|
|
|
|
|
[key goes here]
|
|
|
|
|
-----END RSA PRIVATE KEY-----
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
then on the target machine you need to paste the *public* key into the file /home/[user]/.ssh/authorized_keys
|
|
|
|
|
|
|
|
|
|
and the *private* key into the configuration for the guacamole connection
|
