Hmm. What would happen if you signed in somewhere else in the OS as a way of getting a login prompt, then used that within iTunes? This is the method that gets iMessage working on Mavericks.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Other Aqua Proxy: Fix connection issues on OS X 10.6 – 10.9.
- Thread starter Wowfunhappy
- Start date
-
- Tags
- networking software
- Sort by reaction score
Hmm. What would happen if you signed in somewhere else in the OS as a way of getting a login prompt, then used that within iTunes? This is the method that gets iMessage working on Mavericks.
GitHub - startergo/tls12-snow-leopard-merge at feature/force-tls12-all-setters
TLS 1.2 — macOS 10.6 Snow Leopard Security.framework development - startergo/tls12-snow-leopard-merge
github.com
seems to be startergo's fraken-security.framework. Do be aware that around this period there was the infamous "goto fail" bug. One of the docs said "Guardrails — versions NOT to use", but it's not clear what version it ended up using instead. Also at least modern Security.framework is used for more than just TLS
retta283
macrumors 68040
Do you know by chance when iMessage login got messed up in Mavericks? I have been logged in for about 5 years and don't recall having any problems at that time. I know that in Sierra iMessage refuses to use the account logged in anywhere else for me, not sure why, but logging in directly in the app works still. Curious where in the system I might try to see if it'd work.
The issues started some time in the summer of 2024.
How do I sign into iMessage on OS X 10.9 Mavericks?
I use Mac OS X 10.9 Mavericks because it's my favorite version of OS X. I accidentally signed out of the Messages app (iMessage), and now I can't sign back in. The first time I tried signing in, this
Since iirc Sierra postdates the introduction of two-step authentication I don't think any of this will work (you won't get a code you can append to the end of your password).
(If you have more questions it might be good to move to a separate thread so we can keep this one focused on AquaProxy.)
Hi, I just pushed an update which contains a critical security fix. Please re-download from mavericksforever.com as soon as possible.
I am working on a successor to Aqua Proxy which will fix HTTPS connections without a proxy server. (It will a port of this project for iOS to the Mac). I will eventually make a new thread for this when it's ready.
But in the meantime, an important question—are there any Snow Leopard users who use PPC apps (via Rosetta) which need Aqua Proxy to work? If so, which one(s)? If no one needs it, I will skip Rosetta support.
But in the meantime, an important question—are there any Snow Leopard users who use PPC apps (via Rosetta) which need Aqua Proxy to work? If so, which one(s)? If no one needs it, I will skip Rosetta support.
startergo
macrumors 603
I have not yet uploaded the latest patches yet. Plus there is too much junk yet needs cleaning. But the binary has been tested currently on a Mac mini 3.1 and UTM SL.
GitHub - startergo/tls12-snow-leopard-merge at feature/force-tls12-all-setters
TLS 1.2 — macOS 10.6 Snow Leopard Security.framework development - startergo/tls12-snow-leopard-merge
seems to be startergo's fraken-security.framework. Do be aware that around this period there was the infamous "goto fail" bug. One of the docs said "Guardrails — versions NOT to use", but it's not clear what version it ended up using instead. Also at least modern Security.framework is used for more than just TLS
DurltazorOSXPower
macrumors regular
For my part, I only use the rosetta for games, but.. what about powerpc users? I think it's cool if there is a possible future update of the next aqua proxy for these machines.
PowerPC hardware support will not be happening for now, just trying to match what Aqua Proxy can already do today.
DurltazorOSXPower
macrumors regular
maverick28
macrumors 6502a
I think renaming this thread to reflect all macOS versions up to Mojave is becoming more urgent: Dictionary's Wikipedia in Mojave is effectively incapacitated. The constant changes they play with on the Wiki dev team broke it. Do Aqua Proxy and the Wikifix work with 10.14?
I'm sorry, I have no interest in spending time on any version of macOS later than 10.9. If someone else would like to take the code and build on it, that would be really cool, but it won't come from me.
maverick28
macrumors 6502a
Well, the installer won't run above 10.10, but you could bypass that.
AquaProxy uses a heuristic to determine which traffic should be MiTM'd vs passed through which will be wrong on 10.11+, where modern protocols are natively supported. So you'd have to use -force-mitm, which would interfere with certificate pinning, which is also significantly more common on newer versions of macOS.
Other than that, I don't know what would happen. The code is just Go and should be basically OS agnostic. It's possible the legacy OS patches would interfere with the binary running but you don't need those anyway, so just recompile with whatever version of Go you like.
AquaProxy uses a heuristic to determine which traffic should be MiTM'd vs passed through which will be wrong on 10.11+, where modern protocols are natively supported. So you'd have to use -force-mitm, which would interfere with certificate pinning, which is also significantly more common on newer versions of macOS.
Other than that, I don't know what would happen. The code is just Go and should be basically OS agnostic. It's possible the legacy OS patches would interfere with the binary running but you don't need those anyway, so just recompile with whatever version of Go you like.