यह पृष्ठ अभी आपकी भाषा में उपलब्ध नहीं है। आप अंग्रेज़ी पाठ पढ़ रहे हैं।
Knowledge base
Change a profile fingerprint
What changes
Sites see another machine: graphics card, screen, fonts and everything else they learn about a computer. Hand-picked values from Change values are cleared: they belonged to the old machine.
What stays
The profile ID, cookies, sign-ins, proxy and location stay the same. The system stays too: a Windows profile is still Windows.
The window before the change
The window names the consequences: sites where the profile is signed in will see a sign-in from a new device and may ask for confirmation. Change fingerprint changes it, Cancel leaves everything as it was.
The old fingerprint cannot be brought back. The profile history keeps a line about the change, without the values.
An open profile
On an open profile the button is grey: the fingerprint goes to the browser at launch. Close the profile and change it.
Many profiles at once
New fingerprint on the selection bar gives each profile a computer of its own. The window warns that a site seeing several of these accounts will see them all change on the same day.
Open and password-closed profiles are skipped and named in the result, for example Fingerprint changed for 3 of 5.
What this does not do
- For a profile in an account the change goes through the server and is not made offline: the fingerprint changes for the whole team at once. A server you built yourself before the update cannot change it, and the window answers The server cannot change a fingerprint yet.
- A profile that exists only on this computer can get a new fingerprint without an account, and it goes to the account with that fingerprint when you sign in. A profile from your account does not get a new fingerprint while you are signed out: the window asks you to sign in, otherwise colleagues would open it as the old computer. A profile with a new fingerprint does not go to a server you built yourself before the update and stays on this computer.
- There is no undo: after the change sites already see the new machine.
- The change does not clear cookies and does not change the proxy.
Where this is decided
The claims that carry the most weight, with the stand that checks each of them.
- After the change the card, the launch of both engines and the fingerprint test show the same new machine, and an open profile is not changed
- apps/desktop/test/новый-отпечаток.js
- A profile without a change keeps the same machine byte for byte, and every generator call takes the seed of the profile
- packages/shared/test/семя-отпечатка.js
- The transfer with the session and Export carry the new machine with the same profile, and a copy or a profile with a new ID does not take it
- apps/desktop/test/новый-отпечаток-переносы.js
- In bulk each profile gets its own machine, and open and password-closed profiles are left alone and named
- apps/desktop/test/новый-отпечаток-пачкой-в-окне.js
Questions
- Why, if every profile already has its own fingerprint?
- When an account on the profile was banned and you start over with the same settings but on a different machine for sites.
- Does the system of the profile change?
- No. The system template stays, and the particular machine inside it changes.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.