News for hackers. Stuff that matters.
Re:LastPass: design flaw in communication to privileged comp... by saurik on Wednesday July 27, 2016 @09:31PM (#12177776)
I thought the point of a password manager is to allow you to have separate passwords for numerous services which are protected by centralizing those passwords somewhere (preferably somewhere you control, such as your own phone) and protecting the result with one password. Your model of them seems to involve them replacing a password locally, which I don't think anyone would recommend.
Re:LastPass: design flaw in communication to privileged comp... by EGreg on Wednesday July 27, 2016 @11:04PM (#12178083)
I would say password reuse can be pretty good! Simply have your own rule such as "letters 2 and 5 of the domain name" and combine those with your reusable password.

In fact, I'd go further and say that you can do this with your login name. So for example:

[email protected] for eBaY

This also helps mitigate those attacks where the attacker actually contacts support and socially engineers them into giving all your info and even stealing your account:

https://medium.com/@espringe/amazon-s-customer-service-backd...

If you are hosting with AWS you should really consider doing that http://www.techinsider.io/hacker-social-engineer-2016-2

Re:LastPass: design flaw in communication to privileged comp... by AdmiralAsshat on Thursday July 28, 2016 @10:11AM (#12180277)
This assumes that your password is never leaked, changed, or reset. What happens if Ebay's password database were exfiltrated? You now have the following problems:

1) If your password is cracked, a hacker seeing it might deduce your algorithm and then deduce that your Amazon password would be 'myemail+mo', etc. Now your scheme is out the window.

2) Even assuming your password is salted and hashed securely such that it can't be decrypted, Ebay would probably reset it as a precaution. So now you've got to change this password. Maybe you decide to do the 3rd and 5th letters of the domain name instead. So now your scheme is 2nd-and-5th for all but Ebay, and you've got to remember that the Ebay one is unique. For now. As more leaks or resets occur down the line, however, you'll have more exceptions, to the point that you'll be forced to maintain a list of what KIND of passwords each site uses. In which case, why not just use a password manager?

Re:LastPass: design flaw in communication to privileged comp... by tonmoy on Wednesday July 27, 2016 @11:39PM (#12178185)
This "clever" security measure would be annihilated in case of a well planned attack targeted against a single individual.
Re:LastPass: design flaw in communication to privileged comp... by nitrogen on Thursday July 28, 2016 @12:33AM (#12178326)
I imagine password cracking apps are also smart enough to try letters from the site domain combined with other known base passwords (dictionary words, common substrings from other password leaks, etc.).
Re:LastPass: design flaw in communication to privileged comp... by EGreg on Wednesday July 27, 2016 @11:47PM (#12178202)
Do you realize that your AWS account can be compromised without something like this?
Re:LastPass: design flaw in communication to privileged comp... by justinludwig on Thursday July 28, 2016 @12:50AM (#12178374)
Using different usernames/emails for different services is not a bad idea (particularly as a defense against untargeted attacks). But using a simple algorithm for generating passwords (ie pretty much any algorithm a human can remember) is playing with fire -- if an attacker can recover your generated passwords from just a few different services (via lucky crack from a db dump, or some site stored or transmitted or logged it in plaintext, or you were phished, or you created an account to try out someone's random mvp on a slapdash server that was already pwnd, etc), a human attacker will be able to figure out your username/password for all of your services. (And if we're not there already, it won't be too long before automated password crackers can do the same.)

Plus, from a practical standpoint, what do you do when a site forces you to change your password because they fear their password db has been compromised (or has asinine rules about your password being too long, or make you rotate your password every 90 days, or they change their domain name 5 times in 3 years)?

Re:LastPass: design flaw in communication to privileged comp... by CamperBob2 on Thursday July 28, 2016 @03:31AM (#12178869)
99.999% of users will never experience a "well-planned targeted attack." Making us jump through the same security hoops that can protect high-value targets is annoying.
Re:LastPass: design flaw in communication to privileged comp... by tonmoy on Thursday July 28, 2016 @12:10PM (#12181120)
Anyone could become a target anytime. An attacker would just have to attack one person at a time.