These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

Dear CCP, get rid of your cache of old passwords.

First post
Author
Scrapyard Bob
EVE University
Ivy League
#41 - 2012-04-27 12:19:39 UTC
Hannott Thanos wrote:
l2F¤siQa = bad password (because you have to write it down, and it's too few characters)
MyHorseIsActuallyAPony = retardedly good password (Long and makes no sense, so not in a dictionary, and you already remembered it for at least a few days just by reading it now)

Changing passwords often = bad (because you make short ones to remember them, and after a while you start writing them down)


It's a bit of a myth that writing down the password is automatically bad. Most people inherently understand controlling access to information that is written down on a sheet of paper. They can fold it over to keep it hidden from prying eyes, they can tuck it away in their wallet/purse, or keep it in a locked box/drawer.

What you have to do is train them to (a) not put it somewhere silly like under the keyboard or in an open desk drawer and (b) that they are legally responsible if bad things happen due to the password leaking.
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#42 - 2012-04-27 12:26:51 UTC  |  Edited by: Steve Ronuken
Edit: ability to read = minimal

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter

Barakach
Caldari Provisions
Caldari State
#43 - 2012-04-27 12:38:34 UTC
leviticus ander wrote:

32 BYTE salt? or 32 bit salt? 32 bytes would probably chock a lot of computers out there, and would cause the authentication server to hang itself. 32 bit, while decent is a little weaker than I'd expect for anything decently modern, I would probably go with 56 or 64 bit, light enough for mass authentication, but strong enough to seriously deter most malicious users.
and yeah, people clicking through warning boxes and generally being totally ignorant of the basic function of a computer is what's causing most issues today.


32bytes is nothing. SHA512 has a performance about 100MB/core. Assume 32bytes for the password string(on the large end) and another 32bytes for the salt, that's ~1.6mil hashed passwords per second, ignoring SHA512 object creation time.

Not only would your DB not be able to keep up, but a 10Gb link would have a hard time. Actually, most single cores cannot handle 10Gb/s of network stack. You would actually be spending more CPU time handling packets to feed the SHA512, than actually computing SHA512.

I admit that there are many other variables like allocating a buffer to store the concatenated salt+string and a myriad of many other things, but CPU time is not an issue.
Jafit
Caldari Provisions
Caldari State
#44 - 2012-04-27 15:44:27 UTC
Francisco Bizzaro wrote:
Hannott Thanos wrote:
Jafit wrote:
Hannott Thanos wrote:
To emphasize. "MyHorseIsActuallyAPony" takes 9.1804 × 10^41 Years to solve with a dictionary attack. that's over 900.000.000.000.000.000.000.000.000.000.000.000.000.000 years. Good luck with that


How about MyLittlePonyFriendshipIsMagicApplejackPinkiepieRarityFluttershyRainbowdashTwilightsparkle as a password?

I'm not saying that's my password...

...I'm saying that's my password.


4.800.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.0000.000.000.000.000 years-ish. Should be doable, right?

No, you just have to apply a little AI.

Just look at him: square jaw, crew cut, air force shades, Test.

I would have guessed it on the third try.


I look like this in real life.

Check out this beta dude, I bet he doesn't even lift.
Mr Kidd
Center for Advanced Studies
Gallente Federation
#45 - 2012-04-27 16:07:45 UTC
CCP Sreegs wrote:
This will be reviewed when we institute the two factor option in the next couple of months.


Is that the next couple of months this year or last year? Joking....I'll just assume you guys are working hard to get it going soon(tm).

Don't ban me, bro!

Zed Jackelope
Pator Tech School
Minmatar Republic
#46 - 2012-04-27 23:27:09 UTC
1. "What ifs" What if someone is able to get a copy of the used passwords, encrypted, and some breakthrough tomorrow allows them to be easily deciphered?

2. Re-use. I cannot say what others do, but I have separate sets of passwords for differing services. I use 'boogers' for pretty much any crap site I don't care about. Same with games, all my games use the same couple of passwords. However, its my choice to use those same passwords. And as I feel I take enough care with my browsing not to get key logged, I feel there's absolutely no difference between reusing old passwords and someone's silly mention of stringing a couple of random words into a password that's never changed?

Taking 1 and 2 into account, with ALL your old EVE passwords saved... how many of you are screwed if tomorrow some magic fairy quantum computer dust allows some script kiddy to the list of every password everyone in EVE has ever used? Ever.

3. Password reset. Its annoying, but with 30 mackinaw accounts, eventually I do forget a password.. this just means I have to go through the whole retrieval process. And with this "added security enhancement", instead of simply cycling between 2+ passwords.. I have to make up and remember an entirely new one.

Conclusion: Its my account, my choice. You can warn the mouth breathing porn clickers all day, but if I choose of my own free will to reuse an old password, CCP shouldn't be stopping me, nor storing my old ones.

Just want to say EVER one more time.
Ai Shun
#47 - 2012-04-27 23:53:16 UTC
Zed Jackelope wrote:
how many of you are screwed if tomorrow some magic fairy quantum computer dust allows some script kiddy to the list of every password everyone in EVE has ever used? Ever.


About the same number that would be screwed when a psychic predicts our passwords. Maybe a bit more though.
Barakach
Caldari Provisions
Caldari State
#48 - 2012-04-28 15:36:48 UTC
Zed Jackelope wrote:
how many of you are screwed if tomorrow some magic fairy quantum computer dust allows some script kiddy to the list of every password everyone in EVE has ever used


Might as well stop going to work to enjoy today, because an asteroid may hit tomorrow and kill everyone.

My post makes the assumption CCP is using industry standards.
Ntrails
State War Academy
Caldari State
#49 - 2012-04-28 15:49:59 UTC
Jonas Xiamon wrote:

They're storing an encrypted version of your password, which is virtually useless.



That is not at all true. The issue is that when someone has downloaded a database of salted and hashed passwords there are no limits to the brute force attacks they can use to get the original password - they can test hundreds of thousands of combinations a minute with a decent computer set up.
Nariya Kentaya
Ministry of War
Amarr Empire
#50 - 2012-04-28 16:54:38 UTC
Scrapyard Bob wrote:
Hannott Thanos wrote:
l2F¤siQa = bad password (because you have to write it down, and it's too few characters)
MyHorseIsActuallyAPony = retardedly good password (Long and makes no sense, so not in a dictionary, and you already remembered it for at least a few days just by reading it now)

Changing passwords often = bad (because you make short ones to remember them, and after a while you start writing them down)


It's a bit of a myth that writing down the password is automatically bad. Most people inherently understand controlling access to information that is written down on a sheet of paper. They can fold it over to keep it hidden from prying eyes, they can tuck it away in their wallet/purse, or keep it in a locked box/drawer.

What you have to do is train them to (a) not put it somewhere silly like under the keyboard or in an open desk drawer and (b) that they are legally responsible if bad things happen due to the password leaking.

all of my passwords are written in a tiny notebook with a lock on it, i keep the key around my enck adn the notebook in the bottom of my gun holster, so yeah, getting my passwords would require a fight.
Altair Raja
Brutor Tribe
Minmatar Republic
#51 - 2012-04-28 19:00:32 UTC
Well i rememebr when you could have anythign for a password as long is it was 5+ long...

for a good long while afer the password settings changed i kept my old simple one since even my ID is even diffrent from any other game i play.

also, non english passwords ftw! then no one can guess them, lol

AFK cloaking doesn't earn anything, so it needs a buff!

Ranger 1
Ranger Corp
Vae. Victis.
#52 - 2012-04-28 19:46:50 UTC
Security procedures for any online company is a serious issue, and responsibility.

Asking them to make their service less secure for your personal convenience is likely not going to happen.

Asking for a more convenient option that is as secure or even more so would be seriously considered.

Taking advice from people basing their information on hearsay, urban myth, or purely personal preference on security issues is generally a bad idea.

View the latest EVE Online developments and other game related news and gameplay by visiting Ranger 1 Presents: Virtual Realms.

Tau Cabalander
Retirement Retreat
Working Stiffs
#53 - 2012-04-28 21:23:37 UTC
Password Safe (Free & Open Source)
http://sourceforge.net/projects/passwordsafe/
leviticus ander
The Scope
Gallente Federation
#54 - 2012-04-28 21:26:57 UTC
Tau Cabalander wrote:
Password Safe (Free & Open Source)
http://sourceforge.net/projects/passwordsafe/

safer than that would be to just create an encrypted .txt file. since at least that way, you know that the program accessing it doesn't have any kind of access to the internet.
Mario MacGruber
State War Academy
Caldari State
#55 - 2012-04-28 21:47:29 UTC
CCP Sreegs wrote:
This will be reviewed when we institute the two factor option in the next couple of months.

Will there be 2 factor clients for Android, iPhone and Windows mobile similar to Battle.net and Google Authenticator?
CCP Sreegs
CCP Retirement Home
#56 - 2012-04-29 00:58:43 UTC
Mario MacGruber wrote:
CCP Sreegs wrote:
This will be reviewed when we institute the two factor option in the next couple of months.

Will there be 2 factor clients for Android, iPhone and Windows mobile similar to Battle.net and Google Authenticator?


There will be what is there when we can say it is :)

Internet Security Experts are the new Internet Lawyers. I'm not sure how I feel about that yet.

"Sreegs has juuust edged out Soundwave as my favourite dev." - Meita Way 2012

leviticus ander
The Scope
Gallente Federation
#57 - 2012-04-29 01:59:08 UTC
CCP Sreegs wrote:
Mario MacGruber wrote:
CCP Sreegs wrote:
This will be reviewed when we institute the two factor option in the next couple of months.

Will there be 2 factor clients for Android, iPhone and Windows mobile similar to Battle.net and Google Authenticator?


There will be what is there when we can say it is :)

Internet Security Experts are the new Internet Lawyers. I'm not sure how I feel about that yet.

it'll definitely be nice when you guys get that implemented.
and technically I am an internet security expert, I'm currently training for the CERT ethical hacker exam.
Scrapyard Bob
EVE University
Ivy League
#58 - 2012-04-29 21:55:35 UTC
leviticus ander wrote:

safer than that would be to just create an encrypted .txt file. since at least that way, you know that the program accessing it doesn't have any kind of access to the internet.


That's the method I use. Regular text files, where the contents are a GPG/PGP encrypted ASCII text block. One file per site or account.

The primary advantages:

- As long as I don't lose my GPG keys, I'm in pretty good shape.
- Since they are ASCII armored text blocks, they can be printed / faxed / emailed / OCR'd.
- Backups are dead simple (email a copy to yourself, stuff it in a version control system, etc).
- When I decrypt a particular file to get at a password, it only exposes a single account at a time.

The main downside:

- I'm relying on nobody ever stealing my GPG/PGP key and guessing my (lengthy) passphrase.

(But that's the same issue with letting Firefox remember your passwords, using a master passphrase. So it's a bit of a wash.)
leviticus ander
The Scope
Gallente Federation
#59 - 2012-04-29 23:40:31 UTC
Scrapyard Bob wrote:
leviticus ander wrote:

safer than that would be to just create an encrypted .txt file. since at least that way, you know that the program accessing it doesn't have any kind of access to the internet.


That's the method I use. Regular text files, where the contents are a GPG/PGP encrypted ASCII text block. One file per site or account.

The primary advantages:

- As long as I don't lose my GPG keys, I'm in pretty good shape.
- Since they are ASCII armored text blocks, they can be printed / faxed / emailed / OCR'd.
- Backups are dead simple (email a copy to yourself, stuff it in a version control system, etc).
- When I decrypt a particular file to get at a password, it only exposes a single account at a time.

The main downside:

- I'm relying on nobody ever stealing my GPG/PGP key and guessing my (lengthy) passphrase.

(But that's the same issue with letting Firefox remember your passwords, using a master passphrase. So it's a bit of a wash.)

or you could do what I'm doing, and write your own encryption/decryption software. if it's only you that's going to be using the files, it doesn't matter if you are using an industry standard encryption protocol or not.
Caha Evano
Victory of Samothrace
#60 - 2012-04-30 01:33:31 UTC  |  Edited by: Caha Evano
For anyone wanting to to make a strong password, I suggest you read through this password haystacks webpage. Additionally I suggest using a mnemonic, such as "My very educated mother just sewed us new pants." obviously Pluto is sad now. Either way, to use one in everyday life, just use what is in it or something you like. For example "Audrey Hepburn is the most elegant Woman I have ever seen." So this becomes, "AHitmeWIhes", as you can see the capital letters are in a logical manner to help remember where they are. Now you need numbers, well 4/5/1929 is her birthday. And so we will go with "529," the month and year she was born. Now we need two or three symbols, and these vary depending on the site/program, but EVE allows almost all of them or at least the least common ones, so little issue there. So let us choose our symbols, and they can be "$" "{" and "}". Let's take all them together, now.

AHitmeWIhes529${}

and this can become, Am{529}eWs$

But we are not done yet, so we don't want to come up with say fifty mnemonics, so we differentiate based on site. So how for EVE, well it can be Evil people who take my money, or "Ep".

Thus our final password can look something like this "Am{E529p}eWs$" so you now have a thirteen character password, with capital and lowercase letters, three numbers, and three symbols, that is the same for all your sites expect for two unique characters before and after "529."

Now saying this is as simple as, "Audery most {Evil 529 people } elegant Woman seen $"

If you use the above password for anything, um just wait a few years to do so.

I must admit I only read the first page about people complaining about the password requirements, and well, this address that.