Ip address leaks and some Fingerprints privacy problem

[NHM2005]

Preliminary checklist

• I have read the README
• I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
• I have searched wont fix issues and this request is not among them
• This is a feature request for the Cromite browser; not the website nor F-Droid nor anything else.

Is your feature request related to privacy?

Yes

Is there a patch available for this feature somewhere?

See here on github. Here has Anti-Browser-Fingerprinting measures that is unavailable on cromite.
https://github.com/woheller69/browser#Instructions

Describe the solution you would like

1. I turned on WebRTC for some feature. But after turning on this, it leaks Local IP address. I know Firefox, brave browser, they can hide IP address, though WebRTC turned on. There has technology to hide them. Please, Hide local IP.

Details

2. At Brave, you see canvas and WebGL fingerprint shows "randomized by first party domain"

Details

But Cromite shows only randomize. Please upgrade privacy.

Details

3)At upper screenshot "WEBGL VENDOR & RENDERER" shows real name. But at firefox, it keeps hidden. Shows fake. What do you think about this.

4. HARDWARE CONCURRENCY shows fake value but not randomized like brave.
   I don't know which is better. You know better.

Details

Describe alternatives you have considered

Null

[uazo]

. Here has Anti-Browser-Fingerprinting measures that is unavailable on cromite.

can you be more detailed. what do you think cromite is missing?

I turned on WebRTC for some feature ... Please, Hide local IP.
What do you think about this.

logic tells me that if I reactivate a feature, I reactivate it completely. same thing for webgl.

At Brave, you see canvas and WebGL fingerprint shows "randomized by first party domain"

So? what do you think it means?

HARDWARE CONCURRENCY shows fake value but not randomized like brave.

again, so what? I don't disagree with changing the logic, I just wish it was explained why. as ‘brave’ does, it is not a reason.

[NHM2005]

Here has Anti-Browser-Fingerprinting measures that is unavailable on cromite.

Which is unavailable I told you upper at 4 points

1. Hide local Ip 2) "First party randomization" for canvas and Webgl 3) "WEBGL VENDOR & RENDERER" randomizations
   4)"HARDWARE CONCURRENCY" randomization.

(1-4) available at this open source browser, so I shared link if it helped you.

logic tells me that if I reactivate a feature, I reactivate it completely. same thing for webgl.

Look-out another browser. (Firefox, brave). They can hide local Ip address. Even without disabling feature. It's also about privacy.
I know turning on webgl, it's normal that local Ip will be showed. But technology is available in the open source browser I shared you. Local Ip is also a part of security. Cromite is privacy focused browser. So, I told you.

HARDWARE CONCURRENCY shows fake value but not randomized like brave.

For randomized Fingerprints. For extra security. It helps making more Fingerprints protection. And way to be more anonymous.
https://coveryourtracks.eff.org I tested Fingerprint protection with this websites, it doesn't detect as randomized Fingerprints. I think making Hardware currency randomizer, it will say "randomized Fingerprints."

All above , I think it makes more privacy for Fingerprints.
I don't know more. I'm not expert.
But If open source code is available, what is problem implementing this if it gives extra Fingerprint protection.

[uazo]

so I shared link if it helped you.

thank you, but the technical basis is lacking. to date, the complete disabling of the feature is more than sufficient.

But If open source code is available, what is problem implementing this if it gives extra Fingerprint protection.

webgl and webrtc are already covered by antifingerpriting. i don't think activating a feature by half is the right way to go.

For randomized Fingerprints. For extra security. It helps making more secure.

I don't think it has anything to do with it.

fingerpriting technologies rely on intrinsic browser values that make it clear that the browser is the same but the device is different.
Some values carry more weight than others when the possibility of different values is higher.
Since I don't have any data available (cromite doesn't have any telemetry) so I rely on the logic that if I can, I set a constant that doesn't allow different devices to be distinguished in the same browser.
this is why ‘hardware currency’ is fixed and not random.

[NHM2005]

Okey. Thank you very much for explain.

…

On Mon, May 20, 2024, 2:21 PM uazo ***@***.***> wrote: so I shared link if it helped you. thank you, but the technical basis is lacking. to date, the complete disabling of the feature is more than sufficient. But If open source code is available, what is problem implementing this if it gives extra Fingerprint protection. webgl and webrtc are already covered by antifingerpriting. i don't think activating a feature by half is the right way to go. For randomized Fingerprints. For extra security. It helps making more secure. I don't think it has anything to do with it. fingerpriting technologies rely on intrinsic browser values that make it clear that the browser is the same but the device is different. Some values carry more weight than others when the possibility of different values is higher. Since I don't have any data available (cromite doesn't have any telemetry) so I rely on the logic that if I can, I set a constant that doesn't allow different devices to be distinguished in the same browser. this is why ‘hardware currency’ is fixed and not random. — Reply to this email directly, view it on GitHub <#1085 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BINP5AFHIZTKW3MQXATGXMLZDGW7TAVCNFSM6AAAAABHSBJ2W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZHEZDOMRUGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[github-actions]

This issue has been automatically marked as stale as there has been no recent activity in response to our request for more information. Please respond so that we can proceed with this issue.

[github-actions]

This issue has been automatically closed as sufficient information hasn't been provided on the issue for further actions to be taken. Feel free to add more information.

[NHM2005]

What the hell?🙄

[uazo]

it does not seem to me that this issue needs any development activities.