Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Security Businesses Encryption Google Privacy The Internet Communications

A Good Reason To Go Full-Time SSL For Gmail 530

Ashik Ratnani writes with this snippet from Hungry Hackers: "A tool that automatically steals IDs of non-encrypted sessions and breaks into Google Mail accounts has been presented at the Defcon hackers' conference in Las Vegas. Last week, Google introduced a new feature in Gmail that allows users to permanently switch on SSL and use it for every action involving Gmail, not just authentication. Users who did not turn it on now have a serious reason to do so, as Mike Perry, the reverse engineer from San Francisco who developed the tool, is planning to release it in two weeks."
This discussion has been archived. No new comments can be posted.

A Good Reason To Go Full-Time SSL For Gmail

Comments Filter:
  • Re:Just for Google? (Score:4, Interesting)

    by clone53421 ( 1310749 ) on Tuesday August 19, 2008 @11:44AM (#24659475) Journal

    Not quite ALL intents and purposes. If I want to change my password, I still need to know my current password. Although somebody who steals my SID can read my mail they can't change my password and lock me out.

  • Re:Ow ow ow. (Score:1, Interesting)

    by Anonymous Coward on Tuesday August 19, 2008 @11:47AM (#24659517)
    People usually treat phrases as words and don't really pay attention to their origin or what the individual parts of the phrase mean.
  • Re:Just for Google? (Score:3, Interesting)

    by Loki_1929 ( 550940 ) on Tuesday August 19, 2008 @11:53AM (#24659601) Journal

    There's a sizable portion of the general public that doesn't want to be bothered having to remember any passwords for anything. They simply want to click a button and have it work.

    You'd have better luck explaining the security implications of such a system to a chimp.

  • Re:Just for Google? (Score:1, Interesting)

    by Anonymous Coward on Tuesday August 19, 2008 @11:59AM (#24659681)

    I know this is being pedantic, but you are missing a period after the quote or you should have moved it outside the quotes. The urge is too strong since you seem to be so happy harping on missing periods...

  • by thomasdz ( 178114 ) on Tuesday August 19, 2008 @12:02PM (#24659731)

    I can understand that back in the web's "stone age" (mid 1990s), having HTTPS for every web site would have seriously slowed down all the computers due to CPU usage, but nowadays is there any real good reason that the whole web can't be HTTPS?
    With all the government and ISP snoopings going on, I'm surprised that at least some sites haven't gone that way.
    (or is it that embedded browsers like on cell phones can't do SSL?)

    TDz.

  • by Anonymous Coward on Tuesday August 19, 2008 @12:03PM (#24659735)

    isnt gmail the only webmail provider that offers this? Why are you not complaining about hotmail, yahoo, etc.

  • by origamy ( 807009 ) on Tuesday August 19, 2008 @12:20PM (#24660023) Homepage
    I don't understand why does someone need to prove a security vulnerability by releasing the tool?
    By releasing this tool he will make it available for anyone with bad intentions to implement it. Weeks later we will have issues all over the place because we did not teach our grandparents to enable the checkbox in gmail; or the vulnerability is exploited in other webmail clients. By then, the botnets will be hijacking Gmail accounts to send Spam to everybody
    So, really, who benefits of the release of this tool?
  • by blueg3 ( 192743 ) on Tuesday August 19, 2008 @12:23PM (#24660075)

    Google, etc., were notified of this vulnerability a year ago and have not acted on it. Someone with bad intentions could implement it easily using the description of the vulnerability anyway -- a publicly-available working tool will highlight the importance of fixing this problem.

  • by DuSTman31 ( 578936 ) on Tuesday August 19, 2008 @12:25PM (#24660125)

    One thing that I find somewhat counterproductive is that browsers do not save files sent over SSL in their caches.

    It's sensible, I suppose, to assume that if something's sent over an SSL channel that it's sensitive and therefore shouldn't be saved, but it would give a speed and bandwidth efficiency hit which would deter usage of SSL for everyday browsing.

    You could, of course, have the HTML transmitted over SSL and the supporting images over plain HTTP, but then the browser will scare people by warning that not all content on the page is secure..

    I think browsers should start looking at encrypting their cache files, so that stuff such as SSL can be accommodated without breaking caching.

  • by Atriqus ( 826899 ) on Tuesday August 19, 2008 @12:47PM (#24660501) Homepage
    I found a firefox add-on that makes the browser behave a bit more rationally called perspectives: http://www.cs.cmu.edu/~perspectives/ [cmu.edu]
  • Re:A few notes... (Score:5, Interesting)

    by Dolohov ( 114209 ) on Tuesday August 19, 2008 @01:03PM (#24660761)

    Mike Perry did a great public service by making this tool and making it available.

    WTF? No he didn't. Pointing out the vulnerability is a a public service, yes. Giving a talk where he outlines the problem? Also a public service. Distributing the means for anyone to make use of this vulnerability (ESPECIALLY when so many major vendors aren't prepared for it yet) is not a public service anymore. It's just arming script kiddies. Ralph Nader was able to do plenty of good without going around ramming into Chevy Corvairs to somehow "drive home" the need for a fix.

  • by legirons ( 809082 ) on Tuesday August 19, 2008 @01:43PM (#24661409)

    "Last week, Google introduced a new feature in Gmail that allows users to permanently switch on SSL and use it for every action involving Gmail, not just authentication."

    Unfortunately not available for anyone who has their own domain's email hosted at google :(

  • Re:Just for Google? (Score:3, Interesting)

    by corbettw ( 214229 ) on Tuesday August 19, 2008 @02:24PM (#24661995) Journal

    But if a site is not signed at all, then it must be safe, huh?

    An unencrypted site is less dangerous than a self-signed one because the former isn't advertising that it's safe; the latter is. It's presenting the appearance of security, with the reality of none. You're much better off thinking you're insecure, and acting appropriately, than assuming you're secure, and not realizing you've just given your bank account information to a phisher.

  • Re:Just for Google? (Score:4, Interesting)

    by rah1420 ( 234198 ) <rah1420@gmail.com> on Tuesday August 19, 2008 @03:30PM (#24663121)

    So why the fuck haven't I had mod points? This might be one of the most interesting things I've read on /. in a long time. If ever.

    Yeah, so sue me. I don't get out much.

  • Re:Just for Google? (Score:3, Interesting)

    by kklein ( 900361 ) on Tuesday August 19, 2008 @10:10PM (#24667601)

    Easy. The lexicogrammar of "begs the question" makes far more sense in its common usage as being synonymous with "raises the question." Some situation seems to be begging for someone to ask a particular question. The original meaning of this idiomatic expression, having to do with circular logic, does not as clearly follow from the individual meanings of those words. Also, to be honest, I have never, ever heard a usage of the original meaning. Ever.

    I am an applied linguist by training and trade, and you know what? I have heard this "incorrectly" used at conferences. Face it. The meaning has changed. No one even knows what the original was.

    "Intensive purposes" is different because it makes no sense. When we say "for all intents and purposes," we are making a large, sweeping, general claim. This is the opposite of what is implied by "intensive purposes," which would denote some sort of specific, focused usage of whatever it is we're talking about.

    Also, someone who uses "intensive purposes" needs their hearing checked. There is no /v/ in there. When someone uses "intensive purposes," it implies that they not only don't listen closely but that they also don't even think about what they are saying. It implies a sort of illiteracy. It does not reflect well on someone's education, because educated people do not talk like that.

    Educated people do, however, use "begs the question" "incorrectly." So it gets a pass.

    Language is one of the clearest tribal identifiers. Standard usage identifies to others that you are the same tribe and affords you the benefits thereof. We can yammer on about elitism, but that's just plain how it works. In every society. Learning to use language in a standard way tells others who have done the same that you are brethren and, like them, have spent the time and effort "correcting" your behavior.

    None of this is really about "correct" usage, it's about "standard" and "accepted" usage. "Begs the question" passes; "intensive purposes" doesn't. The former is an interesting evolution of the usage of an idiomatic phrase; the latter, indication that someone is kinda a moron.

  • Re:Just for Google? (Score:3, Interesting)

    by complete loony ( 663508 ) <Jeremy@Lakeman.gmail@com> on Wednesday August 20, 2008 @12:22AM (#24668691)
    Sure you could encrypt traffic between client and server, but if you can't verify the identity of the server during key exchange, you can't prevent a man-in-the-middle attack which makes the encryption useless.

This file will self-destruct in five minutes.

Working...