MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  June 2012

MSUNAG June 2012

Subject:

Re: LinkedIn Password hacked.

From:

David McFarlane <[log in to unmask]>

Reply-To:

David McFarlane <[log in to unmask]>

Date:

Thu, 14 Jun 2012 16:05:56 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (184 lines)

Well, if we are going to discuss password 
generation and strength, then someone has to trot 
out the two canonical references, which I do now:

http://xkcd.com/936
https://www.grc.com/haystack.htm

-- dkm


At 6/14/2012 03:58 PM Thursday, STeve Andre' wrote:
>Teach people to pick phrases from their favorite songs or poems, and
>you get great passwords:
>
>     now is the time for all good men to come to the aid of their country
>
>makes
>
>      nittfagmtcttaotc
>
>take an i make a 1, etc, and you've further obfuscated things.  Longer
>is better and I've seen lots of people take stanzas from things and
>create truly monstrous pw's.
>
>I teach people to make their own passwords that way.  Judging from
>the clackclackclack... noises when logging into things, it's been working.
>
>Use a system that generates passwords for you, and they wind up on
>postit notes.  Last week I saw just that for an account which controls
>a lot of money.  A LOT.  I've seen this so many times when "good" pw's
>are enforced on people.
>
>Passwords certainly are a pain, but they can be managed.
>
>--STeve Andre'
>
>On 06/14/12 09:11, Hoort, Brian wrote:
>>Compared to using the same password for all 
>>their websites, which is what our users do that 
>>aren’t using a LastPass like service, using 
>>LastPass to generate random, long strings for 
>>passwords and storing them in an encrypted blob 
>>(LastPass does not have the key) is far more 
>>secure.  This very event with LinkedIn 
>>demonstrates this. LinkedIn lost their password 
>>hashes.  This is most dangerous to a typical 
>>user (97%?) who has reused passwords across web 
>>sites.  Had they been using LastPass (or a 
>>similar service) to generate random, different 
>>passwords across sites, they would be in a far 
>>more secure position. While there is the 
>>theoretical problem of the encrypted blob being 
>>compromised, LastPass would have had to also 
>>fail in their implementation of encryption for 
>>that loss to be dangerous. LastPass, used 
>>properly to generate passwords, is a big 
>>net-win in security for the vast majority of people.
>>
>>Brian Hoort     |     517-355-3776
>>ANR Technology Services, MSU
>>
>>From: Kramer, Jack 
>>[<mailto:[log in to unmask]>mailto:[log in to unmask]]
>>Sent: Wednesday, June 13, 2012 5:26 PM
>>To: <mailto:[log in to unmask]>[log in to unmask]
>>Subject: Re: [MSUNAG] LinkedIn Password hacked.
>>
>>Right, I get that. If you use them as a 
>>password manager you've definitely increased 
>>your attack surface. I would consider something 
>>like 1Password less attackable since the 
>>password database is kept local. However, this 
>>LinkedIn check utility isn't giving them your 
>>password­it's just doing the SHA-1 compute on 
>>it and then comparing that hash to a list of 
>>hashes that are already out there. I mean, I 
>>guess someone could theoretically compromise 
>>the server hosting that utility and replace the 
>>code with something that captures your password 
>>in plaintext and sends it off to some nefarious 
>>third party, but with no account name (or way 
>>to capture such) I'm having trouble seeing how that's useful information.
>>
>>----
>>Jack Kramer
>>Manager of Information Technology
>>Communications and Brand Strategy
>>Michigan State University
>>w: 517-884-1231 / c: 248-635-4955
>>
>>From: STeve Andre' <<mailto:[log in to unmask]>[log in to unmask]>
>>Reply-To: STeve Andre' <<mailto:[log in to unmask]>[log in to unmask]>
>>Date: Wednesday, June 13, 2012 5:11 PM
>>To: 
>>"<mailto:[log in to unmask]>[log in to unmask] 
>>" <<mailto:[log in to unmask]>[log in to unmask]>
>>Subject: Re: [MSUNAG] LinkedIn Password hacked.
>>
>>My distrust stems from having some other entity get your password.
>>
>>A single point of failure, and you are trusting them to do it right, and
>>not be compromised.  So yes, there *is* an increased attack surface
>>here: you are adding to the complexity of things and trusting that
>>they are secure.  To me, that's increasing the attack surface.  I
>>don't know what else to call it.
>>
>>--STeve Andre'
>>
>>On 06/13/12 17:05, Kramer, Jack wrote:
>>Are you objecting to the concept of a password 
>>manager utility or the check site that Matt 
>>posted? I agree that password managers 
>>represent a single point of failure, though 
>>that single point is at least easier to protect 
>>than the many points of weak password we seem 
>>to end up without any sort of manager; however, 
>>the LinkedIn check page they have just compares 
>>the SHA-1 hash of any text you enter with the 
>>known leak of SHA-1 hashes and tells you if 
>>there's a match. There really isn't an attack 
>>surface there considering you're perfectly 
>>welcome to download that hash leak yourself and 
>>run all the comparisons your heart desires on it.
>>
>>----
>>Jack Kramer
>>Manager of Information Technology
>>Communications and Brand Strategy
>>Michigan State University
>>w: 517-884-1231 / c: 248-635-4955
>>
>>From: STeve Andre' <<mailto:[log in to unmask]>[log in to unmask]>
>>Reply-To: STeve Andre' <<mailto:[log in to unmask]>[log in to unmask]>
>>Date: Wednesday, June 13, 2012 4:51 PM
>>To: 
>>"<mailto:[log in to unmask]>[log in to unmask] 
>>" <<mailto:[log in to unmask]>[log in to unmask]>
>>Subject: Re: [MSUNAG] LinkedIn Password hacked.
>>
>>On 06/13/12 16:30, Carl Bussema III wrote:
>>Actually LastPass is a well-known and respected security tool, so I
>>would actually trust them not to compromise the password. I actually
>>tried to decipher the HTTPS session with Fiddler, but Chrome +
>>LastPass detected a man-in-the-middle and wouldn't proceed.
>>
>>And because apparently some people need to be put out of their
>>paranoia, I went ahead and just used my regular developer tools and
>>found exactly what I suspected:
>>
>>I posted the password "asdf" to their form. I then watched the AJAX
>>request (which because it happens client side is unencrypted before
>>transmission) ... and you know what they are sending to their servers?
>>THE HASHED PASSWORD. It's not like it's hard to SHA1 a string
>>in JavaScript.
>>
>>So the send the hash to the server, check the list of "known bad
>>hashes" (which is what the hackers have published) and tell you if
>>your password hash matches a known compromised hash.
>>
>>It's really about as safe as you can possibly imagine and a great
>>tool. Yes, we should be careful about inputting passwords onto strange
>>sites, but you should also do your due diligence and check if the site
>>might actually be legit.
>>
>>/rant
>>
>>
>>
>>Passwords are about as fragile a thing as there is today: users
>>pick and display idiot pw's, and system (often) have bad security
>>measures in place which don't really work.
>>
>>LastPass is likely an up-front honest entity, but that isn't the reason
>>why they shouldn't be used.  Trusting another entity with your pw
>>increases the attack surface of the product you are testing.  As
>>good as LastPass is, your are now trusting them to be really secure.
>>That they throw away the string you enter is good, but that means
>>that vandals know just where to look if they were trying to break
>>that system.
>>
>>This is a philosophical thing.  Minimizing the places on the net that
>>have pw's is a good thing.
>>
>>--STeve Andre'

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager