Securing 3rd-Party SSL Web Sites With Skweezer
Recently, dotMobi released a study that suggests end-users desire more practical mobile content rather than consumable (entertainment) content. Frankly, our company has known this for awhile as we’ve been analyzing the behaviors of general web use since 2004. Since then, one thing we quickly learned—which has helped shape our product over the years—is end-users want to access content transactionally. That is, users want to get to the part of a Web page that feeds their interest or activity. People, generally, don’t sit around browsing on their phones for the sake of browsing. Therefore, we’ve adopted the position that people are finding more on mobile Web than they are browsing.
This has helped us shape innovation “firsts” like our Find-in-Page™ feature, that jumps the user to the keywords they are looking for that are carried over from a search query. Hit highlighting is another “helper” to let people identify what they are looking for. This also seems to be validated by the much higher-than-normal click-through rates from our mobile ads with search partners.
One of those transactional pieces that’s mentioned in the dotMobi survey is online banking. Unless the banking site has a mobile interface with SSL, most phone users would need a transcoding proxy to access the site in order to gain access. (This would be nearly 90% of the phones in the world, BTW.) As far as mobilizing 3rd-party Web sites go, Skweezer is the only transcoder that I know of (also since 2004, by the way) that keeps a fully SSL-encoded transaction from beginning-to-end on behalf of a user. Since Skweezer isn’t a gateway service hosted directly in an operator’s datacenter like Sprint, Skweezer can talk to any Web site—through SSL—and encode it from start to finish where it’s available.
For users using dotMobi’s recently acquired Mowser—or even the big guys like Google or Yahoo!… none of these services do that. Which is curious to me why dotMobi would bring up the notion of accessing anything securely. For example, if you wanted to check your Union Bank of California account online in Mowser, you would not have an end-to-end SSL connection. Notice that when you go to a secure page in Mowser, the Mowser protocol is “http” wrapped around Union Bank’s “https”…
Mowser Mobile Web Transcoder (Phonifier-adapted)
That’s scary. So, you enter all your personally identifiable info for the bank and it goes to Mowser as clear text before they securely send it to UBOC! Or in the case of Google, they just punt…
Google Mobile Web Transcoder
Google doesn’t even allow SSL connections on their transcoder. Whether they can’t surmount the 80/20 “wall” of transcoding state—or if their legal department feels that it’s somehow a liability—they just have a user go directly to the site, leaving the end-user hung out to dry. Yahoo! is similar, but they don’t even allow you to connect to them in the first place via SSL. Whether it’s Novarra (their partner) not being able to support it, or again, a business reason, users are left with no access to 3rd-party SSL sites…
Yahoo! Mobile Web Transcoder (Novarra)
If this isn’t quite clear, another way you can look at this is there are three parts to any given transaction: the end-user, the transcoding proxy, and the content site. The aforementioned proxies don’t have a secure connection between them and the end-user when the proxy is fetching secure information:

But Skweezer, on the other hand, does. And it does so with up to 256-bit encryption (depending on what your browser supports) to create an end-to-end SSL transaction of 3rd-party websites:

So, if you’re going to access content transactionally, i.e. your bank balance, etc, through a transcoder, be sure the information you’re providing isn’t being sent with just regular HTTP regardless of whether the intended URL is in SSL.
Posted byy Kevin Perkins























