Signal and GIPHY
moxie0 on 01 Nov 2016
The latest Signal release for Android includes support for GIF search and browsing. Signal has long supported sending and receiving GIFs, but this is an experiment that allows users to browse, search, and select popular GIFs from within Signal.
GIFs and privacy
GIF search engines like GIPHY, Tenor, and Guggy have made this type of functionality increasingly popular. They provide network APIs that allow an app to easily expose trending and search functionality for GIFs.
For instance, if someone messages you with an invitation, you might want to write back with a message that says “I’m excited.” With integrated GIF search, you could instead do a GIF search for “I’m excited” and send one of the results instead.
Of course, as you type your search, it’s transmitted over the network to the GIF search engine:
http://api.giphy.com/v1/gifs/search?q=I&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+e&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+ex&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+exc&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+exci&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+excit&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+excite&api_key=dc6zaTOxFJmzC http://api.giphy.com/v1/gifs/search?q=Im+excited&api_key=dc6zaTOxFJmzC
This is of some concern. While it might seem silly to worry about GIF search confidentiality, what you search for is in some sense the “content” of your message. Instead of sending “I’m excited,” you searched “I’m excited.” Message content (or anything like it) is always something we want to think carefully about.
An experimental approach
Any practical approach requires that the search term be transmitted to the GIF search engine. Ideally, however, it would be done in a way that doesn’t provide the GIF search engine’s operator with the knowledge of who issued the search.
Some messaging services act as a plaintext proxy for the GIF searches. The app transmits the plaintext search term to the messaging service, which queries the GIF search engine server-side and transmits the results back to the client. While that does hide from the GIF search engine the identity of the user who issued the search, it is actually worse than issuing an unproxied search directly, since the messaging service itself is given plaintext access to both the search term and the GIF the user selects. Obviously, a privacy preserving messaging service should not have access to that kind of plaintext.
The GIPHY API has an HTTPS endpoint which Signal uses to provide a different kind of proxy. When querying GIPHY:
- The Signal app opens a TCP connection to the Signal service.
- The Signal service opens a TCP connection to the GIPHY HTTPS API endpoint and relays bytes between the app and GIPHY.
- The Signal app negotiates TLS through the proxied TCP connection all the way to the GIPHY HTTPS API endpoint.
Since communication is done via TLS all the way to GIPHY, the Signal service never sees the plaintext contents of what is transmitted or received. Since the TCP connection is proxied through the Signal service, GIPHY doesn’t know who issued the request.
The Signal service essentially acts as a VPN for GIPHY traffic: the Signal service knows who you are, but not what you’re searching for or selecting. The GIPHY API service sees the search term, but not who you are.
While this does hide your IP address from GIPHY and your search terms from Signal, there are some caveats. The GIPHY service could use subtleties like TLS session resume or cache hits to try to correlate multiple requests as having come from the same client, even if they don’t know the origin.
Similarly, the Signal service that’s proxying traffic could attempt to measure the amount of data transmitted in order to discern something about the GIFs being retrieved from GIPHY.
We’ll continue to look at things like adding padding or disabling TLS session resume for these requests in order to push things further. We’re evaluating how this works in the Android app, and will extend it to iOS and the Desktop shortly. Try it out!