Jump to content

AstroSkipper

Member
 View Profile  See their activity

  • Posts

    4,581

  • Joined

  • Days Won

    502

  • Donations

    0.00 USD 

  • Country

    Germany

 Content Type 

Everything posted by AstroSkipper

  1. AstroSkipper
    Hello @roytam1! The links above don't work, they all lead to 404.
  2. AstroSkipper
    @Humming Owl lets the user perform the rebasing by a batch file. In his uploaded archives, for example https://archive.org/download/360EE_Modified_Version/360EE_v13.0.2310.0_Rebase.7z, you can find the file libase.ini with the following code: [Configuration] StartBase=0x60000000 BaseSeparation=0x00100000 IgnoreCase=1 [Generated bases] 62a00000=CHROME.DLL 6da00000=CHROME_CHILD.DLL As you know, the file chrome_child.dll doesn't exist in 360Chrome v13.5, so forget about that command. It's only necessary, for example, for 360Chrome v11. He made the libase.ini file universal for all versions, at least I think so. Anyway! Libase worked without any problems in my case, so there was no need to use Rebase from Microsoft.
  3. AstroSkipper
    Hello @UCyborg! After using the method of rebasing the chrome.dll for a while, I have to thank you once again for sharing this method and providing a link to the tool libase. From now on, I am able to make sense of the 360Chrome browsers in my system and especially the version 360Chrome v13.5 build 1030. Kindest regards, AstroSkipper
  4. AstroSkipper
    From now on, users of avast! Free Antivirus 7 or older can use this universal key provided by avast! here: https://www.avast.com/registration-free-antivirus#pc On this website, you'll find additionally this information: Cheers, AstroSkipper
  5. AstroSkipper
    In my installation of 360Chrome v13.5 build 1030 rebuild 7, the Cloudflare check of the website https://mybrowseraddon.com/webrtc-control.html is passing successfully although the check takes a bit longer than usual. Setting back the flag Disable site isolation to Default was the first action I did when I installed this new build. It works definitely better with this default setting. Additionally, I added 18 flags and two command line switches. And of course, extensions. In total 13 of them, but not all of them are enabled. I manage them with the extension Extension Manager.
  6. AstroSkipper
    BTW, your release 360Chrome v13.5 build 1030 rebuild 7 works great in general, but I re-rebased the chrome.dll back to the address 0x62a00000 which seems to be more suitable in my system. With your rebased chrome.dll to the address 0x3e1c0000, I had some freezes. Now, it works better. Anyway! Good version! Thanks for your efforts!
  7. AstroSkipper
    The @AstroSkipper types! Nice description! I sincerely hope it was meant in a friendly way.
  8. AstroSkipper
    Same in New Moon 28. After setting security.ssl3.rsa_aes_128_gcm_sha256 to true, MEGA downloads are working again.
  9. AstroSkipper
    You are absolutely right. This entry was pre-configured, and I forgot to remove it. I thought my config file was clean. I do have a lot of these config files. Anyway! Good find! After removing it works indeed. So, the problem is really cipher related.
  10. AstroSkipper
    The cipher suite TLS_RSA_WITH_AES_128_GCM_SHA256 was already implemented in ProxHTTPSProxy 1.5.220717. I tried to connect to Mega using Serpent 55 via ProxHTTPSProxy 1.5.220717, and the download of files didn't work, either. Same issue as without using the proxy. Therefore, I think the problem is presumably not only a cipher incompatibility.
  11. AstroSkipper
    Interesting news! ProxHTTPSProxy can only be used by programs which offer an option to use the IE proxy settings as for example browsers or use system components if the proxy has been set system-wide. From now on, we have the possibility to connect any program with a server or the internet via the local proxy ProxHTTPSProxy if necessary, of course including the latest protocol TLS 1.3. The solution is SocksCap64. I have already tested this tool, and it works perfectly with ProxHTTPSProxy. Link: https://www.sockscap64.com/homepage/ Cheers, AstroSkipper
  12. AstroSkipper
    I have tested FreeCap and SocksCap64 for suitability. I set up ProxHTTPSProxy as the proxy server and Iceape-UXP as the program that should exclusively use this proxy server via FreeCap or SocksCap64. The results were very different. FreeCap works with a local proxy like ProxHTTPSProxy more badly than well, SocksCap64 on the other hand has no problems with a local proxy like ProxHTTPSProxy and and works perfectly together with such a proxy. Therefore, my recommendation is definitely SocksCap64.
  13. AstroSkipper
    Just an idea! What about establishing a VPN connection to circumvent ForcePoint's censoring? If a VPN connection is established, all @roytam1's browser with their own TLS 1.3 clients (set to No Proxy, of course) use this connection. Maybe, OE Classic, too. ForcePoint actually shouldn't notice a connection to www.oeclassic.com via VPN.
  14. AstroSkipper
    And on raymond.cc, there is a further recommendation called WideCap: http://web.archive.org/web/20130228172919/http://widecap.ru/files/widecap_setup.en.1.4.exe This tool is abandoned, too, but although it was originally payware, it was changed to freeware in the past. In my system, I have installed Proxifier for a long time. It's not free of charge but IMHO it's one of the best.
  15. AstroSkipper
    These commands can't be executed in Windows XP where you have to use proxycfg.exe instead. Your commands work only on Vista, 7 and up.
  16. AstroSkipper
    As far as I can see, you can try to set ProxHTTPSProxy systemwide by the command proxycfg -u. If it doesn't help, you can revert this by the command proxycfg -d. And did you try in the IE Proxy Settings only the setting of HTTP in combination with the option "Use the same proxy server for all protocols"? Anyway! Software which can't be activated easily is actually not worth its money. Maybe, you should try to get a refund. BTW, @roytam1's suggestion to use ProxyCap sounds promising in any case, though.
  17. AstroSkipper
    @Mathwiz! In which way did you set ProxHTTPSProxy as a systemwide proxy in Windows XP?
  18. AstroSkipper
    @NotHereToPlayGames! Nice to see that you followed my suggestion to offer a special version for Windows XP users after all. Although I no longer need this version and have already rebased the chrome.dll file in my installation of 360Chrome 13.5 build 1030, I'm sure other users here will be happy about a RAM-friendly version for Windows XP. Or did you do other changes except rebasing the chrome.dll file?
  19. AstroSkipper
    I use different profiles for all my browsers. No sharing of profiles anymore for years. In the past, I made bad experiences with shared profiles which became suddenly corrupted. And I always keep backups of important profiles to be on the safe side. Happy New Year, too
  20. AstroSkipper
    The information I researched was actually intended for @UCyborg relating to the browser and our conversation here. So on-topic, unlike so many other posts here. You are welcome to post the problem on the WiseVector StopX forum, but it is not official and therefore not really helpful. But, as I explained in my last post, for me personally, the problem is already solved after rebasing the chrome.dll file. And BTW, the culprit of my BSOD was not my computer. Maybe, you should read my posts again. I think you missed something.
  21. AstroSkipper
    My mainly used browsers in Windows XP are the @roytam1's browsers New Moon 28, Serpent 52, Serpent 55 and @feodor2's browser Mypal 68. Additionally, I use @NotHereToPlayGames's modified browser 360ChromePortable 13.5.1030 rebuild 6 with a chrome.dll rebased by me, only if the others fail on a specific website.
  22. AstroSkipper
    @UCyborg! I removed all exclusions made for 360Chrome v13.5 build 2022 in WiseVector StopX. Running again this browser with the rebased chrome.dll does not cause a BSOD anymore. Therefore, my assumption that rebasing chrome.dll might avoid such conflicts is presumably correct. q.e.d.
  23. AstroSkipper
    This is a quotation from https://www.mandiant.com/resources/blog/six-facts-about-address-space-layout-randomization-on-windows: Important parts are marked by me in bold type.
  24. AstroSkipper
    I thought Windows XP wouldn't be able to rebase dll files in its memory due to the lack of the ASLR feature and would always load these files to their predetermined addresses.
  25. AstroSkipper
    I had only BSODs in the past when starting one of the 360Chrome browsers which had a conflict with WiseVector StopX. Only a total exclusion of all 360Chrome installations in WiseVector StopX helped to avoid further BSODs. And I never had any other BSODs before. My system is flawless, so to speak, at least there are no discernible problems. I assume that rebasing chrome.dll might avoid such conflicts. In any case, I will test this again. BTW, I never said that rebasing is a culprit of whatever. Quite the opposite! I think you have misunderstood something.
×
×
  • Create New...