Jump to content

mixit

Member
  • Posts

    161
  • Joined

  • Days Won

    9
  • Donations

    $0.00 

Everything posted by mixit

  1. My observations : Your browser version doesn't really matter, all you need to get "You're protected" is somehow blocking coinhive.com and coin-hive.com. This can be done in any browser by running a regular adblocker like uBlock Origin, etc., I don't see much need for specialized addons. While raising awareness is commendable in itself, the cryptojackingtest.com site seems to be more about advertising Opera (specifically its built-in adblocker) than serious testing for cryptojacking protection. In my opinion, actually mining cryptocurrency on the site (instead of just checking if it could be done) is a pretty questionable move, even if they claim to donate the proceeds. Edit: If Opera were the ones behind this site, I don't see why they'd register this domain anonymously - this is starting to look like a clever ruse to use people to mine a bit under the guise of an awareness campaign. Apparently the site is referenced in Opera's official blog so it should be legit. It's still weird that they'd use a domain privacy service instead of registering the domain with their official contact information.
  2. @ThomasW Without knowing the exact details of what has been changed in the browser, it's hard to say with 100% certainty that these fixes won't slow anything down. However, it seems very unlikely based on the overview given by Mozilla. Don't let the common word "time" confuse you, reducing the precision of time sources should in no way affect site loading times; and it's hard to imagine any legitimate scripts used by social media sites needing microsecond precision for anything, so they should be unaffected as well. As @Bersaglio said, don't worry about it (least of all on XP, which hasn't received slowdown-causing OS-level mitigations). Besides, ESR means no feature changes, so even in the very unlikely case of there being slowdowns, you can always go back to the previous point release without the risk of messing up your profile.
  3. (Apologies for the slew of quotes, I wanted to get the full context.) It sure would be nice to have a list like that for Meltdown/Spectre, but unfortunately the fact that a CPU is on this list doesn't mean that it's vulnerable to them, just that it has had a microcode update released for it. If you scroll down the downloadcenter.intel.com page and look at Other Versions on the left-hand side, you'll see that there have been many previous microcode releases dating from years before anyone knew about these vulnerabilities, It's a cumulative release and the list you posted simply reflects that, most of the updates included in it are from years ago. As you correctly stated in the end, only the more recent CPUs will be patched for these particular vulnerabilities. EDIT: Just to be clear, I'm not getting on your case or anything. I myself also misunderstood at first what the list actually meant, because I was first directed to it from a site that flat out claimed this was a list specifically for Meltdown/Spectre...
  4. They are not Meltdown+Spectre patches - as things stand right now, those won't be coming to XP-based OSes at all. KB4056615 has seen some pretty serious issues that have been reported here (they don't happen to all installations - I personally have encountered no problems so far) , I haven't noticed any reports about problems with KB4056941 specifically. EDIT: Unrelated, but important for Office 2000/XP/2003 users:
  5. With the latest patches out this Tuesday, Microsoft has completely removed Equation Editor from all still supported Office versions, so it's a very good idea to also remove it from older Office versions ASAP. See the updated opening post for details.
  6. "An elevation of privilege vulnerability exists in the way that the Windows Kernel API enforces permissions." (marked as Important, but Exploitation Less Likely). Doesn't sound very Meltdownish to me. For whatever reason, they decided to release a whole bunch of Windows OS patches early. Take a look at the Server 2008 updates for instance, clearly things like Microsoft Color Management information disclosure vulnerability aren't related to Meltdown.
  7. Time to stop worrying and love the bomb...? From Microsoft's official guidance Protect your Windows devices against Spectre and Meltdown (expand "My operating system (OS) is not listed. When can I expect a fix to be released?") (emphases in the quote added by me): I think this should also settle the confusion some people seem to have over whether KB4056615 was supposed to be a Meltdown fix: it wasn't.
  8. I know what you mean, but until Intel can be bothered to make a definitive itemized list of all processors these problems apply to, 99.9% of the people are going to think Core 2 Duos are included in this, because people aren't going know that "2nd generation Intel® Core™ processors" are supposed to be the same i3/5/7 processors that were already mentioned before (that is, unless Intel has now started reinterpreting the meanings of their own jargon). They just see the word "Core" and assume that they're probably affected, especially with all the vague claims being circulated in the media about all x64 processors being affected, etc.
  9. The quote was by the program author on the same page you got that image from, so I don't really understand what you mean by that "should". It wasn't me making claims about what the message meant.
  10. SpecuCheck (link was in the post you quoted ).
  11. This is a deliberately tweaked test image for a bug in Chromium's PNGImageDecoder, that doesn't mean it's malicious. Even if it were malicious, CVE-2013-2977 applies to IBM Notes which you're unlikely to have installed. In other words, don't worry about it.
  12. @Dave-H, @SD73 While I was was being cautious about suggesting /overwriteoem above, I think that if you guys have been applying POSReady updates so far without these kinds of "OEM driver" issues, it should be pretty safe to use it in this case. There have been a number of kernel updates already, so if all of those got applied on your systems without problems, it's rather unlikely that your current kernel files could still be OEM versions of some sort, so forcing the overwrite shouldn't be a problem. (I'd be more cautious if this were the first kernel update you've ever applied.) I'd still feel more comfortable if I knew what actually causes this strange issue to begin with - my personal policy is not to suggest things to people unless I can be sufficiently certain they won't cause problems, and in this case the situation is somewhat vague.
  13. Check C:\WINDOWS\KB4056615.log. If it contains messages like c:\windows\system32\ntoskrnl.exe is in the list of oem drivers...skipping copy! c:\windows\system32\ntkrnlpa.exe is in the list of oem drivers...skipping copy! you can try running the KB .exe file with the /overwriteoem switch. This could have unwanted consequences, so only try it if you have everything backed up and feel confident you are capable of recovering your system if there are problems! I've never used this switch on a physical installation (because I've never had this issue occur), only for kernel updates in the VirtualBox VM I use for POSReady updates testing before applying them on my actual PC. While I haven't seen any problems resulting in the VM, that doesn't necessarily mean this is always safe. So, please don't take this as the recommended course of action, just something you can try if you're feeling adventurous.
  14. At this point it appears that KB4056615, despite being a kernel update, does not address the Meltdown/Spectre issue. At least neither the official Speculation Control Validation PowerShell script from Microsoft nor Alex Ionescu's SpecuCheck seem to think that it does anything to fix the problem. (To run the PS script on XP, refer to Wolferajd_fur's tip in the Q&A section. For the compiled SpecuCheck executable, you'll have to doctor the minimum OS version in the PE header.) Edit: Of course there's a possibility that these tools themselves don't work properly on XP, but I'd think the syptoms for that would look a bit different. I looked at the Windows 7 Meltdown/Spectre patch (KB4056897), and it updates a huge number of major system components and drivers, not just the kernel and the NTFS driver. It seems we'll have to wait a bit longer to get a fix for XP.
  15. Go to Onepiece XP Post-SP3 AIO Update Pack FINAL at RyanVM. At the bottom of the first post, there is a list of mirrors. Most of the mirrors don't seem to have the original Microsoft issued updates used to build the pack, but currently the Mega.nz mirror (it's the goo.gl link right of the Dropbox one) does have them under the UpdatePack/Portuguese folder. You can probably get the other PTG updates you're still missing from there as well. (I'm not posting a direct link here because such repositories tend to be pretty volatile and I think it's more useful to know where to get the most current links.)
  16. Thanks for the update, @Bersaglio! I edited my post in the other topic to reflect this. Yeah, and fix the mess at the Catalog while you're at it... Not sure why it's necessary to continually attach my name to this feature
  17. Edited the topic to reflect the switch to KB4011604 (thanks for the heads up, @Bersaglio ). FYI, for some reason the KB4011604 Download Center landing page sometimes gives a "no longer available" message, hopefully the direct EXE links are more stable. If you're a more of a Catalog person, I'm sure you'll appreciate the fact that MS has posted all language versions separately, with no indication which is which, so you basically have to click on each download button until you find the right language...
  18. I keep forgetting to mention that I wasn't able to make this problem appear with the latest ESR update and a clean profile, so it likely only manifests in case of some combination of other settings and maybe extensions. Just setting FF to never remember history didn't cause me any problems with manual installation. In any case, thanks for reporting this and hopefully your workaround will work if anyone else should experience something similar.
  19. (This is a generalized version of something I put together to help out a member here. Of course after having written it I found out that @heinoganda has already mentioned most of this earlier in this thread, but at least this is prettier , so I'm still going to post it.) So, you're looking for an older version of Microsoft Security Essentials in your local language (for example version 4.4.304, the last one officially supported on XP) and find out that the web is full of English versions, but it's very difficult to find an installer for the language you want. Fortunately, you can convert an English installer into any other supported language in just a few steps, using 7-zip and a text editor. Any place you see Italian and IT-IT in this example, just replace them with your language from this list: Download the "English" 4.4.304 installer, for example from https://web.archive.org/web/20140325144125if_/http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/ENUS/x86/MSEInstall.exe Right-click MSEInstall.exe > 7-zip > Extract to "MSEInstall" (or wherever you like). Open the folder you extracted it to. Open setup.ini in a text editor, change Market=EN-US into Market=IT-IT. Copy the folder EN-US, paste the copy into the same folder (top folder, not EN-US), rename the copy to IT-IT. (Optional) If you also want to change the installation dialogs from English to Italian: Go into the x86 subfolder, open epp.msi in 7-zip. Right-click product.cab > Open Inside. Locate SetupResDllMui_IT_IT, extract it to the IT-IT folder you created before. Delete the existing setupres.dll.mui, rename SetupResDllMui_IT_IT to setupres.dll.mui . (If you absolutely need an Italian EULA as well, download the latest version of the Italian installer and extract EULA.RTF from its IT-IT folder into your IT-IT folder. Judging by the English EULA, the contents differ slightly between versions, but who really cares about the EULA anyway, right? ) To install MSE, execute epplauncher.exe. (If you want to re-pack your results into a single executable installer, search for sfx in 7-zip help.) Of course none of this would even be necessary if only Microsoft could be bothered to make proper unified installers that automatically launch in the OS language (or, even better, allow selecting the language at program startup). I mean, why not just do this if you have all 33 languages packed into the installer anyway?...
  20. @glnz @dencorso The funny thing is that I don't even like to post references with that box thing (which, as I just discovered, is an iframe - ugh...), but since pasting a post link gets automatically converted to it, I just don't bother to change it every time, as the Link tool in the editor has its own idiosyncracies (at least in my case it forgets the clipboard contents, so I always have to go back and copy my text/URL again after having opened it - pretty annoying ). I really wish we could use BBCode here.
  21. If you have the same Compatibility Pack installed, you can and should apply the same updates on both machines. The system may be 64-bit but Office and the Compatibility Pack would still be 32-bit. Also, what @dencorso already told you:
  22. https://web.archive.org/web/20150922145904/download.microsoft.com/download/A/0/5/A05EF63F-F0FF-4D7F-9441-3BAFCCDED0F0/WindowsXP-KB955704-x86-ITA.exe
  23. Thanks for discovering this! I don't use XP x64, so this obvious-in-hindsight difference never occurred to me. I added this point to the guide.
  24. FYI, since probably not everyone here frequents the Office section and this is not something automatically offered to those of us with Office 2000/XP/2003 with Office 2007 Compatibility Pack:
  25. With the latest patches out this Tuesday, Microsoft has completely removed Equation Editor from all still supported Office versions, so it's a very good idea to also remove it from older Office versions ASAP. I'm guessing this drastic measure has to do with the fact that Microsoft doesn't seem to have the source code for this bundled third-party application, and since it's been under ongoing attack even after the previous binary patch was issued for it, they decided that continuing to patch the binary just wasn't feasible. If your version of Office is still supported, simply apply the latest patches from Microsoft Update (see the CVE link below for manual downloads). For older versions like Office 2000/XP/2003, you can either remove this feature with the Office installer and mark it unavailable (as described below in the If you don't use Equation Editor section), or simply replace the existing EQNEDT32.EXE with a 0-size empty file still called EQNEDT32.EXE (this appears to be what the patches for newer Office versions do). See the following links for more details and Microsoft's suggestions for replacements of Equation Editor functionality. https://support.microsoft.com/en-us/help/4057882/error-when-editing-an-equation-in-office https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0802 This post used to be titled HOWTO: Install Office 2007 Equation Editor security update (KB4011604. aka KB4011276) on Office 2000/XP/2003 and had the following contents: A remote code execution vulnerability was patched this month in Equation Editor, an Office component (CVE-2017-11882 | Microsoft Office Memory Corruption Vulnerability, Description of the security update for 2007 Microsoft Office Suite: November 28, 2017). Official patches are available only for Office 2007 and higher, but since it's a standalone component that hasn't changed since the year 2000, and Microsoft has simply applied a binary patch to the executable and resigned it, you can also use this patch with Office 2000, XP and 2003. NOTE: KB4011604 was initially released as KB4011276 for English and Chinese only. If you've already installed KB4011276, you don't need to install KB4011604, the Equation Editor payloads are byte-for-byte identical. If you prefer a statement from Microsoft (from the CVE link above): "Customers who have already installed the previously-released updates (4011276 or 2553204) do not need to take any further action." If you don't use Equation Editor, instead of updating it, you might want to remove it from your computer altogether. (Even if you don't have it installed right now, since it defaults to Installed on First Use, it's a good idea to explicitly deselect it in the Office installer.) Go to Control Panel > Add or Remove Programs, locate your Office 2000/XP/2003 installer and choose the Change option, then pick Add or Remove Features when the installer launces. Find Equation Editor in the component tree. The exact location may differ depending on your Office version, in my case (Office XP) it was under Office Tools. To disable its installation, or remove it from your computer if already installed, mark it as Not Available and complete the update. You should no longer have an Equation folder under (typically) C:\Program Files\Common Files\Microsoft Shared. If you do use Equation Editor, you'll have to update it manually. (Trying to run the installer, it'll just tell you that you don't have an applicable product installed.) To do this, you'll be needing 7-zip (or a similarly versatile unpacker). Get the patch either as an EXE installer from the Download Center (English; other languages direct links by @Bersaglio) or a CAB file from WU/Catalog (English) . Right-click on the downloaded file and choose to open it with 7-zip. (EXE only) Select [0], right-click, Open Inside. Select eqnedt32-[your-language].msp (e.g. eqnedt32-en-us.msp), right-click, Open Inside. Select PATCH_CAB, right-click, Open Inside. Extract EQNEDT32.EXE_[numeric language code] (e.g. EQNEDT32.EXE_1033) to a location of your choice and remove the numeric part from the file name, leaving you with EQNEDT32.EXE. Copy this file to your Equation Editor folder, (typically) at C:\Program Files\Common Files\Microsoft Shared\Equation, replacing the old EQNEDT32.EXE in there. (If you like, you can make a copy of the old version, but you can always restore it later by re-running the Office installer.) To make sure everything is kosher now, check EQNEDT32.EXE properties. The version should show 2017.8.14.0. (Note that if you use the Office installer in the future to change installed components or repair your installation, it may put back the old EQNEDT32.EXE and you'll have to manually replace it again.)


×
×
  • Create New...