LastPass

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

LastPass
250px
Developer(s) LastPass
Initial release August 22, 2008 (2008-08-22)
Stable release Chrome
4.1.4 (April 1, 2016; 8 years ago (2016-04-01))

Firefox
4.1.5 (March 16, 2016; 8 years ago (2016-03-16))

Safari
4.1.4 (April 1, 2016; 8 years ago (2016-04-01))

Internet Explorer
4.1.2/3 (March 8, 2016; 8 years ago (2016-03-08))[1]

Opera
4.1.2 (March 8, 2016; 8 years ago (2016-03-08))[2]

Maxthon
3.3.0 (March 24, 2016; 8 years ago (2016-03-24))[3]

Mac App
3.14 (March 30, 2016; 8 years ago (2016-03-30))[4]
Operating system Cross-platform
Available in Multilingual
Type Password manager
License Proprietary software
Website lastpass.com

LastPass is a freemium password management service which stores encrypted passwords in the cloud.[5] LastPass is standard with a web interface but also includes plugins and apps for many modern web browsers and includes support for bookmarklets.[5][6][7]

Overview

Passwords in LastPass are protected by a master password, encrypted locally, and synchronized to any other browser. LastPass has a form filler that automates password entering and form filling. It also supports password generation, site sharing and site logging.[8]

On December 2, 2010, it was announced that LastPass acquired the bookmark synchronizer Xmarks.[9] LastPass password management technology was integrated into the "Identity and Privacy" feature of Internet security company Webroot’s newest security suite. Full terms of the licensing deal were not disclosed.[10] Although it is closed source, Sameer Kochhar (one of the developers of LastPass), has argued that, theoretically, the integrity of the software could be verified without making it open source, and mentioned that the developers may be open to the future possibility of making the user interface of LastPass open source.[11]

On October 9, 2015, LastPass was acquired by LogMeIn, Inc. for $125 million; the company will be combined under the LastPass brand with a similar product, Meldium, which was also acquired by LogMeIn.[12] The acquisition was met with quite some criticism from users related to having had a bad experience with LogMeIn in the past.[13]

On February 3, 2016, LastPass unveiled a new logo. The previous logo, which prominently featured an asterisk, was the subject of an unanticipated trademark lawsuit filed in early 2015 by E-Trade, whose logo also features an asterisk.[14][15][16]

On March 16, 2016, LastPass released LastPass Authenticator, a free two-factor authentication app.[17]

Features

  • One master password
  • Cross-browser synchronization
  • Secure password generation
  • Password encryption
  • Form filling
  • Importing and exporting passwords
  • Portable access (using PortableApps.com browsers)
  • Multifactor authentication
  • Password-Fingerprint verification (using local certificates or YubiKey)
  • Cross-platform availability (mobile versions available for premium accounts)
  • Mobile access available[18]
  • Free and premium credit monitoring (USA only)[19]

Reception

In March 2009, PC Magazine awarded LastPass their "Editors' Choice" for password management.[20] LastPass has a rating of 4 out of 5 stars at the Firefox Add-ons web site with over 900 reviews,[21] and it has been featured on Download Squad,[22] Lifehacker,[23] and MakeUseOf.[24]

In July 2010, LastPass's security model was extensively covered and approved of by Steve Gibson in his Security Now podcast episode 256.[25] He also revisited the subject and how it relates to the NSA in Security Now podcast episode 421.[26]

Security issues

XSS vulnerability

In February 2011, a cross-site scripting (XSS) security hole was discovered, reported by security researcher Mike Cardwell, and closed within hours.[27] There was disagreement over severity. Cardwell stated that people should be "very concerned." The company reported that a log search showed no evidence of exploitation (other than by Cardwell). However, in addition to closing the hole, LastPass took additional steps to improve security, including implementing HTTP Strict Transport Security (HSTS), as Cardwell had suggested, implementing X-Frame-Options, and a Content Security Policy-like system in order to provide defense in depth.[27][28]

2011 security breach

On Tuesday, May 3, 2011, LastPass discovered an anomaly in their incoming network traffic, and then another, similar anomaly in their outgoing traffic.[29] Administrators found none of the hallmarks of a classic security breach (for example, database logs showed no evidence of a non-administrator user being elevated to administrator privileges), but neither could they determine the root cause of the anomalies. Furthermore, given the size of the anomalies, it is theoretically possible that data such as email addresses, the server salt, and the salted password hashes were copied from the LastPass database. To address the situation, LastPass decommissioned the "breached" servers so they could be rebuilt, and on May 4, 2011, they requested all users to change their master password. However, the resulting user traffic overwhelmed the login servers and, temporarily, administrators were asking users to refrain from changing their passwords until further notice, having judged that the possibility of the passwords themselves being compromised was trivially small. LastPass also stated that while there was no direct evidence any customer information was directly compromised, they preferred to err on the side of caution.[30] There have been no verified reports of customer data loss or password leaks since these precautions were taken. In comment 6, Joe Siegrist committed to a third-party audit, saying one "is certainly prudent". However, no audit results have been published to date.

2015 security breach

On Monday, June 15, 2015, LastPass posted a blog post indicating that the LastPass team discovered and blocked suspicious activity on their network on the previous Friday.[31] Their investigation revealed that LastPass account email addresses, password reminders, server per user salts, and authentication hashes were compromised. LastPass encrypted user vault data were not taken in this incident. The blogpost was quoted as saying, "We are confident that our encryption measures are sufficient to protect the vast majority of users. LastPass strengthens the authentication hash with a random salt and 100,000 rounds of server-side PBKDF2-SHA256, in addition to the rounds performed client-side. This additional strengthening makes it difficult to attack the stolen hashes with any significant speed."[32]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. https://addons.opera.com/en/extensions/details/lastpass/
  3. http://extension.maxthon.com/detail/index.php?view_id=1721
  4. https://itunes.apple.com/us/app/lastpass-password-manager/id926036361?mt=12
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Automation, partnerships drive Webroot revamp cnet.com 2010-07-26.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. https://forums.lastpass.com/viewtopic.php?f=6&t=131235
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. LastPass mobile
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 LastPass Vulnerability Exposes Account Details (Archived by WebCite®)
  28. Cross Site Scripting vulnerability reported, fixed (Archived by WebCite®)
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. LastPass Security Notification(Archive)
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.

External links