Eric Phillips
34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
---
|
|
title: "ProtonMail Bridge Setup"
|
|
date: 2020-09-19T23:12:36-06:00
|
|
tags:
|
|
- mail
|
|
- protonmail
|
|
- howto
|
|
- guide
|
|
draft: false
|
|
---
|
|
|
|
# Bridge Setup with seperate user
|
|
Protonmail Bridge is a neat little tool to get your protonmail emails onto your local machine. This offers several interesting possibilities for backup and using an alternative email client, ie mutt. Using it on linux is pretty painless, except for it's interaction with my password store. I use [pass](https://www.passwordstore.org/) with git and I have git setup to require signing for every commit. I also use a yubikey to store my gpg signing key and requires a pin for every signature. The protonmail bridge changes the information stored frequently and thus causes me an issue. I decided to solve it by creating a user, proton, on my system specifically to run the bridge with it's own password store just for protonmail. This solves my issue with entering my pin frequently and also limits exposure of my other passwords to the protonmail bridge program.
|
|
|
|
I used the -g option and added the new user to my group so that I would have access
|
|
|
|
`# sudo useradd -m -g myuser proton`
|
|
|
|
`# sudo su proton`
|
|
|
|
Create a gpg key, start a tmux session first to avoid gpg permission denied error
|
|
|
|
`# gpg --full-generate-key --expert`
|
|
|
|
select ecc and ecc, use comment section for details on it being for protonmail bridge user, no password
|
|
|
|
initialize the password store
|
|
|
|
`# pass init user@something.xyz`
|
|
|
|
Then setup the [protonmail bridge](../proton-mail-bridge)
|
|
|
|
Automating the startup of the bridge and getting mutt setup will be in a forthcoming post(s)
|