←back to thread

184 points Bogdanp | 1 comments | | HN request time: 0.207s | source
Show context
bmandale ◴[] No.45105669[source]
> An attempt by an open source password manager to provide export of private keys was ruled insecure and should not be supported.

The name of the issue reveals the actual problem: "should never be exported in clear text". If the export was encrypted with a passphrase in a standard format, then there would be no issue. It's specifically doing it in plain text that causes consternation. Of course, in practice it doesn't make much of a difference when users are incapable of choosing secure passwords, let alone passphrases. But requiring exports to be encrypted is the least one can do to maintain a degree of security while still allowing exports.

> For many years already, people lose access to their Google account every day and can never regain it. Google is well known for terminating accounts without stating any reasons. With that comes the loss of access to your data. In this case, you also lose your credentials for third-party websites.

In practice this is frequently already true. Many sites require an email to sign up. Whenever you attempt to log in on a new device, they require you to type in a code sent to your email. Without access to your email, you cannot sign in.

replies(3): >>45105880 #>>45106093 #>>45117111 #
1. NoGravitas ◴[] No.45117111[source]
The spec participant here is also saying that encrypting your export file is a "temporary minimum". Personally, I think that requiring a passphrase for some standard symmetric encryption on the export is fine. Plenty of free and privacy-preserving apps I use (Signal, Aegis) do this. The real issue is that there is no guarantee over the medium term that even this will continue to be allowed.