My plan is to lipo everything together into a three-arch universal binary (ppc, x86, x86_64).Firefox 45 ESR will continue to be supported with a security updates for another year or so and will run on Snow Leopard. I'm not quite sure what the story is with MacPorts's libcxx package it's currently causing me problems on the Intel side. Skip the commands for libc++ if that library doesn't exist. Install_name_tool -change /usr/lib/libc++abi.dylib lib/libc++.1.dylib Install_name_tool -change /usr/lib/libc++.1.dylib security_file_certgen Install_name_tool -change /usr/lib/libc++abi.dylib security_file_certgen Install_name_tool -change /usr/lib/libc++abi.dylib unlinkd Install_name_tool -change /usr/lib/libc++.1.dylib squid Install_name_tool -change /usr/lib/libc++abi.dylib squid ĭylibbundler -p -d lib -b -of -x security_file_certgen Not to mention, while Squid is quite lightweight, on very old Macs there may be a performance advantage to running it on a different machine.Ĭp /Library/Squid/security_file_certgen. But the separate computer method should be useful on Tiger, Mac OS 9, NEXTSTEP, etc. This allows local IP addresses to access the proxy, but not remote ones.īTW, I am currently working on updating the Squid package to install on Leopard (literally as I write this-I logged onto MacRumors to kill time while MacPorts compiles stuff). There is also an installer package here for ppc and intel.Īcl localnet src 0.0.0.1-0.255.255.255 # RFC 1122 "this" network (LAN)Īcl localnet src 10.0.0.0/8 # RFC 1918 local private network (LAN)Īcl localnet src 100.64.0.0/10 # RFC 6598 shared address space (CGN)Īcl localnet src 169.254.0.0/16 # RFC 3927 link-local (directly plugged) machinesĪcl localnet src 172.16.0.0/12 # RFC 1918 local private network (LAN)Īcl localnet src 192.168.0.0/16 # RFC 1918 local private network (LAN)Īcl localnet src fc00::/7 # RFC 4193 local private network rangeĪcl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machinesĭon't change anything else, including http_access deny all. I still recommend using squid on another device and connecting to that, but this may help if you don't have the option. This will take the load off of the G5 (which is currently running squid) and i can then connect any other "retro" machine to the macmini running squid if i need to.Įdit: If you dont have another machine, or don't want to install macports, here is a prebuilt package that you can manually install. My plan now is to take an old macmini and toss a barebones Linux on it, set up squid, and run it headless so it's out of the way. If you did everything right, LWK will once again be able to access wikipedia and other sites that had previously stopped working. Now check "secure web proxy (https)" and add in your machine running squid's internal IP address using port 3128 and hit apply. Now in Leopard, open system prefs -> network -> ethernet (or wifi depending on how you are connected) -> advanced -> proxies. Now edit the last 2 lines in /Library/Squid/nf and change "deny" to "allow" and save. For instance, install his Squid installer for 10.6-10.9 and follow the directions and ensure squid is properly running on your 10.6-10.9 machine. The easiest route is running squid on another machine (it's faster than waiting 24-ish hours for gcc7, etc to build). Instructions on how to import your new certificate into your keychain, and how to configure your network settings are available in Wowfunhappy's. So, for the brave, you have 2 options: Install macports and build squid4, then use pacifist to extract wowfunhappys nf from the package linked above and edit it point to /opt/local/etc/squid rather than /Library/Squid, OR (i tested this as well), run squid on another machine (i used 10.6 to test this) and connect to it from Leopard. This workaround makes LWK 100% usable again. Sudo port -v install squid4 +ssl_crtdIt worked! Leopard-Webkit can once again access sites that it had previously not been able to be access.
0 Comments
Leave a Reply. |