Leaderboard

This is a very interesting discussion. I don't understand 99% of the acronyms and have no idea what you guys are talking about BUT I wanted to tell you that I have WMC guide listings up to Feb 16th which I downloaded a few days ago in February. I have received no notice that the guide is going away other than in third party online blogs. I'm not saying that it isn't going to happen, but Microsoft sure hasn't told me anything. Ssssshhhhh! don't tell Microsoft that they forgot to turn my guide off!!

@Nikitastepanov Rather than posting a whole series of new threads, please learn to use the search function of this forum and spend some time reading through the many informative threads that already exist. (See "Important/Sticikified Topics") These will answer most of your questions. Don't expect people to do all of your work for you. These two specific questions are both answered by updates created by rloew, who recently passed away. You can find links to his software here.

Out of curiosity, I downloaded that MS update from the link in the KB article; that fetched file "excel2010-kb4484164-fullfile-x86-glb.exe", sized 36.1 MB (!). I can confirm this is only SHA-2 code-signed: You'll have to test file code-signing signatures in a fully updated Win7 system (or higher) or, in my case, in Vista SP2 with one of the WS2008SP2 updates which give the OS SHA-2 code-signing verification support... Trying the Windows Update Catalog link (mentioned in that same KB article), http://www.catalog.update.microsoft.com/Search.aspx?q=KB4484164 I ended up with a different file, excel-x-none_a5b150722cca4d6d9b062063747b02df0eaaaf51.cab (sized 19.8 MB); extracting it yields an excel-x-none.msp file (Windows Installer Patch, sized 40.3 MB), which is also only SHA-2 code-signed; notice that on the MUC, only a generic version is offered, regardless of the OS on which Office 2010 is installed ; perhaps the .exe and .msp files check OS version when launched, but it didn't occur to M$ that XP+Vista don't support SHA-2 code-signatures; there was a specific update on Vista (KB2763674) that allowed for .exe file execution even in the case the .exe was only SHA-2 signed, I guess a similar one might exist in XP (as part of the POSReady ones?) ... The deal breaker here is that Windows Update on both XP and Vista was never patched to deliver updates signed with only sha-2 code signatures - for WS2008SP2, such an update does exist, but when that's installed on Vista, it changes the build number of Vista to 6.0.6003 - but that cuts off Vista completely from WU servers , because they were only configured to serve Vista 6.0.6002 builds; it emerges that WU servers are intelligent enough to tell apart Vista 6.0.6003 (blocked) from WS2008 6.0.6003 (supported); so, starting with Nov 2019 (and for the remaining updates till Oct 2020), users of Office 2010 SP2 on XP/Vista should manually install applicable updates from either MS Download Center/MUC... ( ... and you thought M$ would screw Office 2010 only on XP, by sending incompatible mso.dll files... )

That's good; your last post had me worried! My yellow shield was there this AM with the three Office 2010 updates. Since manual installation still works, here are links to their support pages: https://support.microsoft.com/kb/4484164 https://support.microsoft.com/kb/4484127 https://support.microsoft.com/kb/4484160 You can go to each support page, scroll down to "Option 3: Microsoft Download Center," and find links to the standalone installers for both 32- and 64-bit versions of Office 2010. (I would assume the vast majority of folks have 32-bit systems, but just in case....)

Believe it or not, I think I found a solution to this vexing problem: how can we use older browsers with https-secured Web sites that use newer security features than the browser does? The solution I found is a proxy server that performs an intentional MITM (man-in-the-middle) attack on the browser. Obviously that's a security risk, but since everything is running on one machine, the risk is minimal as long as this software properly validates certificates. It's free and can be found here: http://www.proxfilter.net/proxhttpsproxy/. (There's a picture there that explains it better than I can.) I tested it today on my XP VM, and was able to access that aidanwoods.com site with Chrome 34! It was written so the popular Web-filtering proxy server Proxomitron (used to remove ads, etc., from Web pages) could be used with secure sites, but with a simple configuration change, I confirmed it will run without Proxomitron or any other filtering proxy. You'll need a recent version of OpenSSL too. I tested 1.0.2j and it worked, so Ninho should be all set for now. As newer cipher suites become popular on the Web, you'll need to update OpenSSL to keep up, but that shouldn't be a problem. Edit: Turns out you only need OpenSSL for the Python version (as well as Python, naturally); everything is already built into the .exe version at the link above. (If you want the Python version or just want to look at the code, the link is at http://prxbx.com/forums/attachment.php?aid=998.) I think this will work even as far back as Windows 98, but it may be this weekend before I can test it on my Win 98 non-SSE2 system. Once I've done that, I'll post more detailed instructions here and in the Win 98 forum.