Turkish Turkish language support: there is a level of Turkish language support that can be considered successful. For example, you can delete a message within 24 hours. Protonmail encryptionĭeleted e-mail: sent e-mail can be deleted within the specified time. It’s not mandatory, but it’s a security enhancement. No ads: there are no ad impressions about your correspondence, as in Gmail.Įncrypted e-mail: Protonmail sets a special password for non-users so that the other party can see the content. All servers are kept 1,000 meters below the ground in Switzerland. Swiss privacy and security: no problem if you trust the country’s data security and neutrality policy. The focus is on fast reading, editing and sending. Open source: ProtonMail code is open source and basic user accounts are free.Įasy operation and lean design: access is available via any device. So encrypted emails cannot be shared with third parties.Īnonymous e-mail: No IP log records are kept that can be connected to the account. Then re-ran "protonmail-bridge -cli" and was able to continue with login.Other Additional Information About ProtonMailĮnd-to-end encryption: there is security with end-to-end encryption for all emails. I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. "Protonmail-bridge -cli" results in no further output in the terminal once run in an unraid docker container. Unfortunately beyond this I dont really know what else to try. This has solved my issue of being able to access the cli after the initial install. This hasn't been an issue for me however ymmvĬredit to for this addition. I have no means to make any changes to any settings other than a fresh install. After this first launch the cli command will only inform me that the bridge is running but will not actually give me access to input cli commands. There may be means to get back into the cli but I haven't found it. But the docker has been running as it should and I can connect to it no problem using the detail.
Once I exit cli mode I have never been able to access it again.
So I had to login and set the bridge up in seperate inbox mode and copy the settings to a txt file incase I ever need them later. However this will only work this one time. Gpg -generate-key -batch /protonmail/gpgparams I had to enter the following commands to get the bridge up and running. When I first install and put in "protonmail-bridge - cli" i always got the output that the bridge wasn't running. So delete the app data and container and start from scratch. I only ever seem to be able to access the cli one time and then I never get access again. First of all this all has to be done on the first install of the docker. This is a bit finicky on unraid but here's what I did to get it up and running.
0 kommentar(er)
