Jump to content

My Browser Builds (Part 3)


Recommended Posts

1 hour ago, nicolaasjan said:

Yes, but there are a lot of Android and ChromeOS users, so fingerprinting will become useless over time, when more and more people visit such sites.

If the script is first party and the site doesn't work properly without it, what then?

I will answer you by integrating some info that has already been written:

 

https://www.ghacks.net/2021/05/14/custom-browser-protocol-handlers-may-be-used-for-fingerprinting/

Quote

When you install certain applications on your desktop systems, so-called custom protocol handlers may be added. These are used to launch the application in question, e.g. to initiate a Skype call or open a game on Steam.

Popular applications such as Skype, Spotify, Discord, WhatsApp, TeamViewer, or Slack make use of custom protocols.

Sites may test for support for these protocols in a browser and use the information for fingerprinting.

A demo site has been created that checks if the custom protocol handlers of 24 applications are supported (on Windows). A total of 32 different application protocol handlers are supported right now.

The identification works across operating systems and browsers. It can be used, at least in theory, to identify a user based on the results of the test alone.

Let's take the case of Zoom: the videoconferencing application configures and uses the URL zoommtg://. If you click on the browser side on an address starting with this prefix, Zoom will open immediately and automatically.

I chose Zoom because it was recently brought to attention in this very thread.
With Skype it's the same:

https://github.com/fingerprintjs/external-protocol-flooding

Quote

To check if an application is installed, browsers can use built-in custom URL scheme handlers. You can see this feature in action by entering skype:// in your browser address bar. If you have Skype installed, your browser will open a confirmation dialog that asks if you want to launch it. This feature is also known as deep linking and is widely used on mobile devices, but is available within desktop browsers as well. Any application that you install can register its own scheme to allow other apps to open it.

To make this vulnerability possible, the following steps are required:

Prepare a list of application URL schemes that you want to test. The list may depend on your goals, for example, if you want to check if some industry or interest-specific applications are installed.

Add a script on a website that will test each application from your list. The script will return an ordered array of boolean values. Each boolean value is true if the application is installed or false if it is not.

Use this array to generate a permanent cross-browser identifier.

Optionally, use machine learning algorithms to guess your website visitors’ occupation, interests, and age using installed application data.

The actual implementation of the exploit varies by browser, however the basic concept is the same. It works by asking the browser to show a confirmation dialog in a popup window. Then the JavaScript code can detect if a popup has just been opened and detect the presence of an application based on that.

If the mechanism is based on javascripts it is obvious that the control of the scripts allows to put it out of play:thumbup

Martin also writes what I have already written:

Quote

As far as protection in the meantime is concerned, a script-blocker may prevent the attack from being carried out in the first place.

P.S.

If we reduce the surface of attack, proportionally we will have less possibility of attack on the privacy or security side.

The contraindication is of course the lack of functionality.

Edited by Sampei.Nihira
Link to comment
Share on other sites


I'm seeing this "identifier" as USELESS.

Here's why - isn't an "identifier" supposed to be able to IDENTIFY?

Then why did I get 92.35% earlier this morning and now I'm at 91.87%?

Easy, because OTHER PEOPLE are getting the same EXACT "identifier" as I am getting!

Namely, "0FVVVV".

And I got that "0FVVVV" in two different browser (BNav and 360Chrome).

spacer.png

Edited by ArcticFoxie
Link to comment
Share on other sites

It's not that simple as it may seem . This should bother you much more . Have you ever heard about IPT ? It's your unique ID that is generated by all Intel (maybe AMD too) CPUs. I'm not sure about the exact year of it's implementation , but a quick searh reveals that it was there in 2014 already.

From Intel's wevsite:

"Intel Identity Protection Technology is a built-in security token technology that helps a hardware-based proof of a unique user’s PC to websites, financial institutions, and network services; " .

Take this one , for example . It's more than a 6 y.o. old basic/cheap mobile CPU from 2015 and it has this "technology" built in.

https://ark.intel.com/content/www/us/en/ark/products/89611/intel-pentium-processor-4405u-2m-cache-2-10-ghz.html

It was available in earlier models too , starting from 2013-2014 (at least).

 Found this one article from 2014 :

"this token is built right into the device hardware, it is much more convenient " , funny , huh ? "convenient" for them , right.

https://www.askwoody.com/forums/topic/intel-identity-protection-technology/

Outright privacy invasion , a very powerful hardware based tracking tool! But no info anywhere ! Amazing.

Link to comment
Share on other sites

On 5/14/2021 at 2:16 PM, Sampei.Nihira said:

P.S.

If we reduce the surface of attack, proportionally we will have less possibility of attack on the privacy or security side.

The contraindication is of course the lack of functionality.

Basically: this is me, my system is heavily crippled for the sake of (so called) privacy/security. I guess we do what we can so we can still enjoy the experience (as you say ... proportionally) , otherwise, whats the point?

 

On 5/14/2021 at 4:14 PM, Dixel said:

It's not that simple as it may seem . This should bother you much more . Have you ever heard about IPT ? It's your unique ID that is generated by all Intel (maybe AMD too) CPUs. I'm not sure about the exact year of it's implementation , but a quick searh reveals that it was there in 2014 already.

From Intel's wevsite:

"Intel Identity Protection Technology is a built-in security token technology that helps a hardware-based proof of a unique user’s PC to websites, financial institutions, and network services; " .

Take this one , for example . It's more than a 6 y.o. old basic/cheap mobile CPU from 2015 and it has this "technology" built in.

https://ark.intel.com/content/www/us/en/ark/products/89611/intel-pentium-processor-4405u-2m-cache-2-10-ghz.html

It was available in earlier models too , starting from 2013-2014 (at least).

 Found this one article from 2014 :

"this token is built right into the device hardware, it is much more convenient " , funny , huh ? "convenient" for them , right.

https://www.askwoody.com/forums/topic/intel-identity-protection-technology/

Outright privacy invasion , a very powerful hardware based tracking tool! But no info anywhere ! Amazing.

Thank you for sharing this info; Dixel ... I didn't know that, but it doesn't surprise me.

 

Well if "they" are tracking (little old) me (mister blobfish) they must be very very bored lol. Geez Louise ... they would fall asleep if they went through my computer :D

Link to comment
Share on other sites

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210515-e29e57e-uxp-e98338935-xpmod.7z
Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210515-e29e57e-uxp-e98338935-xpmod.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom

IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210515-e29e57e-uxp-e98338935-xpmod-ia32.7z

source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32

NM28XP build:
Win32 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210515-2ad022d8c-uxp-e98338935-xpmod.7z
Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210515-2ad022d8c-uxp-e98338935-xpmod-sse.7z
Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210515-2ad022d8c-uxp-e98338935-xpmod.7z

Official UXP changes since my last build:
- Issue #1751 -- Remove cocoa support code from /dom (ca35efb84)
- Issue #1751 -- Remove cocoa and uikit widget support code (08da125d9)
- Issue #1751 -- Update crashtests (b5ece9f77)
- Issue #1751 -- Remove cocoa and uikit gfx and hal support code (1ee35eafa)
- Issue #1770 - Fix incorrect reference to event parameter (5c583e905)
- Merge pull request 'Fix undefined event error thrown when scrolling on the auto scroll pop-up' (#1771) from FranklinDM/UXP:scroll-wheel-event-work into master (2b7197465)
- [network] Fix typo in port blocking range check. (e98338935)

No official Basilisk changes since my last build.

Official Pale-Moon changes since my last build:
- Issue #1865 - Remove mac-specific resources (2e3103d23)
- Back-end branch pointer update. (2ad022d8c)

Edited by roytam1
Link to comment
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20210515-355db4de-uxp-e98338935-xpmod.7z
BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20210515-355db4de-uxp-e98338935-xpmod.7z

source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older

* Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15.

--

New build of HBL-UXP for XP!

Test binary:
IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20210515-id-f0915f3-uxp-e98338935-xpmod.7z
IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20210515-id-f0915f3-ia-c642e3c-uxp-e98338935-xpmod.7z

source repo (excluding UXP):
https://github.com/roytam1/icedove-uxp/tree/winbuild
https://github.com/roytam1/iceape-uxp/tree/winbuild

for UXP changes please see above.

Link to comment
Share on other sites

New NewMoon 27 Build!

32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210515-963b86a51-xpmod.7z
32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210515-963b86a51-xpmod-sse.7z
32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210515-963b86a51-xpmod-ia32.7z

64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210515-963b86a51-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1158442 - Remove the "Performance Entry buffer size maximum reached" warning; r=baku (98065e0a3)
 - Bug 1164552 - create new colors in light/dark themes for devtools specifically for rendering graphs in the performance tool. The highlight-* colors in light theme work well for text, less so for rendered blocks and appear very 'bold'. Most of the dark theme graph colors are the same as their highlight-* equivilents. r=vp (a5f33fb22)
 - Bug 1158731 - Buffer for Performance APIs (Resource Timing, User Timing) should be separeted. r=baku (87d4be360)
 - Bug 1166494 - Re-add console timestamp and style markers' metadata. r=vp (24c989240)
 - Bug 1166494 - part2: correctly add labels to console markers and properly add style markers' restyleHints. r=vp (ecf87cff4)
 - Bug 1166494 - part3: Correctly handle marker definition fields that are described via function rather than array. r=vp (b71b8575f)
 - Bug 1162662 - Map JS markers to human readable keys, and hide if platform related via (Gecko). r=vp (7526bec84)
 - Bug 1167006 - Refactor marker details to not handle stack traces explicitly, and move logic into marker utils. Separate out some source link styles. r=vp (5b69886a7)
 - remove rough hack, shall be introduced later clean witha round like TFF or proper clamping/jittering as with FF 1443943 (91a202517)
 - Bug 1155761 - User Timing API in Workers, r=ehsan (0b7d3fe7d) (3517c9d90)
- import changes from mozilla upstream:
 - Bug 1167489 and bug 1153672 - Clamp the resolution of performance.now() calls to 5us, because otherwise we allow various timing attacks that depend on high accuracy timers. r=froydnj, a=abillings (aeab359c2)
 - Bug 1186489.  Apply the performance.now() resolution clamping in workers as well.  r=froydnj (e56bc3c9a) and changed to 20us as bug 1427870 suggested. (cbb05a977)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1168411 - Disable test_sharedWorker_performance_user_timing.html on B2G debug for intermittent failures. r=RyanVM (844f2ecd9)
 - Bug 916893 - Patch 1 - Notification on workers. r=khuey,wchen (058a84ae1)
 - Bug 916893 - Patch 2 - Deal with onclose. Some grammar fixes. r=wchen (19cf84c5a)
 - Bug 916893 - Patch 3 - Walk up worker chain to find correct window for WorkerNotificationObserver. r=khuey (ee1f0c3fc)
 - Bug 1190176 - Make LayerScopeWebSocketManager thread safe. r=:djg (92c5ee233)
 - Bug 1196682 - DebugDataSender is not thread safe. r=kamidphish (6825e5d9b)
 - Bug 1196682 - fixup static analysis build bustage on a CLOSED TREE; r=me (eccf7b0cc) (2d7e3ad42)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1175138 P1 Make the dom.caches.testing.enabled pref available in workers. r=ehsan (fe47d0e0a)
 - Bug 1175138 P2 Expose dom.serviceWorkers.testing.enabled to workers. r=ehsan (efab5d0d3)
 - Bug 1160458 - Part 1: Use the CSP of the principal passed to CreateServiceWorker. r=nsm (4d0a1d742)
 - Bug 1172948 - Part 3: Add an explicit test case to ensure that authenticated origins that have a non-authenticated parent cannot register a service worker; r=nsm (78b3087c9)
 - Bug 803537 - XHR crashes in workers and in debug-builds when blob URLs are used from file scheme documents, r=khuey (aa86f77b7)
 - Bug 1163900 - crash in mozilla::net::nsHttpChannelCacheKey::GetData(unsigned int*, nsACString_internal&), r=jduell (adb5ddb01)
 - Bug 1147746 - Null check mInterceptListener in HttpChannelChild::ResetInterception; r=jdm (4c8c4e630)
 - Bug 1157283 - Recreate IPC redirected HTTP channels as necessary after intercepting the request in the child. r=mayhemer (3b144e45e)
 - Bug 1172884 P1 Properly decode body when intercepted response redirects. r=jduell (f49c37d4f)
 - Bug 1172884 P2 Add test for synthesizing a redirect to a compressed resource. r=ehsan (823d2122a)
 - Bug 1160458 - Part 2: Test. r=nsm (02b9fb3a0)
 - Bug 1169249 - Unregister service worker registration when uninstalling a service-worker-enabled application. Tests. r=baku (5509a19d6)
 - Bug 1177621 - SharedWorkers should not be shared between a private and a non-private documents, r=nsm (0836234c7)
 - Bug 1175138 P3 Expose the devtools SW testing flag on workers. r=ehsan (aade20454)
 - Bug 1173467 P3 Pass private browsing flag into CacheStorage factory methods. r=ehsan (c4d062a80)
 - Bug 1173467 P4 Add a test to validate Cache in private browsing window. r=ehsan (dde897e69)
 - Bug 1162487 - Enable the dom.caches.enabled pref in test_chrome_constructor.html; r=baku (2c73e2929)
 - Bug 1175138 P4 Enable dom.caches.testing.enabled in existing tests. r=ehsan (c453e03fb)
 - Bug 1175138 P5 Make CacheStorage reject on untrusted origins. r=ehsan (c85424d4e)
 - Bug 1175138 P6 Add a simple test to verify CacheStorage rejects in http origin. r=ehsan (5832eb99d)
 - Bug 1179567 - Make ServiceWorker keep its document and window alive; r=baku (1ae847884)
 - Bug 1179982 - Fix all compile errors in dom/workers on non-unified build. r=mrbkap (d30bece64) (963b86a51)

Link to comment
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rthost.win/kmeleon/KM76.4.3-Goanna-20210515.7z

Changelog:

Out-of-tree changes:
* update Goanna3 to git 32a8a4473...963b86a51:
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1158442 - Remove the "Performance Entry buffer size maximum reached" warning; r=baku (98065e0a3)
 - Bug 1164552 - create new colors in light/dark themes for devtools specifically for rendering graphs in the performance tool. The highlight-* colors in light theme work well for text, less so for rendered blocks and appear very 'bold'. Most of the dark theme graph colors are the same as their highlight-* equivilents. r=vp (a5f33fb22)
 - Bug 1158731 - Buffer for Performance APIs (Resource Timing, User Timing) should be separeted. r=baku (87d4be360)
 - Bug 1166494 - Re-add console timestamp and style markers' metadata. r=vp (24c989240)
 - Bug 1166494 - part2: correctly add labels to console markers and properly add style markers' restyleHints. r=vp (ecf87cff4)
 - Bug 1166494 - part3: Correctly handle marker definition fields that are described via function rather than array. r=vp (b71b8575f)
 - Bug 1162662 - Map JS markers to human readable keys, and hide if platform related via (Gecko). r=vp (7526bec84)
 - Bug 1167006 - Refactor marker details to not handle stack traces explicitly, and move logic into marker utils. Separate out some source link styles. r=vp (5b69886a7)
 - remove rough hack, shall be introduced later clean witha round like TFF or proper clamping/jittering as with FF 1443943 (91a202517)
 - Bug 1155761 - User Timing API in Workers, r=ehsan (0b7d3fe7d) (3517c9d90)
- import changes from mozilla upstream:
 - Bug 1167489 and bug 1153672 - Clamp the resolution of performance.now() calls to 5us, because otherwise we allow various timing attacks that depend on high accuracy timers. r=froydnj, a=abillings (aeab359c2)
 - Bug 1186489.  Apply the performance.now() resolution clamping in workers as well.  r=froydnj (e56bc3c9a) and changed to 20us as bug 1427870 suggested. (cbb05a977)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1168411 - Disable test_sharedWorker_performance_user_timing.html on B2G debug for intermittent failures. r=RyanVM (844f2ecd9)
 - Bug 916893 - Patch 1 - Notification on workers. r=khuey,wchen (058a84ae1)
 - Bug 916893 - Patch 2 - Deal with onclose. Some grammar fixes. r=wchen (19cf84c5a)
 - Bug 916893 - Patch 3 - Walk up worker chain to find correct window for WorkerNotificationObserver. r=khuey (ee1f0c3fc)
 - Bug 1190176 - Make LayerScopeWebSocketManager thread safe. r=:djg (92c5ee233)
 - Bug 1196682 - DebugDataSender is not thread safe. r=kamidphish (6825e5d9b)
 - Bug 1196682 - fixup static analysis build bustage on a CLOSED TREE; r=me (eccf7b0cc) (2d7e3ad42)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1175138 P1 Make the dom.caches.testing.enabled pref available in workers. r=ehsan (fe47d0e0a)
 - Bug 1175138 P2 Expose dom.serviceWorkers.testing.enabled to workers. r=ehsan (efab5d0d3)
 - Bug 1160458 - Part 1: Use the CSP of the principal passed to CreateServiceWorker. r=nsm (4d0a1d742)
 - Bug 1172948 - Part 3: Add an explicit test case to ensure that authenticated origins that have a non-authenticated parent cannot register a service worker; r=nsm (78b3087c9)
 - Bug 803537 - XHR crashes in workers and in debug-builds when blob URLs are used from file scheme documents, r=khuey (aa86f77b7)
 - Bug 1163900 - crash in mozilla::net::nsHttpChannelCacheKey::GetData(unsigned int*, nsACString_internal&), r=jduell (adb5ddb01)
 - Bug 1147746 - Null check mInterceptListener in HttpChannelChild::ResetInterception; r=jdm (4c8c4e630)
 - Bug 1157283 - Recreate IPC redirected HTTP channels as necessary after intercepting the request in the child. r=mayhemer (3b144e45e)
 - Bug 1172884 P1 Properly decode body when intercepted response redirects. r=jduell (f49c37d4f)
 - Bug 1172884 P2 Add test for synthesizing a redirect to a compressed resource. r=ehsan (823d2122a)
 - Bug 1160458 - Part 2: Test. r=nsm (02b9fb3a0)
 - Bug 1169249 - Unregister service worker registration when uninstalling a service-worker-enabled application. Tests. r=baku (5509a19d6)
 - Bug 1177621 - SharedWorkers should not be shared between a private and a non-private documents, r=nsm (0836234c7)
 - Bug 1175138 P3 Expose the devtools SW testing flag on workers. r=ehsan (aade20454)
 - Bug 1173467 P3 Pass private browsing flag into CacheStorage factory methods. r=ehsan (c4d062a80)
 - Bug 1173467 P4 Add a test to validate Cache in private browsing window. r=ehsan (dde897e69)
 - Bug 1162487 - Enable the dom.caches.enabled pref in test_chrome_constructor.html; r=baku (2c73e2929)
 - Bug 1175138 P4 Enable dom.caches.testing.enabled in existing tests. r=ehsan (c453e03fb)
 - Bug 1175138 P5 Make CacheStorage reject on untrusted origins. r=ehsan (c85424d4e)
 - Bug 1175138 P6 Add a simple test to verify CacheStorage rejects in http origin. r=ehsan (5832eb99d)
 - Bug 1179567 - Make ServiceWorker keep its document and window alive; r=baku (1ae847884)
 - Bug 1179982 - Fix all compile errors in dom/workers on non-unified build. r=mrbkap (d30bece64) (963b86a51)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

Link to comment
Share on other sites

Is it normal that the Palemoon 28 interface becomes unresponsive while executing high CPU JavaScript on single core? Often I encounter a heavy webpage and want to press the stop button or close the tab, but cannot do that until the page has finished running its code. Then sometimes I close multiple tabs or the entire window once it starts accepting input. I also generally feel that the browser milks every bit of system power to itself with other programs feeling sluggish during a full speed file download over SSL. Lately I started running it at /belownornal priority, but that doesn't address the unresponsive GUI.

I "upgraded" from Opera and Firefox 27 which felt better, compatibility aside.

Link to comment
Share on other sites

30 minutes ago, j7n said:

Is it normal that the Palemoon 28 interface becomes unresponsive . . .

That was my experience, yes!

v28 became my default-for-everything soon after its "sneak peek" version was released in May 2018.

To me, v28 became increasingly sluggish soon after version 28.2.2 (official numbering, Roytam's equivalent was 28.1.0a1.win32-git-20180922).

At that time, I "upgraded" to v27 and found its performance much better than v28.

I never really researched at the time "why" v28 became so sluggish.

Link to comment
Share on other sites

9 hours ago, Dixel said:

Have you ever heard about IPT ? It's your unique ID that is generated by all Intel (maybe AMD too) CPUs. I'm not sure about the exact year of it's implementation , but a quick searh reveals that it was there in 2014 already.

From Intel's wevsite:

"Intel Identity Protection Technology is a built-in security token technology that helps a hardware-based proof of a unique user’s PC to websites, financial institutions, and network services; " .

9 hours ago, Dixel said:

It was available in earlier models too , starting from 2013-2014 (at least).

It was available first time, actually, in Pentium 3, but that was pre-9\11 world and this did not fly well and was quickly strike down by EU.

https://en.wikipedia.org/wiki/Pentium_III#Controversy_about_privacy_issues

 

Quote

On November 29, 1999, the Science and Technology Options Assessment (STOA) Panel of the European Parliament, following their report on electronic surveillance techniques asked parliamentary committee members to consider legal measures that would "prevent these chips from being installed in the computers of European citizens.

Intel eventually removed the PSN feature from Tualatin-based Pentium IIIs, and the feature was absent in Pentium 4 and Pentium M.

A largely equivalent feature, the Protected Processor Identification Number (PPIN) was later added to x86 CPUs with little public notice, starting with Intel's Ivy Bridge architecture and compatible Zen 2 AMD CPUs. It is implemented as a set of model-specific registers and is useful for machine check exception handling.

After 9\11 right-wingers rig the world and you all should comply and be obedient slave citizen or nine-eleven will happen again.

P.S. I long time want to ask, will roytam adapt 29 version of PM? They promise "Google WebComponent" support on they release notes with 29... Maybe this question was asked before, but i never see it. So what will be with 29 for XP?

Edited by Rod Steel
Link to comment
Share on other sites

13 hours ago, Dixel said:

It's not that simple as it may seem . This should bother you much more . Have you ever heard about IPT ? It's your unique ID that is generated by all Intel (maybe AMD too) CPUs. I'm not sure about the exact year of it's implementation , but a quick searh reveals that it was there in 2014 already.

From Intel's wevsite:

"Intel Identity Protection Technology is a built-in security token technology that helps a hardware-based proof of a unique user’s PC to websites, financial institutions, and network services; " .

Take this one , for example . It's more than a 6 y.o. old basic/cheap mobile CPU from 2015 and it has this "technology" built in.

https://ark.intel.com/content/www/us/en/ark/products/89611/intel-pentium-processor-4405u-2m-cache-2-10-ghz.html

It was available in earlier models too , starting from 2013-2014 (at least).

 Found this one article from 2014 :

"this token is built right into the device hardware, it is much more convenient " , funny , huh ? "convenient" for them , right.

https://www.askwoody.com/forums/topic/intel-identity-protection-technology/

Outright privacy invasion , a very powerful hardware based tracking tool! But no info anywhere ! Amazing.

There is an old thread about this on the Pale Moon forum:

https://forum.palemoon.org/viewtopic.php?t=14617

The technology involved a NPAPI plugin that could be set to "Never activate".

Link to comment
Share on other sites

roytam1, please remove the limitation 4K texture for hardware acceleration. This can return hardware acceleration for Radeon 9500 - X1250 and Intel GMA900 - 3150 graphics cards

https://bugzilla.mozilla.org/show_bug.cgi?id=637089

 

And add opengl32.dll file for SSE2 + ,  that it would be possible to enable software WebGL on computers with a bad video card https://bugzilla.mozilla.org/show_bug.cgi?id=1193695

https://download.qt.io/development_releases/prebuilt/llvmpipe/windows/

(25-Sep-2014) and rename opengl32sw.dll

 

Edited by grey_rat
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...