Forgot your password?

typodupeerror

Comment: Re:Really? (Score 1) 308

by IpalindromeI (#37190980) Attached to: Smartphones: the New Home of Crapware

For your example, have you looked at Our Groceries? My wife and I both use it on Android, but their website says it's available for iPhone, too. It's server-backed, so lists are synced across phones. Obviously I can't say for sure, but I imagine it would work between iOS and Android.
http://www.ourgroceries.com/download

Comment: Re:Google+? (Score 1) 181

by IpalindromeI (#36845308) Attached to: Linux Kernel 3.0 Released
If you've got an Android phone, you can do the following:
  1. Install the Android Debug Bridge on your computer. http://developer.android.com/guide/developing/tools/adb.html
  2. Turn on USB debugging on your phone, and connect it to your computer.
  3. Install Tetherbot http://graha.ms/androidproxy/ on your phone, and start the Socks Proxy Server.
  4. Setup ADB to open a port on your computer that forwards to the port on your phone where the proxy server is listening: "adb forward tcp:5555 tcp:1080"
  5. Set your browser to use localhost:5555 as a proxy server.

Now all your web browsing goes through your phone. If you run Firefox, you can get FoxyProxy to set up URL-based rules for which addresses go through your phone-proxy and which go through your regular company network connection. And no mayo gets on your phone.

Comment: Re:What the....? (Score 1) 545

by IpalindromeI (#36435040) Attached to: Ask Slashdot: Web Site Editing Software For the Long Haul?

It isn't sarcasm. It's a typo that happens to spell another word, so the little squiggly red lines don't appear to let people know they made a misspelling. Also, hardly anyone here bothers to proof-read their posts, as is clear from the common requests for an "edit" button.

So, it's basically down to laziness.

Comment: Re:There is still man-in-the-middle attack (Score 2, Insightful) 152

by IpalindromeI (#33793684) Attached to: GoogleSharing, Now With No Trust Required

Here's the quick rundown:

You contact Google's server through the proxy, and the server sends you Google's public key. This key isn't secret, so it doesn't matter if the proxy gets it, too.

Now you use their public key to encrypt a message telling them the symmetric encryption key you want to use for the rest of the communication. Only Google can decrypt that message, so only you and Google will know the key to use to decrypt the rest of your communications.

A man in the middle attack is only possible if GoogleSharing can either break or guess Google's private key, or the symmetric key you agreed to use after the handshake. Both are very hard to do. So don't worry about it.

The debate rages on: Is PL/I Bachtrian or Dromedary?

Working...