Proteção contra impressão digital não está funcionando corretamente
Categories
(Firefox for Android :: Privacy, defect)
Tracking
()
People
(Reporter: samuel.elias, Unassigned, NeedInfo)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Android 10; Mobile; rv:132.0) Gecko/132.0 Firefox/132.0
Steps to reproduce:
- Estava configurando a privacidade do navegador;
- Ativei o modo de proteção rigorosa e testei a impressão digital de Favicon no supercookie.me;
- Pareceu funcionar da primeira vez, mas voltou a gerar o identificador após reiniciar o navegador.
Actual results:
A proteção contra impressão digital simplesmente se desligou ao reiniciar o navegador (descobri testando a flag no Firefox beta, já que o Firefox normal não tem about:config por motivos misteriosos). Estou tendo que utilizar o Firefox Beta por enquanto por causa da flag "resistfingerprinting" que ajuda a quebrar um galho, mas faz a aceleração de hardware não funcionar em sua capacidade máxima em alguns sites (e limita a taxa de atualização a 60 Hz)
Expected results:
A proteção deveria se manter ativa (em ambas as versões do navegador).
Reporter | ||
Comment 1•8 months ago
|
||
Reporter | ||
Comment 2•8 months ago
|
||
Reporter | ||
Comment 3•8 months ago
|
||
Aparentemente, mudar para o personalizado e alterar o bloqueio de fingerprinters para "em todas as abas" faz ele voltar a funcionar.....
Comment 4•8 months ago
|
||
The severity field is not set for this bug.
:Gela, could you have a look please?
For more information, please visit BugBot documentation.
Reporter | ||
Updated•8 months ago
|
Reporter | ||
Comment 5•8 months ago
|
||
Como eu faço para editar? Era para estar no S3
Olá!
Como eu faço para editar? Era para estar no S3
As the component owner, I will be setting the priority/severity on this. I unfortunately do not speak much Portuguese but from my understanding, this seems to be similar to this ticket someone else opened a while back: FPP settings keep resetting on Android.
Can you take a look and let me know if I understood this ticket correctly?
Obrigado!
Comment 8•8 months ago
|
||
Thank you for reporting this bug!
If I understand correctly, this issue was likely solved by bug 1909024. The fix starts in v132. I'll cc the patch author of that bug on this bug too.
A couple of questions:
- My understanding is that this bug is reported for v131 release, is that correct?
- The fix in bug 1909024 hasn't made it to release yet, but will early next week.
- Can you confirm that the setting works as expected in v132 Beta?
- The fix is coming in through v132, so if it works in Beta, it is likely fixed by bug 1909024.
If you can, please let us know if it is fixed in release later next week after the update to v132.
There is also a Nimbus experiment in this area. I don't think it is interferring, but you could check enrollment through looking at "Nimbus Experiments" enrollment that is revealed by pressing "About Firefox" and then pressing the logo multiple times.
Comment 9•7 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:Gela, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE
if it is not actionable?
For more information, please visit BugBot documentation.
Description
•