»  Jeff Alexander
»  Eric Arseneau
»  Cristina Cifuentes
»  Gilda Garreton
»  Vipul Gupta
»  Karl Haberl
»  Mick Jordan
»  Roger Meike
»  David Simmons
»  Doug Simon
»  Poorna Udupi
»  Jim Waldo
»  Derek White
Sun Microsystems Laboratories Blogs

January 29, 2010

Eric Arseneau's Blog

My desktop is secure, why should my web app worry?

<p><p>I can see the convenience of a web app for most people. &nbsp;It can be really nice to run anywhere and get access to functionality and data. &nbsp;Although I think it should be done using different tools, web apps can work.</p> <br/> <p>So now, why then would people insist on making web apps so hard to get into? &nbsp;I dont know about the rest of the world, but I don't use THAT many machines. &nbsp;90% of the time I find myself in front of my own desktop and/or laptop. &nbsp;Now these machines are already secured to the level I am happy with, I have my password when I turn on my machine and sometimes put a lock screen on. &nbsp;I should be able to connect to a web site on my personal machine and not have to enter a password, I already did when I came to my machine. &nbsp;Do any of my desktop applications ask me for a password EVERY single time I want to use them? &nbsp;No they NEVER do.</p> <br/> <p>If you want to make a web app like a desktop app, why not do so? &nbsp;Don't force me to login every time for starters.</p> <br/> <p>Even the most simple application that does not require any real security on my machine, Facebook, requires me to log in when I go to it. &nbsp;What could be so important in my facebook that I don't want anyone else to see. &nbsp;Wait, nothing, as Facebook is already all public <img src="http://blogs.sun.com/images/smileys/smile.gif" class="smiley" alt=":)" title=":)" /> &nbsp;Now would I want to have someone else change my status without my knowledge, no, but then I have physical control of my machine, so they can't.</p> <br/> <p>Most people would say, this is not a problem Eric, as the browsers now all remember my user id and password to all websites. &nbsp;Does THIS not point to the fact that there is a flaw somewhere? &nbsp;Let me see, the reason we have passwords is so that our access to services can be perceived as secure. &nbsp;Well what difference is there in a service remembering who I am and logging me in directly, then my browser remembering my user passwords. &nbsp;In terms of security I see no real difference. &nbsp;But in terms of usability, its HUGE. &nbsp;Lets see, I have a need for a service, I go to it, have the cognitive dissonance of trying to remember my password or reading screen asking me to login, then hopefully get back to what I actually wanted to do with the service. &nbsp;As remember, a number of these services don't even have the decency to remember WHERE you were going to in the first place, they just wanted you to feel secure. &nbsp;Well I don't feel any more secure than if you logged me on, as the password came from my browser anyway <img src="http://blogs.sun.com/images/smileys/smile.gif" class="smiley" alt=":)" title=":)" /></p> <br/> <p>I think what would fix things for me would be add a simple checkbox &quot;Log me in ALWAYS&quot;. &nbsp;And provide the appropriate implementation. &nbsp;If its done via cookies and the browser has cookies turned off, then maybe we need a separate system to capture secure information about our login status with sites.&nbsp;</p> <br/> <p>My other favorite is the timeout feature of a login. &nbsp;I was entering expenses the other day, took me some time to get through some gnarly details on a collection of receipts. &nbsp;When I came back to the browser to continue entering details, the browser session presented me with a kindly worded message &quot;For your own security, this session has timed out&quot;. &nbsp;Well thanks but NO thanks. &nbsp;I lost some data here as I had already started the expense report. &nbsp;What part of security are you trying to help me with? &nbsp;First, I had to VPN into my corporate network to get to the site. &nbsp;Then to get into the site I had to log in with a user id and password. &nbsp;So these two levels of security are not good enough?&nbsp;</p> <br/> <p>Now, you would say, what about when I need to use a public machine? No problem, login and don't specify the option to keep me logged in ALWAYS. &nbsp;Remember for me, this happens less than 1% of the time I spend in front of a computer. &nbsp;So why hit me 100% of the time with inconvenience <img src="http://blogs.sun.com/images/smileys/sad.gif" class="smiley" alt=":(" title=":(" /></p> <br/> <p>Single signon might work, but again I think its a workaround to a problem that should not exist at all. &nbsp;As we've seen with single signon, various parties want THEIR technology to win, so there is more than one option for a web site to choose from. &nbsp;Here is a NOVEL idea, don't create the need for single signon in the first place. &nbsp;If all websites allowed us to login for ever, then the need would not be there for single signon products.</p> <br/> <p>Now, I DO realize that single signon, could be seen as useful when you go to another machine. &nbsp;I'll buy that, however then having different options for single signon on dont seem as bad, as I wont need to use them very often.</p> <br/> <p>Can we start a compaign out there in the wild for &quot;Login ALWAYS&quot;, &quot;Trust my desktop!&quot;, &quot;Dont make me login to my desktop apps every time, anytime <img src="http://blogs.sun.com/images/smileys/sad.gif" class="smiley" alt=":(" title=":(" />&quot;</p></p>

by eric on January 29, 2010

January 27, 2010

Jeff Alexander's Blog

Did you mean...?

Just an example of how search engines use statistics to help them "understand" words. Until today, iPad wasn't a word (or at least, it wasn't a name). If you go to Google (for now at least) and search for ipad, you see something like this:

iPad appears very infrequently but is similar to a word that appears very frequently - "iPod". iPad appears infrequently enough and the discrepancy between the two is large enough, that Google assumes I probably made a mistake typing iPad. Google's actual algorithm for spelling corrections is more complicated than this, but this is the basic idea behind spelling correction in search engines. As iPad starts to show up all over the web, Google will stop making that suggestion since iPad will become more plausible (statistically) as a word. Or maybe somebody at Google will just add iPad to an exception list so it stops making the suggestion.

As a side note (no pun intended) the sponsored ads on the side of the page are all for the iPAQ as various vendors have put in bids to get listed for ipad as a misspelling of ipaq. In this case, I'm fairly sure, these are strictly companies that asked their ads to be shown for the word ipad (as well as ipaq).

by Jeff Alexander on January 27, 2010