Playing hooky…

November 3rd, 2010, 5:26pm by Kelvin


… For the Giants parade.




10 Responses to “Playing hooky…”

  1. Jake Says:

    I would’ve been disappointed if you didn’t! Nice that you could go to your first World Series Parade together.

  2. Mike Says:

    Nice that the whole city of SF could go to its first World Series parade together! Congratulations!

    It’s also gotta be helpful to home prices to be near AT&T Park, home of the World Champion San Francisco Giants!

  3. Kelvin Says:

    Oh, it was a lot of fun. Beautiful day in the city, incredible crowd, the streets awash in orange. Lucas was terribly impressed by all the horns people were carrying around (I didn’t want to teach him “vuvuzela”). We didn’t have a great view, but Lucas saw what he could from my shoulders (made me think of Derrick and Brandon’s Thankgiving parade).

    Oh, you guys will get a kick out of this… I made last-minute enroute decisions to NOT drive into the city and jump onto a train based on Twitter searches Serena was doing at work. Figured out which train stations had parking, which stations were getting passed over by trains that were full, which stations had long lines at the ticket booths, etc.

  4. Jake Says:

    Wow, after 15 years the internet finally proves itself to be useful!

  5. Kelvin Says:

    I wouldn’t say it’s the first time– I just paid my credit card bill using my Wells Fargo app!

  6. Mike Says:

    …hopefully over 3G, not an unsecured, Firesheep-accessible wifi hotspot!

  7. Kelvin Says:

    Well actually, Firesheep wouldn’t be able to do anything with the SSL-encrypted data stream from banking apps/websites. It’s only unencrypted logins that need worry us (facebook, twitter, pyslent). Actually, what’s disturbing to me is that these websites seem to be constantly exchanging login info (in clear text), rather than only at the initial login page. Am I understanding that correctly?

  8. Jake Says:

    No, it’s not that. Instead, Firesheep intercepts the cookie being sent in the clear. They duplicate the cookie, then impersonate the target.

    The EFF has a nice Firefox Plug-In that will default Facebook, Google (mostly) & Twitter to https, but I doubt it’s fool-proof. Plus, Yahoo/Flickr is in the clear.

  9. Kelvin Says:

    When I log out of Yahoo and try to sign back in, the sign in page is https. But once logged in, the webpages are all in the clear. And is that a problem, then? Yikes.

    When are these identifying cookies sent? Constantly (with every click/refresh)? or only on the first browser instance of going to the site?

  10. Jake Says:

    Pretty much constantly. So yeah, using WiFi is now opening your account for spoofing.

    This will help a bit. But even if you use https on Google, Maps is still http. https://www.eff.org/https-everywhere

Leave a Reply


Copyright © 2019 The Board. All Rights Reserved.
No computers were harmed in the 2.303 seconds it took to produce this page.

Designed/Developed by Lloyd Armbrust & hot, fresh, coffee.