To those of you that say its the worst idea to write the 24 word seed in gmail... i would agree with this because someone could hack your account. However, if you use say lastpass or keepass and then put the seed in either program, isn't that pretty safe? Thus the hacker would not only need to know your gmail address, they need your gmail password. Then they would need your password to either your lastpass or keepass. So wouldn't that be pretty safe? Or that could still be hacked?
If you are putting the seed into a password manager (which itself is as secured as the passwordmanager (encryption implementation, ..) is), why are you then storing something in your email?
Is your idea to store the encrypted file in your email account?
Or are you talking about storing your gmail password in a password manager and then store the seed (encrypted/unencrypted ?) in your gmail account?
As i have already mentioned..
email is broken!Any (unencrypted) email you send, can be read by anyone who cares to read your emails. I hope you know this.
So, no. An attacker would not need your gmail password to 'receive' your mails. He simply just 'copies them on the way to the mail server'.
Note that it is not that trivial as i have described. But for an attacker with medium knowledge this is pretty easy to accomplish.
For more information about how broken email is:
https://en.wikipedia.org/wiki/Email#Privacy_concerns
Because they would have to go through 2 layers of security right?
No, only passwordmanager encryption.
Since an attacker (who does target you) can read/intercept all of your (unencrypted) emails.
Also isn't it true if someone logs into your gmail account from another location, gmail would block them if they don't recognize the ip address or country etc?
An attacker could use a proxy, faking an IP address near from your location.
This is a security measurement which can easily be bypassed.
So wouldn't that be another hurdle for that hacker?
No.
And even if they get through that, how could they hack the password for lastpass or keepass then? Are there cases of this?
Because i have heard of cases where someone types their seed and emails it to their gmail account like in plain letters... that is bad since its not even encrypted. But with lastpass or keepass, isn't that pretty safe then?
Well, as long as there is no vulnerability found (e.g. mistake in the implementation in the password manager) it is safe to store your seed inside kepass.
But keep in mind that an attacker might have your encrypted file once you attach it to an email.
So he has quite some time (assuming you don't change your seed frequently) to bruteforce all easy passwords.
And once a vulnerability might be found, your seed can definetely get compromised.
Overall, it is 'pretty safe' to store your encrypted seed in your email account regarding the possibility of someone cracking the encryption.
But note that there are way more secured storage possibilities than an email account.
Additionally you don't have any control over 1) who gets access to your encrypted file and 2) how long your file will stay there.
One morning the email service provider might have a failure with their servers, resulting in a loss of data.. or whatever..
I would not suggest to use email as a storage for ANY confidential information.