Avian00 Wrote:I'm a little confused about something. In your version 1.28 announcement, you say 2 things that trouble me:
2) "We now cover nearly 1500 TLDs properly, some TLDs like com.ru were missed before"
Avian00 Wrote:By quantifying your level of support with a finite number, and by announcing a for a particular site's compatibility, you seem to be indicating support for sites is being done a per-site basis. Why is this? Why is your software not simply taking the domain name from the URL and mapping that to Username and Password fields and automatically filling in the web form? In my brief experience with 1Password, the software simply runs in the background (with apparently no prior knowledge about any of the sites I visit), and the instant it detects that I've submitted username and password form data, it simply grabs them and stores them for later automatic filling. Does LastPass not operate on this same principle? If so, why the need to configure the software for compatibility on a per-site basis? This seems troublesome with potential a lot of overhead. What happens if a site re-arranges its forms at a later date? Would LastPass fall apart and not know what to do?
JoeSiegrist Wrote:One of the features that we wanted to do that no other password manager has done, is allow you the option of easily seeing passwords you created for other hosts in the same domain
JoeSiegrist Wrote:We have bent over backwards to make everything 'generally applicable'; we don't want to have a product that will break when the next generation comes around
Avian00 Wrote:Thanks for your quick and informative feedback. I have a couple follow-up questions, if you don't mind:JoeSiegrist Wrote:One of the features that we wanted to do that no other password manager has done, is allow you the option of easily seeing passwords you created for other hosts in the same domain
That sounds interesting. What about TLD's that have multiple hosts/subdomains but share the same account information? A prime example is google.com which shares the same credentials across all of its services (like mail.google.com, calendar.google.com, reader.google.com,etc...). Can LastPass use this principle in revers? Perhaps with a *.google.com wildcard so I don't end up with 10 LastPass entries for my unified Google credentials?
Avian00 Wrote:I have another question slightly related to this point. Will LastPass more 'generally applicable' in the sense that it goes beyond simply managing web-site logins? I'm also interested in something that could hold information like bank accounts and PINs and other various bits of important data I must remember but must remain secure. Obviously I could currently use LastPass for this task, but only in a way which seems counter to its intended use, since it is a URL-centric system.
JoeSiegrist Wrote:Yes this is exactly what it's for; '.com' is a TLD, so XX.com and YYY.XX.com are shown together to try to share accounts if the login and password are the same.... We hate having 50 accounts with different saved passwords for each, we thought 1 was more appropriate (and more likely to be managed).
JoeSiegrist Wrote:Yes, that's definitely where we're headed, and I'd add to it that you'll see windows applications passwords stored as well.
Users browsing this forum: No registered users and 14 guests