1Password: Difference between revisions
m http to https with AutoWikiBrowser, replaced: http: → https: |
m This edit adds issues related to 1Password's licencing controversy |
||
| Line 38: | Line 38: | ||
1Password, which uses an Okta instance, published a blog post disclosing an internal investigation of the breach.<ref>{{Cite web |last=Canahuati |first=Pedro |date=2023-10-23 |title=Okta Support System incident and 1Password |url=https://blog.1password.com/okta-incident/ |url-status=live |archive-url=https://web.archive.org/web/20250905070945/https://blog.1password.com/okta-incident/ |archive-date=2025-09-05 |access-date=2025-09-05 |work=1Password Blog}}</ref> According to their disclosure, the attackers' actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported that no user data was exfiltrated or decrypted.<ref>{{Cite web |date=2023-10-27 |title=Security incident report |url=https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-url=https://web.archive.org/web/20250920201057if_/https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-date=2025-09-20 |access-date=2026-01-23 |website=1Password Blog}}</ref> | 1Password, which uses an Okta instance, published a blog post disclosing an internal investigation of the breach.<ref>{{Cite web |last=Canahuati |first=Pedro |date=2023-10-23 |title=Okta Support System incident and 1Password |url=https://blog.1password.com/okta-incident/ |url-status=live |archive-url=https://web.archive.org/web/20250905070945/https://blog.1password.com/okta-incident/ |archive-date=2025-09-05 |access-date=2025-09-05 |work=1Password Blog}}</ref> According to their disclosure, the attackers' actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported that no user data was exfiltrated or decrypted.<ref>{{Cite web |date=2023-10-27 |title=Security incident report |url=https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-url=https://web.archive.org/web/20250920201057if_/https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-date=2025-09-20 |access-date=2026-01-23 |website=1Password Blog}}</ref> | ||
===1Password License Controversy=== | |||
1Password’s so-called “lifetime license” (i.e., standalone license) was a perpetual license for a specific major version, not unlimited future upgrades: 1Password 7 for Windows launched with standalone licensing on May 29, 2018<ref>{{Cite web |title=1Password for Windows Release Notes |url=https://app-updates.agilebits.com/product_history/OPW6 |url-status=live |access-date=2026-04-30 |website=1Password}}</ref>, however, after the release of 1Password 8, previous licenses would not be offered and previous versions would no longer be supported <ref>{{Cite web |title=Upgrading to version 8 from 7 |url=https://www.1password.community/discussions/1password/upgrading-to-version-8-from-7/159414 |url-status=live |access-date=2026-04-30 |website=1Password Community}}</ref>, making 1Password effectively membership-only and pushing users toward a 1Password account. While existing 1Password 7 licenses did not expire, their end-of-life meant that users would likely bump on vulnerabilities (see comment by 1P_SimonH<ref>{{Cite web |title=Upgrading to version 8 from 7 |url=https://www.1password.community/discussions/1password/upgrading-to-version-8-from-7/159414 |url-status=live |access-date=2026-04-30 |website=1Password Community}}</ref>). | |||
==See also== | ==See also== | ||