Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
XIII
4 years agoSuper Contributor
How to set up TLS for 1Password Connect?
The documentation on setting up TLS for 1Password Connect is too brief for me...
Where do I need to set OP_HTTPS_PORT ? (On the Pi running Connect? On each client running the CLI? On all of the...
Former Member
4 years agoIt works now!
Awesome! 🎉
Partially off-topic, but security related, so I hope it's allowed:
I would like the *.pem files to only be readable by root, but still share them with the Docker container.
Is this possible? If so, how? If not, what's the best practice here?
Of course that is allowed! Unfortunately, it is somewhat of a problematic thing with Docker. There is no way to mount a file with different permissions than on the host. That means that if the file is accessible by root only, the container have to run as root to read the file. The latter is generally considered to be a bad practice. That is also the reason why Connect's images use a custom user.
What you can give a try though, is: sudo chown 999 <pem-file> and sudo chmod 600 <pem-file>. That will make the user with UID 999 (the UID that is used within Connect's containers) owner of the file and the only user that can read it. Connect should still be able to read the file and any user except for user 999 and root should not be able to read it.