linux-cli-community icon indicating copy to clipboard operation
linux-cli-community copied to clipboard

[Enhancement] Add a section for encrypted home directories in USAGE.md

Open clemdep opened this issue 5 years ago • 3 comments

Is your feature request related to a problem? Please describe. Many users are encountering issues when they have encrypted home directories, which is quite common on Linux systems. When following the steps to auto-connect to VPN on boot, they will fail because a few additional steps are required when working with a home directory. For examples see #124 , #175 , #174 .

Describe the solution you'd like I am aware that a big update is in the works which will fix the root issue, but in the meantime a few edits (2 additional steps) to USAGE.md could help people setting up the auto-connect service even with encrypted home directories.

Describe alternatives you've considered There are no alternatives AFAIK.

Additional context The content to be added to USAGE.md is actually quite concise, just 3 lines, I could open a PR for that if it is appropriate.

clemdep avatar Jun 11 '20 22:06 clemdep

I'd be happy about a PR :)

Rafficer avatar Jun 12 '20 11:06 Rafficer

Ahh sorry!! :scream: I'm new to contributing to projects and have gone about this entirely backwards!! :worried:

I have been struggling on and off to get protonvpn to auto connect at boot for months. It hasn't been a high priority. I tried one more time today and finally figured out that the problem was the encrypted home drive!! It's not opened/unencrypted until after the systemd service starts so protonvpn-cli can't access the configuration. I went and edited the USAGE.md file and submitted a pull request with the "memo" that I'm unsure whether how I've made it work: running protonvpn-cli as the root user, is a security issue or not. Now I'm trying to contact people to check and I discover I've gone about it backwards. I'm supposed to talk first, then code.

My apologies :bow:

storyjesse avatar Jun 14 '20 13:06 storyjesse

Having read the issues linked to above, it appears that what I've done is actually what you were asking someone to do. I'm afraid I don't know what a PR is. I've added one more push since I forgot to include the need to sudo systemctl daemon-reload. And a small section on troubleshooting (how to find the service logs).

Me apologies again if I be messin' with stuff. I do be a Pirate but a good man all the same. :stuck_out_tongue_winking_eye:

storyjesse avatar Jun 14 '20 14:06 storyjesse