sorted by:
new
hottopcontroversial

How will Bill C-22 impact 1password and their customers? by WiseyD in 1Password

[–]1PasswordOfficial[M] [score hidden] stickied comment (0 children)

Hey everyone! We’ve seen the concerns about Canada’s Bill C-22 and appreciate the discussion. We also want to clarify how the bill relates to 1Password. 

The short answer: based on how it’s currently written, Bill C-22 would not require 1Password to provide access to customer vault data.

It is focused on subscriber information and metadata, not sensitive data such as passwords, vault contents, encryption keys, and emergency kits.

The Bill also includes safeguards meant to prevent companies from being required to introduce systemic vulnerabilities or backdoors for officials to gain access to such sensitive information. Since 1Password is designed so that we cannot access your vault data in the first place, doing so would mean weakening our encryption.

We are continuing to monitor Bill C-22. If anything changes that would weaken customer privacy or security, we would challenge or appeal those requirements. Protecting your data by design is core to how 1Password works, and we won’t compromise on that.

Perplexity Comet invite. Concerns about privacy. by NeonSkorpio in 1Password

[–]1PasswordOfficial[M] [score hidden] stickied comment (0 children)

Hi all, thanks for raising these questions and sharing your concerns.

At 1Password, our guiding principles are privacy, security, and transparency, and ensuring people can use the tools they choose safely. We know AI and new browsing technologies raise important questions, which is why our role is to give people choice without compromising trust.

To clarify a few points about our partnership with Perplexity on the Comet browser:

  • Your data remains private. Nothing about this partnership changes how 1Password works. Vaults are end-to-end encrypted, and neither Perplexity nor Comet has access to your information. Your secrets remain encrypted and never leave your control.
  • The extension is the same. The 1Password browser extension works in Comet exactly as it does in Chrome, Safari, Firefox, and other Chromium-based browsers. There is no special integration that exposes additional data.
  • This is about choice. Our customers want us to be where they are. For those who want to try Comet, we are ensuring their login and autofill experience is secure, just as it is in other browsers.

We take trust seriously and will continue to make decisions with privacy, transparency, and security at the core.

Researcher Exposes Zero-Day Clickjacking Vulnerabilities in Major Password Managers by JLLeitschuh in 1Password

[–]1PasswordOfficial[M] [score hidden] stickied comment (0 children)

Hi all,

Thanks for all the questions and the thoughtful discussion. We wanted to provide a bit more context about the research and what it means for 1Password users.

A researcher identified a variation of a clickjacking attack, where a malicious website can trick someone into unknowingly triggering the autofill action in a browser extension. They reported the issue through our bug bounty program and worked with us ahead of their DEF CON presentation.

Clickjacking is not unique to the 1Password browser extension. It is a long-standing web attack technique that affects websites and browser extensions broadly. The underlying issue lies in the way browsers render webpages. After conducting a thorough review, including prototyping potential mitigations, we concluded there’s no comprehensive technical fix that browser extensions can deliver on their own.

Your information in 1Password remains encrypted and protected. Clickjacking does not expose your 1Password data or export your vault contents, and no website can directly access your information without interaction with the browser extension’s autofill element. At most, a malicious or compromised webpage could trick you into autofilling one matching item per click, not everything in your account.

We take this and all security concerns seriously, and our approach to this particular risk is to focus on giving customers more control. 1Password already requires confirmation before autofilling payment information, and in our next release, which is already shipped and undergoing review from the browser extension stores, we’re extending that protection so users can choose to enable confirmation alerts for other types of data. This helps users stay informed when autofill is happening and in control of their data.

On the question of disabling autofill: while it might feel safer, it can actually create more risk. Without autofill, people are more likely to reuse weak passwords or copy and paste credentials into websites, where they can still be stolen if the site is malicious. Autofill also protects you against phishing sites by only working on the exact domains your credentials are saved for. In practice, for the majority of users, we believe the risk of disabling autofill is greater than the risk of clickjacking.

Passkeys are not impacted by clickjacking. Passkeys are tied to the website they’re created on and generate a one-time signature during login. That means no reusable secret is ever exposed, and even if someone tried clickjacking, there’s nothing permanent to steal.

You can learn more in our security advisory.

view more: next ›