stack
/
guacamole
1
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity
9 Commits 6 Branches 5 Tags 288 KiB
SQL 90.7%
Jsonnet 5.9%
Shell 2.9%
Dockerfile 0.5%
Go to file
Giles Bradshaw 2b50ba9c66
continuous-integration/drone/push Build is passing Details
ci: remove certificates from .gitignore 		2020-08-11 11:00:12 +01:00
guacamole-postgresql . 2020-05-10 21:59:45 +01:00
.drone-home.star . 2020-05-10 21:59:45 +01:00
.gitignore ci: remove certificates from .gitignore 2020-08-11 11:00:12 +01:00
CHANGELOG.md chore(release): 0.0.1 2020-08-11 10:47:45 +01:00
README.md Update 'README.md' 2020-07-15 09:38:14 +00:00
build.sh ci: path top docker corrected 2020-08-11 10:56:04 +01:00
deploy.sh ci: package.json scripts and release 2020-08-11 10:47:20 +01:00
docker-compose.yml . 2020-05-10 21:59:45 +01:00
package.json ci: package.json scripts and release 2020-08-11 10:47:20 +01:00
yarn.lock ci: package.json scripts and release 2020-08-11 10:47:20 +01:00

README.md

guacamole

secrets

  • guacamole-postgres-db
  • guacamole-postgres-password
  • guacamole-postgres-user
  • local-docker-registry
  • registry-password

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:

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