3 ms·
This is an interesting workaround. People forget that part of the point of different colors for iMessage vs SMS was to indicate that iMessage is encrypted and
by runako 7y ago
This is an interesting workaround.
People forget that part of the point of different colors for iMessage vs SMS was to indicate that iMessage is encrypted and SMS isn't. It's also a handy marketing thing, but there is a technical justification for making a visible distinction.
AirMessage is basically a proxy that strips encryption for Android devices:
"AirMessage leverages the power of your Mac computer in order to route messages to and from Apple's iMessage servers. The server is to be installed on a computer at home, and will pass messages to and from your smartphone to allow the usage of iMessage and other installed services."
- untog 7y agoDoes it re-encrypt them when sending, though? I would have to assume they've at least looked at doing that, otherwise it's a giant security hole.
- runako 7y agoSee my peer response. I would imagine all traffic from the Mac<->other device is encrypted. You're responsible for securing the Android<->Mac link.
- dkonofalski 7y agoI don't think that's what's happening here. I think AirMessage is just functioning as an iMessage client by using the Messages app on the Mac as a proxy. It would be no different from sitting physically in front of the computer. You can only read the messages off the screen and you can only send messages through Message itself.
- runako 7y agoI think we're saying the same thing. :-) I would imagine that the AirMessage Android app is actually in communication with the AirMessage server on your Mac. It uses some automation (perhaps via something like https://github.com/shusain93/OSXMessageProxy https://github.com/shusain93/OSXMessageProxy) to talk the the Messages app. The connection is encrypted from there to the other side, as if you were sitting in front of your Mac. This happens in reverse the other way. Hacky, and now you own the weak links in the E2E encryption chain. But a neat workaround, in a pinch.
- dkonofalski 7y agoYes, it looks like we are. :)