Richard J. Acton
My feedback
23 results found
-
5 votesRichard J. Acton
supported this idea
·
-
2 votesRichard J. Acton
supported this idea
·
-
12 votesRichard J. Acton
supported this idea
·
-
143 votes
An error occurred while saving the comment -
1,408 votesRichard J. Acton
supported this idea
·
-
4 votes
An error occurred while saving the comment Richard J. Acton
commented
Probably (hopefully in my view given how spread proton already is) out of scope for proton for now.
For some detailed information on configuring pfsense/opensense firewalls for privacy see:
https://inteltechniques.com/firewall/ -
20 votesRichard J. Acton
supported this idea
·
-
27 votesRichard J. Acton
supported this idea
·
An error occurred while saving the comment Richard J. Acton
commented
It would be nice to see webfinger configured to allow tailscale and other platforms that support this approach to adding external OICD providers added to simplelogin's sign in services see:
https://github.com/simple-login/app/discussions/1927
https://tailscale.com/kb/1240/sso-custom-oidc -
61 votes
An error occurred while saving the comment Richard J. Acton
commented
Quad9 already exists: https://www.quad9.net/ operated by the Swiss-based Quad9 Foundation
-
53 votes
An error occurred while saving the comment Richard J. Acton
commented
I personal think that separate apps are preferable so that you can use only what parts of the proton suite you want to - An installer that lets you select from all of the proton apps that you'd like to have installed would be preferable to a monolithic app.
(Maybe a metapackage with all the apps for linux package repos in whatever packing guideline proton provides to linux packagers.)
On the sign-in to multiple apps issue - maybe some kind of integration with OS level keyrings to store proton session tokens so you only need to login once, except pass that should probably be kept separate.
-
69 votesRichard J. Acton
supported this idea
·
-
349 votes
An error occurred while saving the comment Richard J. Acton
commented
Aegis covers this use case if you sync the local export via proton drive or other could sync you trust e.g. a self-hosted nextcloud server. Proton should not spend their limited dev time on a problem that already has a good libre/open source solution.
Doing this is a bit of a security improvement over having your TOTP codes in proton pass as they have a separate encryption key from aegis so someone with access to your proton account would still need to ***** the encryption on your aegis vault backup separately. This is less secure than Yubikeys as has been pointed out but of course less vulnerable to locking you out of your stuff if your only copies are lost/destroyed - as usual there's a trade-off.
-
764 votesRichard J. Acton
supported this idea
·
-
180 votes
Hi everyone,
For our thoughts on Monero, check out our Bitcoin deep dive with Seth on the latest Opt Out podcast: https://www.youtube.com/watch?v=gUGJje2jvck
Richard J. Acton
supported this idea
·
-
3,139 votesRichard J. Acton
supported this idea
·
-
401 votesRichard J. Acton
supported this idea
·
-
379 votesRichard J. Acton
supported this idea
·
-
40 votesRichard J. Acton
supported this idea
·
-
90 votesRichard J. Acton
supported this idea
·
-
188 votesRichard J. Acton
supported this idea
·
Possible duplicate: https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/47641541-proton-identity-sso-idp