Event JSON
{
"id": "96e90c42a4aca5281b307e4da76d43fc0811670ba979a159525fbb66c3069896",
"pubkey": "6f2307904a92e77162cd675737a5ad7faeb23a643875f776058e6c0f88d321ba",
"created_at": 1704206900,
"kind": 1,
"tags": [
[
"p",
"749d2a0ca4592e847a6ed93d459cc3b86eed60f6016a9e31e06c91a43d23e252",
"wss://relay.mostr.pub"
],
[
"p",
"de7aa63b1c7e809f66a67bdcd2bd4c952a09cd52ee01ed7db358d09bad97f840",
"wss://relay.mostr.pub"
],
[
"t",
"protonpass"
],
[
"t",
"protonmail"
],
[
"t",
"protondrive"
],
[
"t",
"protoncalendar"
],
[
"t",
"proton"
],
[
"t",
"passwordmanager"
],
[
"t",
"2fa"
],
[
"t",
"bitwarde"
],
[
"t",
"security"
],
[
"t",
"privacy"
],
[
"proxy",
"https://techhub.social/users/Stark9837/statuses/111686903405399394",
"activitypub"
]
],
"content": "nostr:npub1wjwj5r9ytyhgg7nwmy75t8xrhphw6c8kq94fuv0qdjg6g0fruffq02ue5t are there any plans to change the fact that #ProtonPass uses the same password as our #ProtonMail, #ProtonDrive and #ProtonCalendar? It just seems like a design flaw and security concern?\n\nFor example, I can't use ProtonPass to store a randomly generated password for my email, as it uses my #Proton account. Also, assuming I now use a password for my ProtonMail, if the password becomes comprised in whatever way, my password manager is also compromised. \n\nThis effect is cascaded by the fact that ProtonPass can be used as a #passwordmanager and #2FA, so I can't use it for my 2FA for my email. \n\nThis is probably one of my few reasons to not switch from #Bitwarde.\n\n#Security #Privacy",
"sig": "81bb790320af9c1d10b1b82ab45e69082ad79932e376cb7f470d7d227e98294c5497013add730eadbcd769480d136f7fe97f4b93a6d50eb6d815d1ffb50d2531"
}