Questions about using with TOR entry (image proxy, other connections)

[TimmyBoi155]

Want to say firstly thank you for this application. It's amazing. Even if proton comes out with a desktop client, i will likely keep using this one.

I want to use this over TOR. But I have a few questions about it:

1. If I use the TOR API, how are images loaded through proton's image proxy? Do you merely use the clearnet URL but through the TOR network? or does proton have an onion based image proxy?
2. If I have 2 accounts connecting over tor, can they be correlated to each other in any way that you are aware of? Locally-speaking. Also, does each TOR account have individual tor circuits?
3. Are there any other connections that are made by the webclient besides these? and are they requested over TOR?

Thanks in advance

[TimmyBoi155]

Also, I'm currently having an issue, where, if I try to log in under the TOR API, the "Log In" button loads for 1 second, then stops loading, and nothing happens. It just stays at log in. However, it works fine under proton.me

My local tor socks5 proxy is started too

[vladimiry]

Proton uses core/v4/images API call to load remote images. The address depends on the API entry point you selected in the app on the account edit form. There was an issue with API address resolving in recent app versions, but got fixed in v5.1.6.

Are there any other connections that are made by the webclient besides these? and are they requested over TOR?

I don't know, since I'm not the author of the webclient project, but enabling Block non "API entry point"-based network requests flag on the account edit form supposed to block non-API entry point based requests. The hcaptcha.com domain is kept in the whitelist.

If I have 2 accounts connecting over tor, can they be correlated to each other in any way that you are aware of? Locally-speaking. Also, does each TOR account have individual tor circuits?

There are many different techniques, so I guess if you got targeted for some reason, they might find a way to mark you as a user of multiple accounts.

I'm currently having an issue, where, if I try to log in under the TOR API, the "Log In" button loads for 1 second, then stops loading, and nothing happens.

It worked before, so apparently proton changed something at the backend side (like for example API subdomain use schemes). So I put it as an upstream backend-related breaking change.

[vladimiry]

I'm currently having an issue, where, if I try to log in under the TOR API, the "Log In" button loads for 1 second, then stops loading, and nothing happens.

Just tested it and it works. So I guess you missed specifying the socks5://localhost:9050 proxy address for the account (or other address if you have changed the defaults), see #113 (comment).