NotHereToPlayGames

Go to your temporary working "options" folder where you used PeaZip and extracted "options.zip". Open "options.html" in Notepad++. Do a Ctrl-F (Find) for "certificate_list" (without the quotes) then close the Find dialog. Make the five changes pictured below labeled as "first before". Do a second Ctrl-F (Find) for "certificate_list" (without the quotes) then close the Find dialog. Make the one change pictured below labeled as "second before" then use PeaZip to "Medium compression, ZIP (compatible with most extractors)" all the files in the "options" folder. Cut-and-paste the new "options.zip" back into the 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (360Chrome should be CLOSED when you do this).

Go to your temporary working "options" folder where you used PeaZip and extracted "options.zip". Open "options.html" in Notepad++. Do a Ctrl-F (Find) for "close_last_tag_radio" (without the quotes) then close the Find dialog. Make the four changes pictured below then use PeaZip to "Medium compression, ZIP (compatible with most extractors)" all the files in the "options" folder. Cut-and-paste the new "options.zip" back into the 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (360Chrome should be CLOSED when you do this).

Go to 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (ie, version.0.build.0) Copy "options.zip" file to a temporary working folder. Open PeaZip and browse to the temporary working folder that you copied "options.zip" to via the left pane. Right-click on top of "options.zip" in the right pane and select "Extract all here, in new folder (Ctrl+Shift+Alt+N)" in the drowdown menu. Go to the temporary working folder via your preferred File Manager and you'll now have an "options" folder. Inside that "options" folder is an "options.html" file - open that file via Notepad++. Do a Ctrl-F (Find) for "login" (without the quotes) then close the Find dialog. Make the changes pictured below then save "options.html" and exit Notepad++. Note: I optionally remove the "hand" .png and also change the color of the text to match the rest of the GUI Interface (the color difference is too slight to even be noticed in the "dark" theme). In PeaZip, double-click the "options" folder that was created when you extracted "options.zip". Do a Ctrl-A to select ALL of the files inside the "options" folder. Once ALL of the files are highlighted, then select the down-arrow to the right of the "Add" button in the upper left corner of PeaZip. In the dropdown, select "Medium compression, ZIP (compatible with most extractors)". Click "OK" in the bottom right corner of the "New Archive" dialog. Return to your preferred File Manager "options" folder and CUT the new "options.zip" file that was just created. Go back to 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (ie, version.0.build.0) and rename or archive the original "options.zip". PASTE the new "options.zip" that you CUT two step up into the 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (360Chrome should be CLOSED when you do this). I suggest KEEPING the temporary working "options" folder because we'll be making more changes later.

Optional as some prefer the "dark" but I prefer to be "enlightened" (waka, waka, waka). The skin/theme changer will still work even with our above Hosts File entries. But if you want to see the "preview" thumbnails then you will need to temporarily disable the above Hosts File. You'll need to PgDn two or three times to find the skin that I use. I include it as a step here mainly for the sake of before-and-after pictures in following steps.

Go to 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (ie, version.0.build.0) I delete (but a rename would have the same effect) the following two files as they are both all Chinese and the browser is fully functional without them. errorpage.zip newtab.zip The errorpage is basically just a DNS 404 similar to the old ieframe.dll days. The newtab now reverts to an EMPTY page with a "New Tab" tab title (whereas "about:blank" has no tab title).

Open 360Chrome -> 360Loader.ini I add these entries to [FileToRun] -> Parameters --kiosk-printing --disable-print-preview --cipher-suite-blacklist=0xe013 I add these entries to [RunAfter] FileDelete=%Profile%\Default\IndexedDB\chrome-extension_{extension-id-1}_0.indexeddb.leveldb\*.log FileDelete=%Profile%\Default\IndexedDB\chrome-extension_{extension-id-2}_0.indexeddb.leveldb\*.log FileDelete=%Profile%\Default\data_reduction_proxy_leveldb\*.log;MANIFEST-* FileDelete=%Profile%\Default\Extension State\*.log;*.ldb FileDelete=%Profile%\Default\File System\Origins\*.log FileDelete=%Profile%\Default\MANIFEST-*;*.ldb DirRemove=%Profile%\Default\Sessions DirRemove=%Profile%\Default\blob_storage DirRemove=%Profile%\Default\VideoDecodeStats

Open 360Chrome -> Chrome -> Application -> 360chrome.exe in Resource Hacker. Make the three changes as shown below (file description, product name, and product short name). Pull down "Action" menu and click "Compile Script" at very top. Pull down "File" menu and click "Save" (the original file is automatically kept for you and renamed to "360chrome_original.exe"). Exit Resource Hacker.

Go to the 360Chrome -> Chrome -> User Data -> Default folder. You will find a file with no file extension called "Preferences". With 360Chrome CLOSED, open the "Preferences" file in Notepad++. Do a "Ctrl-F" (Find) for "lang" (with no quotes) then close the Find dialog box. The original line will read "accept_languages": "ru-RU,ru,en-US,en" Edit the line to read "accept_languages": "en-US,en" (ie, just delete the ru-RU,ru, portion). Save the "Preferences" file and exit Notepad++.

I prefer the latest Hosts File from here -- https://winhelp2002.mvps.org/hosts.htm And then add these entries -- 0.0.0.0 browser.360.cn 0.0.0.0 cloud.browser.360.cn 0.0.0.0 dd.browser.360.cn 0.0.0.0 qurl.f.360.cn 0.0.0.0 chrome.360.cn 0.0.0.0 ext.chrome.360.cn 0.0.0.0 u.qurl.f.360.cn 0.0.0.0 puv.tt.browser.360.cn 0.0.0.0 p.ssl.qhimg.com 0.0.0.0 p0.ssl.qhimg.com 0.0.0.0 p1.ssl.qhimg.com 0.0.0.0 p2.ssl.qhimg.com 0.0.0.0 p3.ssl.qhimg.com 0.0.0.0 p4.ssl.qhimg.com 0.0.0.0 p5.ssl.qhimg.com 0.0.0.0 p.ssl.qhmsg.com 0.0.0.0 p0.ssl.qhmsg.com 0.0.0.0 p1.ssl.qhmsg.com 0.0.0.0 p2.ssl.qhmsg.com 0.0.0.0 p3.ssl.qhmsg.com 0.0.0.0 p4.ssl.qhmsg.com 0.0.0.0 p5.ssl.qhmsg.com

Below is my guide on how to convert some of the Chinese still present in 360Chrome. Also includes a few tweaks to reduce/eliminate privacy risks. I'll unfold the guide a little at a time over a few weekends or so and have inserted "placeholder" posts to keep them all at the top of the thread. I use the Russian Repack from here (version 13 build 2206) -- https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html Run the "_Unpack Portable.cmd" and it will create a "360Chrome" folder - we will be modifying files inside that folder. You can always revert back to original by renaming folder and running "_Unpack Portable.cmd" again. Freebie software that you will need. Resource Hacker --- I prefer the portable ZIP at the bottom of here -- http://www.angusj.com/resourcehacker/ PeaZip --- I prefer the 32bit Portable version from here -- https://peazip.github.io/peazip-portable.html Notepad++ --- I prefer portable version 6.8.8 but newer versions work just as well -- https://sourceforge.net/projects/portableapps/files/Notepad%2B%2B Portable/ Chrome PAK Customizer -- I use v2.0, grab the chrome-pak.7z from here -- https://github.com/myfreeer/chrome-pak-customizer/releases HxD Hex Editor --- I use version 2.4.0.0 from here -- https://mh-nexus.de/en/hxd/

So if I understand this correctly, the ONLY way for you to UPDATE root certificates is to ALLOW a weak cipher ??? If that is true, then this seems to me to be case-in-point to NOT disable a cipher just because it is "weak".

Thanks @VistaLover -- I've disabled 0xe013 now as well. ALL browsers (will confirm one of these days with Win10 browsers, probably should do that before I use the word "all") have "weak" (never used?) ciphers, but this is the first I've seen any mention of any "exclusive" shenanigans!

Here's the breakdown as far as "weak ciphers" go --

I apologize if I sounded too "critical". I simply failed to comprehend why anyone would point out 6 (7?) "weak ciphers" in the browser that this thread is discussing but throw a blind eye to to the TWICE AS MANY "weak ciphers" in the other popular browsers discussed on this forum. If Roytam isn't striving for ZERO "weak ciphers", then why would we expect a repacked Chrome version targeting XP to strive for ZERO "weak ciphers"? But again, apologies if I didn't tackle this with a tad more "political correctness"

To each their own, but in "my book" this is a GIGANTIC don't care!. I see it somewhat as a smear-campaign tactic to scare people away without viewing the bigger picture. But I'll follow along for the sake of discussion and to illustrate that bigger picture. You cited 7 weak ciphers - which version did you pull that from? I'm showing only 6 for v13 -- 0xc013, 0xc014, 0x9c, 0x9d, 0x2f, and 0x35 -- https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html BUT, since we are on this path - I'm showing 12 for Mypal 27.9.4 - but no surprise, it's dated 2018. I'm showing 12 for palemoon-27.9.7.win32-git-20210130-126891b20-xpmod released just this past weekend. I'm showing 12 for palemoon-28.10.2a1.win32-git-20210130-0fe3d520e-uxp-e1daeef18-xpmod released just this past weekend. I'm showing 12 for bnavigator.win32-20210130-355db4de-uxp-e1daeef18-xpmod released just this past weekend. I'm showing 14 for basilisk55-win32-git-20210130-27e1f69a6-xpmod released just this past weekend. I'm showing 12 for basilisk52-g4.8.win32-git-20210130-5fdeb2a-uxp-e1daeef18-xpmod released just this past weekend. I'm showing 12 for arcticfox-27.11.0.win32-git-20210130 released just this past weekend.

The tab between "Lab" and "Adfilter" is "Security and Privacy". It's actually fairly easy to fix. I fixed mine labeling it "Security" (screen cap below). The "how" kinda needs done by yourself on your end (I wouldn't want to violate any copyrights/trademarks by making changes for you and uploading). So I can walk you through "how" but I don't think I can upload - better safe than sorry. I use the "portable repack" so these instructions stem from that. Go to your "install-folder\Chrome\Application\version.0.build.0" folder. You will find an "options.zip" file in that folder - unzip using WINRAR (will not work using IZArc or 7-Zip, did not try others). Once unzipped, you will find an "options.html" file. Open "options.html" with Notepad++. There's over 3600 lines but you can page down and easily find all of the "Chinese" because they'll show up as a bunch of boxes (unless you have a Chinese font installed or allow fonts to install on their own, which I do not). When you find the "Chinese" 'boxes', simply highlight, copy, and paste into Google Translate. Then replace the "Chinese" 'boxes' with however you wish to reword the translation. Once you go through all 3600 lines (you only need to edit two dozen or so, don't remember offhand), save the file and rezip using WINRAR. Close 360, save the new "options.zip" back into the "install-folder\Chrome\Application\version.0.build.0" folder. Now when you open 360, you will see your translations instead of the Chinese remnants not translated by the Russian Repack guy. Really easy :)

I know that I already called it a Dead Horse - but I've come across a REPEATABLE test if you WANT to CRASH your browser. A word of caution in advance, this *will* CRASH your browser and you *will* have a TON of error dialogs to clear. But the computer does remains responsive - I'm only crashing the browser and not the OS. I did this in a WinXP VirtualBox with 2GB RAM - the numbers would vary plus or minus 5 or so with consecutive runs. v11 crashed with only roughly 58 about:blank's opened. v12 crashed with roughly 74. V13 crashed with roughly 97. Note that I"m only loading "about:blank" tabs but this test DOES demonstrate that newer versions don't crash as early as older versions with a "ton of tabs" open. Here's how (I use the "portable repack", so these instructions will need modified if you use the "installed" version versus the "portable") - Create a "crash.bat" file (without the quotes) in the same folder that contains "360Loader.exe". When you execute crash.bat, several about:blanks will open and *will* eventually CRASH -- the command prompt will stop incrementing when no more about:blanks will load - ie, you crashed your browser. The crash.bat contents follow -- @echo off for /l %%i in (1,1,1000) do ( echo Tab Count: %%i start 360Loader.exe "about:blank" ping 127.0.0.1 -n 1 > nul ) Happy Crashing

Yes, again no disagreement. But "at the same time" these people with only 2GB of RAM need to stop living in a "fantasy world" and stop expecting their 1996 computer to function 100% in 2021. ie, if you only have 2GB of RAM and you are loading 10 or more tabs, "then you bring upon your own pain and no doctor can treat you." That said, I have 6 computers and two of them have 2GB of RAM (one used exclusively for streaming videos, but I don't bog it down with other tabs while doing so, that would be "unrealistic" of me). I certainly don't expect them to function comparably to my i7-4770 computer with 16GB of RAM. But anyway, I think we've beat this dead horse and others know where we are both coming from

No disagreement. Just pointing out that RAM utilization isn't "linear" and I don't think the userbase should "water it down" as such (not "you", per se, just speaking in generalities). We have to consider a "balance" - what good is a browser with a TINY "footprint" but it CRASHES because of excessive RAM with only 10 tabs loaded? I'm just pointing out that if you want a TINY "footprint" then use a browser that does NOT have "tabs". But since this isn't 1996 and we all use "tabs", then we have to find that "balance" Here's another chart. This time with 5 "real-life scenario" tabs - one with 720p streaming audio/video, one with a big Flash loop, one with a Sudoku game, one with a Google Search, and one with a top-rated news headline site. Yes, by "magnitude" newer Chrome versions use more RAM then older (no duh, lol) - BUT if a difference of a few hundred MB is "make or break" or crashes your system, then my advice is to use a browser from 1996 "mileage may vary"

I do not agree that v13 is "more RAM hungry". I believe that v13 utilizes RAM better than v12. And in turn v12 utiilzes RAM better than v11. RAM utilization is not a "linear" process and it's not as simple as just comparing "magnitude", so to speak.

I've finally tracked down my printing issues in 360EE v11, v12, and v13. While I can't speak for WHY this was happening, I found a fix for it nonetheless (only tested in v12 and v13). Whenever I would attempt to print to my wireless printer via 360EE, the browser would LOCK UP requiring a process-kill via Task Manager and a reboot of my wireless router to get the printer back! 360EE would "scan" for printers and find one of my Roku Express HD Streaming Media Players instead! The then-idle Roku would then steal the IP Address for the then-idle wireless printer and 360EE would try to print to the Roku which would just ignore the "data" being sent to it. The "fix" is to disable 360EE's "stupid" print preview 'feature'. In v12, add " --kiosk-printing --disable-print-preview" to the Parameters line in 360Loader.ini and go to chrome://flags and DISABLE "Enable Cloud Printer Handler". In v13, add " --kiosk-printing --disable-print-preview" to the Parameters line in 360Loader.ini, no chrome://flags needed changed in v13. Shew! What a Relief! That was kind of a nightmare, lol.

lol, yeah, I'm aware of the irony. I "cripple" my Google Voice and do track DNS queries. My only excuse is that I *KNOW* when Google Voice is loaded and what traffic to Google occurs. And I *KNOW* when Google Voice is NOT loaded and what traffic to Google is blocked. I can use this very forum as why I have a "curiosity" in 360Chrome - I know others have posted and there's probably a "fix", but I have not gotten that far yet. But I do know the ONLY way I can now POST on this forum is by using CHROME/CHROMIUM. Again, there may be a "fix", it's not that high up my priority list yet :)

I synchronize my profile to a USB file once a month or so and I've *WITNESSED* a file with "telemetry" in the name exist! I'll screen-cap the next time I witness this behavior.

Thanks for the screen-cap. I block ALL of these via HOSTS file so I've not seen any suspicious DNS activity. 0.0.0.0 browser.360.cn 0.0.0.0 cloud.browser.360.cn 0.0.0.0 dd.browser.360.cn 0.0.0.0 qurl.f.360.cn 0.0.0.0 chrome.360.cn 0.0.0.0 ext.chrome.360.cn 0.0.0.0 u.qurl.f.360.cn 0.0.0.0 puv.tt.browser.360.cn 0.0.0.0 p.ssl.qhimg.com 0.0.0.0 p0.ssl.qhimg.com 0.0.0.0 p1.ssl.qhimg.com 0.0.0.0 p2.ssl.qhimg.com 0.0.0.0 p3.ssl.qhimg.com 0.0.0.0 p4.ssl.qhimg.com 0.0.0.0 p5.ssl.qhimg.com 0.0.0.0 p.ssl.qhmsg.com 0.0.0.0 p0.ssl.qhmsg.com 0.0.0.0 p1.ssl.qhmsg.com 0.0.0.0 p2.ssl.qhmsg.com 0.0.0.0 p3.ssl.qhmsg.com 0.0.0.0 p4.ssl.qhmsg.com 0.0.0.0 p5.ssl.qhmsg.com I use this to monitor DNS activity - DNSQuerySniffer v1.81 Copyright (c) 2013 - 2020 Nir Sofer Web site: http://www.nirsoft.net All that said, and while I do have high hopes for 360Chrome, I have not used it beyond the scope of "curiosity" because I cannot PRINT from v11, v12, or v13! A browser that cannot PRINT does not fit my needs but I do continue to have high hopes - it is nice for Google Voice to work 100% under Win XP and 360Chrome is the ONLY browser that can do that, to the best of my knowledge.

I'm not seeing anything at these offsets and nor have I seen any suspicious DNS activity (v13 patched with a few of my own hex-fixes). Sometimes "code" can remain in the exe/dll but it not be "called". For example, Roytam builds WILL create a "telemetry" file on occasion but I've not seen it "sent" anywhere (and the userbase tends to "blindly" trust that it isn't being "sent" anywhere). I think this "telemetry" file is also created by upstream Pale Moon but again, the userbase "blindly" trusts that it's not being "sent" anywhere.