Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The login you use with lesspass doesn't need to match your actual login on a web site. In fact, nothing needs to match anything real. You could use any url or alias for the service you want to access ie "Google" and you can use your real login or any other text, it doesn't matter as far as you remember it (You could use 'me' for every site, I don't know why this field is required)


Okay, but now I have to remember 3x as many things as with a managed password manager. And how do I handle having multiple accounts on the same website?

"You can put whatever you want in field X" is not a solution to the problem IMO.


> how do I handle having multiple accounts on the same website?

You use the url of the site and your different logins to generate different passwords. What's so difficult about it.

Anyway, I don't think there is a problem at all.

Imagine this: I have 3 google accounts, which I use mainly for my gmail, another one for google play on my android and another one for my kids (google play, youtube). I could use the following setup: Gmail + me + masterpassword for the first one, Google Play + me + masterpassword for the second one, and Google Kids + kids + masterpassword. Another configuration could be: google + mail + pass, google + play + pass and google + kids + password. I actually would use my real login, since my accounts are already like this: username.mail@gmail.com, username.play@gmail.com, username.kids@gmail.com.

First there is nothing new to remember here, I already rememeber that I have 3 different accounts and what they are for. Second, it doesn't matter how many accounts you have on a site or how many sites you can access with the same account. You can use the url of a site and a different login for several accounts. You can use a description/purpose of your accounts and the same or different logins for several accounts on SSO services.

As I said, I don't see the problem.


> You use the url of the site and your different logins to generate different passwords. What's so difficult about it.

Your suggested solution of "not using your actual login" requires me to remember something that is not related to my login. This means that for multiple different accounts I need to remember twice as many things. Which makes it impractical (they can't be linked to my account or else my profiles will reveal the information).

> Imagine this: I have 3 google accounts, ...

I have ~8 different gmail accounts, all of which are used for emails. Yes, they're for different purposes but your scheme won't help differentiate them without also giving away my logins.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: