Content Type
Profiles
Forums
Events
Posts posted by heinoganda
-
-
Small side note to KB4494528, MS has in the updates for MSI 4.5, since the update KB2918614 from August 11, 2014, the installer deleted various entries in the installation file (update_SP3QFE.inf). These have led to the problem of not recognizing the existing MSI version and to the current problem of unregistered msi.dll. Even with my update rollup I have corrected this error in the updates for MSI 4.5.
The following entries are missing in the file update_SP3QFE.inf:
[Prerequisite]
condition=CompositeOp,AndOp,MsiPrereq.Section[ProcessesToRun]
"%systemroot%\system32\spupdsvc.exe /install"[ProcessesToRunBeforeUninstall]
%systemroot%\system32\spupdsvc.exe /install
"%windir%\system32\regsvr32.exe /s /u %windir%\system32\msi.dll"[ProcessesToRunAfterUninstallReboot.RebootNotRequired]
"%windir%\system32\regsvr32.exe /s %windir%\system32\msi.dll"[ProcessesToRunAfterReboot.RebootNotRequired]
"%windir%\system32\regsvr32.exe /s %windir%\system32\msi.dll"[Msidll.Present.Section]
PresentOp=CheckFilever,system32.Files,msi.dll[Msidll.AndOp.Section]
GreatOrEqualOp=CheckFilever,system32.Files,msi.dll,">=",4.5.6001.22159
LessOrEqualOp=CheckFilever,system32.Files,msi.dll,"<=",4.5.6002.24556[MsiPrereq.Section]
SingleOp=Msidll.Present.Section
AndOp=Msidll.AndOp.Section
Display_String="This fix only installs over MSI 4.5"The file "spupdsvc.exe" is also missing into the update KB4494528.
0 -
0
-
Have just tested the language files from the Firefox version 52.9.0 in version 52.9.1 successfully.
Download from the Firefox version 52.9.0 language files and
download the Simple Locale Switcher (v 1.0.2).
Note:
Maybe these files should also be backed up.1 -
Update for root certificates:
New:
CN = Autoridade Certificadora Raiz Brasileira v5
OU = Instituto Nacional de Tecnologia da Informacao - ITI
O = ICP-Brasil
C = BRCN = NAVER Global Root Certification Authority
O = NAVER BUSINESS PLATFORM Corp.
C = KRCN = RCSC RootCA
O = VI Registru centras- i.k. 124110246
OU = RCSC
C = LTThose using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.
4 -
Have new build generated by ProxHTTPSProxy v1.5 (Rev3c), python module cryptography-2.6.1 with openssl-1.1.1b (Thanks to @Mathwiz) updated.
If anyone has interest please write a PM to me.Info:
At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).3 -
Perhaps the following CSS errors on Instagram can help narrow down the problem with Firefox 52.9.0 / 52.9.1
Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:273 Unknown pseudo-class or pseudo-element ‘-webkit-full-screen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:28 Unknown pseudo-class or pseudo-element ‘-ms-fullscreen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:121 Unknown pseudo-class or pseudo-element ‘fullscreen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:164 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. Br-vL3OldQJ:1:228 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:2541 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:130 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:57 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1038 Error in parsing value for ‘background-image’. Declaration dropped. Br-vL3OldQJ:1:2364 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:261 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:12541 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:12570 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:302 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:88 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:62 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:348 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:1363 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:707 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:811 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:267 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:570 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:188 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:521 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:438 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:88 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:494 Expected color but found ‘auto’. Expected color but found ‘-webkit-focus-ring-color’. Expected end of value but found ‘-webkit-focus-ring-color’. Error in parsing value for ‘outline’. Declaration dropped. Br-vL3OldQJ:1:311 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:478 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:535 Unknown pseudo-class or pseudo-element ‘-ms-clear’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:663 Unknown pseudo-class or pseudo-element ‘-webkit-inner-spin-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:724 Unknown pseudo-class or pseudo-element ‘-webkit-search-cancel-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:850 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1142 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:77 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:121 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:413 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:56 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:171 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:222 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1326 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:770 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:799 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:2096 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:2125 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:384 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:413 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:535 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:564 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:866 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:895 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:12880 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:12909 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:279 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:308 Unknown property ‘backdrop-filter’. Declaration dropped. Br-vL3OldQJ:1:161 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:388 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:738 Unknown property ‘backdrop-filter’. Declaration dropped. Br-vL3OldQJ:1:443 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:511 Error in parsing value for ‘background-image’. Declaration dropped. Br-vL3OldQJ:1:489 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:461 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:153 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:460 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:437 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:466 Unknown pseudo-class or pseudo-element ‘-webkit-media-controls-start-playback-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:126 Unknown property ‘overflow-anchor’. Declaration dropped. Br-vL3OldQJ:1:124 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:761 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:963 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:2290 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:397 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1442 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:2133 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:2902 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:222 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:864 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:948 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:54 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:139 Unknown pseudo-class or pseudo-element ‘-ms-clear’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:323 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:392 Error in parsing value for ‘background’. Declaration dropped. Br-vL3OldQJ:2:2320 Error in parsing value for ‘background’. Declaration dropped. Br-vL3OldQJ:2:2946
A test with Google Chrome 44 was positive.
0 -
-
19 minutes ago, Mathwiz said:
Almost. (I assume that unlike me, you have a full version that will not expire!)
A part of VS2010 can be installed from the DVD (GRMSDK_EN_DVD.iso), no licenses needed. Whether that's enough to create OpenSSL unfortunately I do not know.
19 minutes ago, Mathwiz said:I didn't try that for this Windows build, but if it works, I assume everything would be built into the .lib files and no .dll files would be built, which I believe is how the Cryptography developers intended it.
I do not know. We could test it, but it does not necessarily have to be, especially as it takes time. I'm busy with today's updates.
Again a big thank you for your efforts!
0 -
8 hours ago, Mathwiz said:
I think this is even better than the original! With the original Cryptography, we had to wait for the Python developers to release a new Cryptography version, incorporating the latest OpenSSL. With your version, we only need to replace the .dll's in C:\Python34\Lib\site-packages\cryptography\hazmat\bindings.
That does not work. The size of the lib files in your package seemed very small, but I leave no stone unturned. For the missing parts in the lib files (have landed at the files libcrypto-1_1.dll, libssl-1_1.dll and possibly also at capi.dll, padlock.dll) there must be a reference in the lib files to the dll files Especially since without these files an error message from HTTPSProxy is issued because of missing dll files. Part of VS2010 is needed to build the cryptography module in Python 3.4.4 (Microsoft Windows SDK (for Windows 7) DVD (GRMSDK_EN_DVD.iso), maybe the VS2010 on this DVD is enough to create OpenSSL?). Therefore, the files from the Include folder are also needed. If you look at the size of the generated _openssl.pyd file in the newly created Cryptography modules, that is noticeable. I'm glad it works that way because it keeps the puzzle for TLS1.3 moving forward.
The users who use Python version 3.5 or higher need a build with VS2015! The Cryptography module would therefore have to be created under Windows 7 (parts of VS2015 are needed) with your customized OpenSSL variant and hope that this module now works under Windows XP.
The procedure in the case of Python 3.7 is identical to that of Python 3.4.4, which means installing Python 3.7 on the Windows 7 machine where a VS2015 is also installed, loading the desired cryptography module from the cryptography project website and before running your OpenSSL package (created with VS2015) copy the lib files from the lib folder to the python37\libs folder and copy the openssl folder to python37\include from the include folder (these files are no longer needed after the module is created). After the module has been created (pip install cryptography-2.6.1.zip), the dll files to python37\lib\site-packages\cryptography\hazmat\bindings have to be manually copied from the bin (from your OpenSSL package) folder, as well as the dll files from the folder lib\engines-1_1. Now make an adjustment to the file installed-files.txt in the python37\lib\site-packages\cryptography%version%-py3.7.egg-info folder where the following lines are added:
..\cryptography\hazmat\bindings\capi.dll ..\cryptography\hazmat\bindings\libcrypto-1_1.dll ..\cryptography\hazmat\bindings\libssl-1_1.dll ..\cryptography\hazmat\bindings\padlock.dll
All __pycache__ folders in python37\lib\site-packages\cryptography and subfolders can be deleted and finally pack the two cryptography folders with 7z or WinRAR.
1 -
The cryptography 2.6.1 module with OpenSSL -1.1.1b (thanks to @Mathwiz) for Python 3.4.4 I have tested so far with the following modules:
altgraph==0.16.1
appdirs==1.4.3
asn1crypto==0.24.0
cffi==1.12.2
colorama==0.4.1
cryptography==2.6.1
future==0.17.1
idna==2.8
macholib==1.11
packaging==19.0
pefile==2018.8.8
pyasn1==0.4.5
pycparser==2.19
PyInstaller==3.4
pyOpenSSL==19.0.0
pyparsing==2.3.1
PySocks==1.6.8
pywin32==221
pywin32-ctypes==0.2.0
six==1.12.0
urllib3==1.24.1
For Installing:
Uninstall the older cryptography module beforehand (pip uninstall cryptography), then simply unpack the two directories in the python directory
python34\lib\site-packages.(The latest cryptography module 2.7.dev1 from March, 11 2019 for testing is also included)
Note:
The manually installed cryptography module can be uninstalled the usual way (pip uninstall cryptography)!5 -
6 hours ago, Mathwiz said:
Final (apparently XP-compatible) build of OpenSSL v1.1.1b is about 3 MB when written to a .7z archive file. You can download it from my company's Web site.
I was able to create a working Cryptography (2.6.1) module for Python 3.4.4 , but the two binaries libcrypto-1_1.dll and libssl-1_1.dll are required. Had to improvise something (is not in the sense of Cryptography module creator), it works and that's the main thing. Now I will do several tests (when the tests are completed, I will make this module available). Thanks a lot!
1 -
8 minutes ago, Bersaglio said:
You previously mentioned that this is not possible...
I have created my own cryptography module with OpenSSL 1.1.0j. I would prefer the latest OpenSSL 1.1.1b, but this does not work in Windows XP.
More on this
0 -
Have new build generated by ProxHTTPSProxy v1.5 (Rev3b), various python modules updated (cryptography-2.6.1_openssl-1.1.0j), config.ini supplemented by some entries, CA certificates (cacert.pem) updated and alternativ cacert.pem from MSCerts (Cert_Updater) 11/28/2018.
If anyone has interest please write a PM to me.Info:
At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).3 -
Additional Information:
To generate your own cryptography module, the desired module is downloaded from the cryptography project website (https://github.com/pyca/cryptography/releases) (cryptography-2.6.1.zip). Then we need an appropriate OpenSSL release (best from the release infrastructure of the cryptography project Unfortunately, the website is not always available!) and for Python 3.4.4 Windows Native Code Development (VS2010) from the Microsoft Windows SDK (for Windows 7) DVD (GRMSDK_EN_DVD.iso). From Python 3.5 Windows Native Code Development (VS2015).
Further Information https://cryptography.io/en/latest/installation/#building-cryptography-on-windows. I have successfully created the cryptography module 2.6.1 with OpenSSL 1.1.0j (openssl-1.1.0j-2010-x86.zip from the release infrastructure of the cryptography project) for Python 3.4.4. Now the problem is that from OpenSSL 1.1.1a (openssl-1.1.1a-2010-x86.zip) compatibility is no longer given to Windows XP. We need a customized version of openssl-1.1.1b-2010-x86.zip and openssl-1.1.1b-2015-x86.zip that still works on Windows XP.
0 -
2 hours ago, Sampei.Nihira said:
What version of uMatrix did you install to make that failed test?
The switch: "Forbid web workers" is available from version 1.2.0.
They just do not want to understand that it does not work in the older Chromium versions! So as not to make you sleep, μMatrix version 1.3.16. If it's so hard to install a VM and install a Windows XP, then you can convince yourself that in the older Chromium versions the trick with μBlock and μMatrix does not work, I would have preferred it. The proxy solution is of course inconvenient for the normal user, but there is no choice. For Firefox, it is a simple service worker to disable. Otherwise, the topic is done for me.
0 -
5 minutes ago, Sampei.Nihira said:
I will never,never,never,install Chrome/Chromium
You can stay with whatever browser you want, but do not compare apples to oranges. In the meantime, a lot has happened with the Chromium version, so with version 72 that works too, but not with the older versions, regardless of the current version of μMatrix or μBlock (experiment with version 1.17.4).
0 -
3 hours ago, Sampei.Nihira said:
1. We are in the forum for Windows XP
2. It's about the older Chromium versions 44, the last official version for Windows XP 49 and Advanced Chrome 54.
3. On Windows 7/8/10 with Chromium version 72 it works with μBlock and / or μMatrix. (I'm lost for words!)
4. Please test under the conditions like other users in this part of the forum too, OS WindowsXP x86 and older Chromium versions as listed above!Maybe try this way to get an older version of μBlock installed.
0 -
This does not help on Chromium browsers that have implemented ServiceWorker.
With μMatrix
With proxy filter
0 -
For Chromium-based browsers under "chrome://serviceworker-internals" the current working scripts can be displayed, stopped and removed with (unregister) until the next call of certain web pages. The following websites were noticed:
When opening a new tab
https://www.4shared.com
https://www.youtube.com
Lastly, only HttpsProxy (ProxAddr and RearPort) helped interpose a proxy (Jana Server) where certain blocklist entries helpedyoutube.com/sw.js
serviceworker.js
sw _ *. jshelped put an end to these activities.
μBlock could not block these serviceworker scripts.Since they have us a real s*** installed in Chrome, which can not be deactivated.
0 -
3 hours ago, Dibya said:
I mean python greater than 3.7.1
In all honor, but what good is Python greater than 3.7.1, if the current modules do not work. We need the latest cryptography module, which works well in Windows XP.
0 -
10 hours ago, luweitest said:
The information I can get is from http://thehotfixshare.net/board/index.php?showtopic=13598 , "KB972828 - Files that are copied from a Windows Server 2008-based remote computer to a Windows XP SP3-based client computer by using the Remote Desktop Connection 6.1 client are corrupted". The file is signed, but I'd like to know why MS retrieved it back, if the hotfix has bug, superseded by some new fix or not. I am uncertain if I should install it.
The hotfix "KB972828" updates the file "lhmstscx.dll" if RDP 6.1 exists (I use RDP 7.0 myself). Security update KB2813345 (Info / Download from WSUS catalog) dated 04/08/2013 includes a more recent version of the lhmstscx.dll file, so KB972828 can not be installed. KB2813345 includes a QFE branch, which usually includes previous hotfixes. To try this out, first you have to uninstall the existing KB2813345 and install the downloaded KB2813345 manually with the parameter "/b:SP3QFE". I wish you success!
0 -
2 hours ago, -SnooPY- said:
Nevertheless, the problem with the new versions of "cryptography" and Python crashes would be interesting to solve.
I agree with that. As mentioned earlier, HTTPSProxy works on Windows 7 (bcrypt.dll should be functional on this level). Have already tested various "bcrypt.dll" file variants, where at least one, HTTPSProxy not crashed and if the certificates in Cert folder existed conditionally worked.
At least you can currently exclude Python 3.7, but what will after March 2019, especially since the last under Windows XP officially functioning Python 3.4.4 is no longer supported. It is likely that future modules will make problems.
Whether an error message helps the creator of the cryptography module because of the lack of support for the module (version 2.5, 2.6 and 2.61) with Python 3.4.4 on Windows XP, I dare to doubt.
0 -
Windows media 11 runtime (WMFDist11-WindowsXP-X86-ENU.exe) I could not find more in MS, but in Media Player 11 included (files "umdf.exe", "wmfdist11.exe" and "WindowsXP-MSCompPackV1-x86.exe" with WinRAR or 7zip extract). First install Media Player 10, then "umdf.exe", "wmfdist11.exe" and "WindowsXP-MSCompPackV1-x86.exe".
The following updates are required for this combination:
KB929399-v2
KB941569
KB952069-v2
KB973540
KB954155
KB972187
KB978695
KB975558
KB2834904-v2
KB3033890
KB3067903
0 -
Meanwhile, I have under Python 3.4.4 the current "cryptography" module version 2.6.1 also tested unsuccessfully under Windows XP. There are essentially two problems, one with the file "bcrypt.dll" (it looks like there are still some features missing) and the other with the system file "mpr.dll". I would recommend to install "cryptography" module version 2.4.2 manually to be sure that there are no problems with Python 3.7.
Download:
https://pypi.org/project/cryptography/2.4.2/#filesTo install manually:
pip install cryptography-2.4.2-cp37-cp37m-win32.whl
0
POSReady 2009 updates ported to Windows XP SP3 ENU
in Windows XP
Posted · Edited by heinoganda
@glnz
This adjustment of the file "update_SP3QFE.inf" in the update KB4494528 is of interest to users who want to fix this update in their update collection archive or whatever. If the update is already installed, a subsequent change brings nothing (before installing a modified KB4494528, the already installed update KB4494528 of MS would have to be uninstalled). Do not worry, important is that "regsvr32 MSI.DLL" was executed. As you should know in the meantime I create own update rollups or as with the oleaut32.dll problem that I could bridge with custom updates.