In the coming months, the integration of the SimpleLogin functionality into ProtonMail will be improved, meaning the Proton community will be able to hide their email addresses using SimpleLogin. This makes SimpleLogin a complementary service to ProtonMail, with ProtonMail protecting data privacy with encryption while SimpleLogin prevents malicious actors from exploiting real email addresses. If a service a user signed up for gets hacked, sends spam, or sells emails to advertisers, that email alias can be disabled to safeguard the inbox. As the name suggests, it is a simple way to create a login, generating an email alias so that users don’t need to disclose their real email address. Even a poorly documented one would be better than this.ĮDIT: I did a bit more digging and it seems the WebClient requires a human verification when 9001 occurs, so maybe something for this needs to be implemented?ĮDIT 2: I went and cleared my cookies for ProtonMail as well and was not shown a captcha or anything of the sort, so that's odd as well.SimpleLogin is a browser extension, web app, and mobile app that provides users with anonymous email addresses whenever they sign up for a new online service. Man times like this just make me with ProtonMail would just release a documented API already. I have been looking through the WebClient source code and honestly this whole thing feels like a mess of spaghetti, but I'm trying to figure out how exactly they are doing their API. Lemme know if there's any more info that would help. I seem to get this same error on all my machines, regardless of connection and location.
I don't get this same error from the same exact connection when logging into the WebUI (Same exact computer).It seems the server doesn't even get to the point of checking the password, since you can put in an incorrect password and still get the same error (9001).Changing the client version to the same as the new web client.Using as the API URL instead of protonmail.ch (To see if it's an API issue, as maybe the old WebUI has a different auth API than the new one).ProtonMail has a way of detecting if the client sending is actually the bridge or not.Although I looked at the python one and it used the same exact API it seemed The API has changed and this one is depreciated now.That being said, it seems that WebClient uses the same exact key The new web client came out, and with that, a new modulus pubkey for SRP.So I've been digging around and I think I might have a few theories on why this is happening:
0 kommentar(er)
