Jump to content

trium

Experienced Members
 View Profile  See their activity

  • Posts

    2,544

  • Joined

  • Last visited

 Content Type 

Posts posted by trium

    Can I upgrade my i3 processor to an i5 or i7

    in Hardware

    Posted

    the same class, processor heat, bios support, power supply...

    for example:

    (mobile 5th generation)

    i3-5020U - 2 cores - 2,2 GHz basespeed, 3MB Cache with 15 Watt TDP down to 10 Watt

    i5-5300U - 2 cores - 2,3 GHz basespeed, 3MB Cache with 15 Watt TDP down to 7,5 Watt

     

    (mobile 8th generation)

    i3-8130U - 2 cores - 2,2 GHz basespeed, 4MB Cache with 15 Watt TDP down to 10 Watt

    i5-8279U - 4 cores - 2,4 GHz basespeed, 6MB Cache with 28 Watt TDP

    i5-8269U - 4 cores - 2,6 GHz basespeed, 6MB Cache with 28 Watt TDP down to 20 Watt

    or i7-8550U - 4 cores - 1,8 GHz basespeed, 8MB Cache with 25 Watt TDP down to 10 Watt

     

    Can I upgrade my i3 processor to an i5 or i7

    in Hardware

    Posted

    https://www.intel.com/content/www/us/en/support/articles/000005682/processors.html

     

    Intel Desktop Processor Upgade Information

    If you would like to upgrade your processor to a new generation Intel® Core™, compare Celeron® or Pentium® processors, or compare different processor families, you can watch the video Finding Information on Intel Processors or review the steps in How to Compare Intel® Processors Using Product Specifications Page (ARK).

    Contact your system or motherboard manufacturer before upgrading your desktop processor. Your manufacturer is familiar with your system specifications and the different upgrade options available, and they can tell you which processors your system or motherboard supports.

    Even if your processor and motherboard socket match, it's critical to make sure that your motherboard BIOS supports your new processor. Older motherboards frequently don't have BIOS support for newer processors. Lack of BIOS support for your processor can cause the system to not boot or display erratic behavior.

    Another upgrade consideration is that faster processors, and processors with more cores, can also affect the temperature of your system. You need to make sure your chassis and thermal solution work with your upgrade from a thermal perspective.

    One way to verify processor compatibility is to use the Intel® Desktop Compatibility Tool and search by processors or motherboards.

    For more information on your Intel® Processor or Intel® Desktop Board, select one of the links below:

    Intel® Desktop Processor Resources
    Compare Intel Desktop Processors Use comparison chart to compare desktop processors and features.
    Intel Desktop Processor support resources This document has useful links to installation videos, integration documents, and warranty information.
    Find compatible motherboards for Intel® Desktop Processors Use this tool to enter your Intel desktop processor to find compatible motherboards.
    Intel® Processor Identification Utility The utility identifies your processor and if it's working at the correct frequency.
    Intel Product Information This resource shows detailed specifications for all Intel products.

    where is the pear? v5.69

    in CCleaner

    Posted

    On 02/08/2020 at 13:54, Dave CCleaner said:

    For paid users it will show their expiry status

     

    perhaps there can be a script to display the pear again -> for free users  -no need to show expire date but good to bring back the pear :-)

    ublock users

    in Software

    Posted

    ublock v1.29.0

    gorhill released this

    13 days ago

    Closed as fixed:

    Chromium

    Firefox

    Core

    Notable commits with no entry in issue tracker:

    The Firefox/Mozilla Thread

    in Software

    Posted

    ff v68.11.0 esr

    28. july 2020

    Fixed

     

    Quote

     

    Security Vulnerabilities fixed in Firefox ESR 68.11

    Announced July 28, 2020
    Impact high
    Products Firefox ESR
    Fixed in
    • Firefox ESR 68.11

    #CVE-2020-15652: Potential leak of redirect targets when loading scripts in a worker

    Reporter Mikhail Oblozhikhin
    Impact high
    Description

    By observing the stack trace for JavaScript errors in web workers, it was possible to leak the result of a cross-origin redirect. This applied only to content that can be parsed as script.

    References

    #CVE-2020-6514: WebRTC data channel leaks internal address to peer

    Reporter Natalie Silvanovich of Google Project Zero
    Impact high
    Description

    WebRTC used the memory address of a class instance as a connection identifier. Unfortunately, this value is often transmitted to the peer, which allows bypassing ASLR.

    References

    #CVE-2020-6463: Use-after-free in ANGLE gl::Texture::onUnbindAsSamplerTexture

    Reporter Reported by Pawel Wylecial of REDTEAM.PL
    Impact moderate
    Description

    Crafted media files could lead to a race in texture caches, resulting in a use-after-free, memory corruption, and a potentially exploitable crash.

    References

    #CVE-2020-15650: Overwriting local files through malicious file picker application

    Reporter Pedro Oliveira
    Impact moderate
    Description

    Given an installed malicious file picker application, an attacker was able to overwrite local files and thus overwrite Firefox settings (but not access the previous profile).
    Note: This issue only affected Firefox for Android. Other operating systems are unaffected.

    References

    #CVE-2020-15649: Exfiltrating local files through malicious file picker application

    Reporter Pedro Oliveira
    Impact moderate
    Description

    Given an installed malicious file picker application, an attacker was able to steal and upload local files of their choosing, regardless of the actually files picked.
    Note: This issue only affected Firefox for Android. Other operating systems are unaffected.

    References

    #CVE-2020-15659: Memory safety bugs fixed in Firefox 79 and Firefox ESR 68.11

    Reporter Mozilla developers
    Impact high
    Description

    Mozilla developers Jason Kratzer and Luke Wagner reported memory safety bugs present in Firefox 78 and Firefox ESR 68.10. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

    References

     

    The Firefox/Mozilla Thread

    in Software

    Posted

    ff v79.0

    28. july 2020

    New

    • We’ve rolled out WebRender to more Windows users with Intel and AMD GPUs, bringing improved graphics performance to an even larger audience.

    • Firefox users in Germany will now see more Pocket recommendations in their new tab featuring some of the best stories on the web. If you don’t see them, you can turn on Pocket articles in your new tab by following these steps.

     

    Fixed

    • Various security fixes.

    • Several crashes while using a screen reader were fixed, including a frequently encountered crash when using the JAWS screen reader.

    • Firefox Developer Tools received significant fixes allowing screen reader users to benefit from some of the tools that were previously inaccessible.

    • SVG title and desc elements (labels and descriptions) are now correctly exposed to assistive technology products such as screen readers.

     

    Enterprise

    • A number of bug fixes and new policies have been implemented in the latest version of Firefox. You can see more details in the Firefox for Enterprise 79 Release Notes.

    • Updates to the password policy allow admins to require a primary password (formerly called master password. Previously the policy could disable the primary password but not force a primary password. Users required to use a primary password will only be asked to create a primary password the first time they try to save a password.

     

    Developer

    Developer Information

    • Newly added asynchronous call stacks let developers trace their async code through events, timeouts, and promises. The async execution chains are shown in the Debugger’s call stack, but also for stack traces in Console errors and Network initiators.

    • Erroneous network responses with 4xx/5xx status codes display as errors in the Console, making it easy to understand them in the context of related logs. The request/response details can be expanded or resent for quick debugging.

    • JavaScript errors are now visible not only in the Console, but also in the Debugger. The relevant line of code will be highlighted and display error details on hover.

    • Opening SCSS and CSS-in-JS sources from the Inspector now works more reliably thanks to improved source map handling across all panels.

    • Inspecting accessibility properties from the browser context menu is now available to all users by default.

    ublock users

    in Software

    ublock users

    in Software

    ublock users

    in Software

    Posted

    ublock v1.28.2

    gorhill released this

    Jul 11, 2020

    Changes:

    Both stock malware domain lists, which are enabled by default in uBO, have been replaced by URLhaus Malicious URL blocklist, which is now enabled by default in uBO.

    For existing installations, both removed malware lists will be moved to the Custom section if you still have them enabled. It is recommended you remove these lists from your Custom lists -- only you can do this, uBO does not remove lists which are currently enabled. It may take a few days before you are updated with the new default stock lists.

    Closed as fixed:

    ublock users

    in Software

    Posted

    firefox legacy v1.16.4.21

    gorhill released this

    Jun 20, 2020

    ublock users

    in Software

    Posted

    ublock v1.28.0

    gorhill released this

    Jun 30, 2020

    Changes:

    ##script:inject(...), which has been deprecated in favor of ##+js(...) for more than two years, is no longer supported.

    It's no longer possible to point-and-click to create allow (green) rules from within the popup panel by default. This change is motivated by seeing way too many cases of improper usage of dynamic filtering in which users are creating allow (green) rules where noop (gray) rules should have been used. You can get back temporarily the ability to create allow rules from within the popup panel by tapping twice the Ctrl key.

    Improved syntax highlighting of static filters in "My filters" and asset viewer. Additionally, in "My filters":

    • Ability to toggle commenting out of filter(s) by pressing the Tab key
    • Auto-completion using Ctrl-Space, this works for:
      • Static filter options
      • Resource names for redirect= option
      • Procedural operators for cosmetic/HTML filters
      • Scriptlet names for ##+js filters

    Closed as fixed:

    Chromium 65

    Chromium

    Core

    Notable commits with no entry in issue tracker:

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept