Vince
My feedback
7 results found
-
1,471 votes
-
5,017 votesVince
supported this idea
·
-
62 votes
An error occurred while saving the comment Vince
supported this idea
·
-
842 votesVince
supported this idea
·
An error occurred while saving the comment Vince
commented
My basic need is to strictly manage identities. There is a crucial gap, in my opinion. I notice that to use Proton Drive (and ProtonVPN) securely, we need to be able to use an identity without having to share the main secret of our ProtonMail account. However, this seems unavoidable, as it is also the secret for ProtonDrive and ProtonVPN (using rclone and the 'obscure' directive is not enough to ensure sufficient protection). A solution would be for Proton to comply with OIDC/OAuth2, allowing us to use Proton Identities and Aliases in authentication and authorization protocols based on their own service infrastructures, i.e., without relying on external elements to enable integration that would then need to be verified and maintained with the associated secret management. We are aware that this business direction requires some investment and preparation to meet the demand that would certainly follow. But it seems already taken since a Business offer of Proton Drive is established. This offer cannot reasonably operate without these additional shared services, which are certainly already operating in your billable services. Your business model is indeed at stake, but you need to start by aligning these elements and responding to the community. It is clear that you face the same challenges of functional evolution with a highly visible security aspect, and we understand the required caution. Looking forward to your response.
-
241 votesVince
supported this idea
·
-
590 votesVince
supported this idea
·
-
602 votesVince
supported this idea
·
Instead of repeating myself (it would be great to be able to 'link' ideas), ->
see: https://protonmail.uservoice.com/forums/932839-proton-drive/suggestions/43582125-proton-drive-api?page=1&per_page=20