MEW-01-005 Web - Remove all HTTP links (#978)

* Replace custom linter rule with no-http-string rule. Fix exceptions.

* Replaced all http links in translations with https links.
This commit is contained in:
William O'Beirne 2018-02-01 17:51:15 -05:00 committed by Daniel Ternyak
parent e34137270e
commit ecccdcfc33
36 changed files with 163 additions and 328 deletions

View File

@ -170,7 +170,7 @@ export default class CustomNodeModal extends React.PureComponent<Props, State> {
{this.renderInput(
{
name: 'url',
placeholder: 'http://127.0.0.1/'
placeholder: 'https://127.0.0.1/'
},
invalids
)}

View File

@ -193,7 +193,9 @@ const EXP: NetworkConfig = {
unit: 'EXP',
chainId: 2,
color: '#673ab7',
// tslint:disable:no-http-string - Unavailable behind HTTPS right now
blockExplorer: makeExplorer('http://www.gander.tech'),
// tslint:enable:no-http-string
tokens: require('./tokens/exp.json'),
contracts: require('./contracts/exp.json'),
dPathFormats: {

View File

@ -75,7 +75,7 @@ const generalInfoNodes: InfoNode[] = [
<li key="ensMore-2">
<NewTabLink
content="ENS: Read the Docs"
href="http://docs.ens.domains/en/latest/userguide.html#registering-a-name-with-the-auction-registrar"
href="https://docs.ens.domains/en/latest/userguide.html#registering-a-name-with-the-auction-registrar"
/>
</li>,
<li key="ensMore-3">

View File

@ -9,7 +9,7 @@ import translate from 'translations';
const ENSDocsLink = () => (
<NewTabLink
href="http://ens.readthedocs.io/en/latest/introduction.html"
href="https://ens.readthedocs.io/en/latest/introduction.html"
content="Ethereum Name Service"
/>
);

View File

@ -20,7 +20,7 @@ const BROWSERS = [
},
{
name: 'Opera',
href: 'http://www.opera.com/',
href: 'https://www.opera.com/',
icon: operaIcon
}
];

View File

@ -52,7 +52,7 @@
Chrome
</span>
</a>
<a class="BadBrowser-content-browsers-browser opera" href="http://www.opera.com/" rel="noopener noreferrer" target="_blank">
<a class="BadBrowser-content-browsers-browser opera" href="https://www.opera.com/" rel="noopener noreferrer" target="_blank">
<span class="BadBrowser-content-browsers-browser-name">
Opera
</span>
@ -97,4 +97,4 @@
</script>
</body>
</html>
</html>

View File

@ -263,7 +263,7 @@
"MSG_info3": "Include a specific reason for the message so it cannot be reused for a different purpose. ",
"VIEWWALLET_ShowPrivKey": "(show)",
"VIEWWALLET_HidePrivKey": "(hide)",
"VIEWWALLET_Subtitle": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. Vous devrez le faire pour [importer votre compte dans Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si vous voulez consulter votre solde, nous recommandons d'utiliser un explorateur de blockchain comme [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. Vous devrez le faire pour [importer votre compte dans Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si vous voulez consulter votre solde, nous recommandons d'utiliser un explorateur de blockchain comme [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. ",
"VIEWWALLET_SuccessMsg": "Succès ! Voici les détails de votre portefeuille. ",
"MNEM_1": "Sélectionnez l'adresse avec laquelle vous désirez interagir. ",
@ -522,7 +522,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": " This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -536,12 +536,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -651,3 +651,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -230,7 +230,7 @@
"MYWAL_Content_1": "Achtung! Du bist gerade dabei dein Wallet zu löschen ",
"MYWAL_Content_2": "Stelle sicher, dass du **die private Key/JSON Datei und das Passwort** deines Wallets gespeichert hast, bevor du es löschst. ",
"MYWAL_Content_3": "Wenn du dieses Wallet in Zukunft mit MyEtherWallet CX verwenden willst, musst du es mittels der privaten Key/JSON Datei und deinem Passwort manuell wieder hinzufügen. ",
"VIEWWALLET_Subtitle": "Dies erlaubt dir den Download verschiedener Versionen deines privaten Schlüssel sowie das erneute Drucken deines Papier-Wallets. Es wird empfohlen, dies zu tun um [Deinen Account in Geth/Mist zu importieren.](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Zum Überprüfen deines Kontostands empfehlen wir, einen Blockchain Explorer wie [etherscan.io](http://etherscan.io/) zu verwenden. ",
"VIEWWALLET_Subtitle": "Dies erlaubt dir den Download verschiedener Versionen deines privaten Schlüssel sowie das erneute Drucken deines Papier-Wallets. Es wird empfohlen, dies zu tun um [Deinen Account in Geth/Mist zu importieren.](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Zum Überprüfen deines Kontostands empfehlen wir, einen Blockchain Explorer wie [etherscan.io](https://etherscan.io/) zu verwenden. ",
"VIEWWALLET_Subtitle_Short": "Dies erlaubt dir den Download verschiedener Versionen deines privaten Schlüssel sowie das erneute Drucken deines Papier-Wallets. ",
"VIEWWALLET_SuccessMsg": "Erfolgreich! Hier sind die Daten deines Wallets. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -227,7 +227,7 @@
"MYWAL_Content_1": "Προσοχή! Πρόκειται να αφαιρέσετε το πορτοφόλι σας. ",
"MYWAL_Content_2": "Σιγουρευτείτε ότι έχετε **αποθηκεύσει το αρχείο keystore/JSON και το συνθηματικό** του πορτοφολιού αυτού πριν το αφαιρέσετε. ",
"MYWAL_Content_3": "Αν θέλετε να χρησιμοποιήσετε το πορτοφόλι αυτό με το MyEtherWalletCX στο μέλλον, θα χρειαστεί να το ξαναπροσθέσετε χειροκίνητα χρησιμοποιώντας το ιδιωτικό κλειδί/JSON και το συνθηματικό. ",
"VIEWWALLET_Subtitle": "Αυτό σας επιτρέπει να κατεβάσετε διαφορετικές εκδοχές των ιδιωτικών κλειδιών σας και να επανεκτυπώσετε το χάρτινο πορτοφόλι σας. Ίσως επιθυμείτε να το κάνετε προκειμένου να [εισαγάγετε το λογαριασμό σας στο Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Αν επιθυμείτε να ελέγξετε το υπόλοιπό σας, συνιστούμε να χρησιμοποιήσετε ένα εργαλείο εξερεύνησης blockchain όπως το [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Αυτό σας επιτρέπει να κατεβάσετε διαφορετικές εκδοχές των ιδιωτικών κλειδιών σας και να επανεκτυπώσετε το χάρτινο πορτοφόλι σας. Ίσως επιθυμείτε να το κάνετε προκειμένου να [εισαγάγετε το λογαριασμό σας στο Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Αν επιθυμείτε να ελέγξετε το υπόλοιπό σας, συνιστούμε να χρησιμοποιήσετε ένα εργαλείο εξερεύνησης blockchain όπως το [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Αυτό σας επιτρέπει να κατεβάσετε διαφορετικές εκδοχές των ιδιωτικών κλειδιών σας και να επανεκτυπώσετε το χάρτινο πορτοφόλι σας. ",
"VIEWWALLET_SuccessMsg": "Επιτυχία! Εδώ είναι οι πληροφορίες για το πορτοφόλι σας. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Γιατί δεν έχει εμφανιστεί ο λογαριασμός που μόλις δημιούργησα στον εξερευνητή blockchain; (δηλαδή: etherchain, etherscan) ",
"HELP_15_Desc_1": "Ένας λογαριασμός εμφανίζεται σε έναν εξερευνητή blockchain μόνο όταν ο λογαριασμός έχει δραστηριότητα&mdash;για παράδειγμα, αφού μεταφέρετε κάποιο ποσό Αιθέρα σε αυτόν. ",
"HELP_16_Title": "16) Πώς ελέγχω το υπόλοιπο του λογαριασμού μου; ",
"HELP_16_Desc_1": "Μπορείτε να χρησιμοποιήσετε έναν εξερευνητή blockchain όπως το [etherscan.io](http://etherscan.io/). Επικολλήστε τη διεύθυνσή σας στη γραμμή αναζήτησης και θα ανασύρει τη διεύθυνση και το ιστορικό συναλλαγών σας. Για παράδειγμα, δείτε πώς φαίνεται ο [λογαριασμός μας για δωρέες](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) στο etherscan.io ",
"HELP_16_Desc_1": "Μπορείτε να χρησιμοποιήσετε έναν εξερευνητή blockchain όπως το [etherscan.io](https://etherscan.io/). Επικολλήστε τη διεύθυνσή σας στη γραμμή αναζήτησης και θα ανασύρει τη διεύθυνση και το ιστορικό συναλλαγών σας. Για παράδειγμα, δείτε πώς φαίνεται ο [λογαριασμός μας για δωρέες](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) στο etherscan.io ",
"HELP_17_Title": "17) Γιατί δεν εμφανίζεται το υπόλοιπό μου όταν ξεκλειδώνω το πορτοφόλι μου; ",
"HELP_17_Desc_1": "Αυτό πιθανότατα οφείλεται στο γεγονός ότι βρίσκεστε πίσω από κάποιο τείχος προστασίας. Το API που χρησιμοποιούμε για να πάρουμε το υπόλοιπο και να μετατρέψουμε το εν λόγω υπόλοιπο συχνά εμποδίζεται από τείχη προστασίας για διάφορους λόγους. Θα εξακολουθείτε να είστε σε θέση να αποστείλετε συναλλαγές, απλά πρέπει να χρησιμοποιήσετε μια διαφορετική μέθοδο για να δείτε το εν λόγω υπόλοιπο, όπως το etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -284,7 +284,7 @@
"MSG_info1": "Include the current date so the signature cannot be reused on a different date. ",
"MSG_info2": "Include your nickname and where you use the nickname so someone else cannot use it. ",
"MSG_info3": "Include a specific reason for the message so it cannot be reused for a different purpose. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -525,7 +525,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": " This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -539,12 +539,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -654,3 +654,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -230,7 +230,7 @@
"MYWAL_Content_1": "¡Atención! Estás a punto de eliminar tu cartera ",
"MYWAL_Content_2": "Asegúrate de haber **guardado tu clave privada y/o archivo almacén de clave y la contraseña** antes de eliminarlo. ",
"MYWAL_Content_3": "Si en el futuro quieres utilizar esta cartera con MyEtherWallet CX, tendrás que volver a añadirla manualmente utilizando Clave Privada/JSON y contraseña. ",
"VIEWWALLET_Subtitle": "Esto te permite descargar múltiples versiones de claves privadas e imprimir de nuevo tu cartera en papel. Puede que te interese hacer esto para [importar tu cuenta en Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si quieres comprobar tu saldo, recomendamos utilizar un explorador de blockchain como [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Esto te permite descargar múltiples versiones de claves privadas e imprimir de nuevo tu cartera en papel. Puede que te interese hacer esto para [importar tu cuenta en Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si quieres comprobar tu saldo, recomendamos utilizar un explorador de blockchain como [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Esto te permite descargar múltiples versiones de claves privadas e imprimir de nuevo tu cartera en papel. ",
"VIEWWALLET_SuccessMsg": "¡Enhorabuena! Estos son los detalles de tu cartera. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your account and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your account and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Seguridad - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "¿Dónde está guardando mi información esta extensión? ",
"HELP_SecCX_Desc_2": "La información que guardas en esta extensión de Chrome se guarda por medio de [chrome.storage](http://chrome.storage/). - este es el mismo lugar en el que se guardan tus contraseñas cuando guardas tus contraseñas en Chrome. ",
"HELP_SecCX_Desc_2": "La información que guardas en esta extensión de Chrome se guarda por medio de [chrome.storage](https://chrome.storage/). - este es el mismo lugar en el que se guardan tus contraseñas cuando guardas tus contraseñas en Chrome. ",
"HELP_SecCX_Desc_3": "¿Qué información se guarda? ",
"HELP_SecCX_Desc_4": "La dirección, alias y clave privada se guardan en chrome.storage. La clave privada se cifra utilizando la contraseña que introdujiste al añadir la cartra. El alias y la dirección de la cartera no están cifrados. ",
"HELP_SecCX_Desc_5": "¿Por qué no se cifran el alias y la dirección de la cartera? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -231,7 +231,7 @@
"MYWAL_Content_1": "Varoitus! Olet poistamassa lompakkoasi. ",
"MYWAL_Content_2": "Varmista että olet **tallentanut tähän lompakkoon liittyvät yksityisen salausavaimesi/JSON tiedostosi ja salasanasi** ennen kuin poistat sen. ",
"MYWAL_Content_3": "Jos tahdot käyttää tätä lompakkoa MyEtherWallet CX:si kanssa tulevaisuudessa, sinun täytyy manuaalisesti uudelleen-lisätä se käyttäen yksityistä salausavaintasi/JSONia ja salasanaa. ",
"VIEWWALLET_Subtitle": "Tämä antaa sinun ladata eri versiota yksityisistä salausavaimistasi ja uudelleen-tulostaa paperi lompakkosi. Saatat tahtoa tehdä tämän [tuodaksesi sinun tilisi Gethiin/Mistiin](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jos haluat tarkistaa saldosi, me suosittelemme käyttämään blockchain exploreria kuten [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Tämä antaa sinun ladata eri versiota yksityisistä salausavaimistasi ja uudelleen-tulostaa paperi lompakkosi. Saatat tahtoa tehdä tämän [tuodaksesi sinun tilisi Gethiin/Mistiin](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jos haluat tarkistaa saldosi, me suosittelemme käyttämään blockchain exploreria kuten [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Tämä antaa sinun ladata eri versiota yksityisistä salausavaimistasi ja uudelleen-tulostaa paperi lompakkosi. ",
"VIEWWALLET_SuccessMsg": "Onnistui! Tässä ovat lompakkosi yksityiskohdat. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -234,7 +234,7 @@
"MYWAL_Content_1": "Attention ! Vous êtes sur le point de supprimer votre portefeuille ",
"MYWAL_Content_2": "Assurez-vous d'avoir bien **sauvegardé la clé privée/ fichier JSON et le mot de passe** associé à ce portefeuille avant de le supprimer. ",
"MYWAL_Content_3": "Si vous voulez utiliser ce portefeuille avec MyEtherWallet CX à l'avenir, vous devrez le rajouter manuellement en utilisant la clé privée/fichier JSON et le mot de passe. ",
"VIEWWALLET_Subtitle": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. Vous devrez le faire pour [importer votre compte dans Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si vous voulez consulter votre solde, nous recommandons d'utiliser un explorateur de blockchain comme [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. Vous devrez le faire pour [importer votre compte dans Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Si vous voulez consulter votre solde, nous recommandons d'utiliser un explorateur de blockchain comme [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Ceci vous permet de télécharger plusieurs versions des clefs privées et de ré-imprimer votre portefeuille papier. ",
"VIEWWALLET_SuccessMsg": "Succès ! Voici les détails de votre portefeuille. ",
"VIEWWALLET_ShowPrivKey": "(montrer)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Pourquoi le compte que je viens de créer n'apparaît-il pas dans l'explorateur de blockchain ? (i.e. : etherchain, etherscan) ",
"HELP_15_Desc_1": "Les comptes n'apparaissent dans un explorateur de blockchain qu'après une activité y ait eu lieu comme, par exemple, quand on y a transféré de l'Ether. ",
"HELP_16_Title": "16) Comment puis-je vérifier le solde de mon compte ? ",
"HELP_16_Desc_1": "Vous pouvez utiliser un explorateur de blockchain comme [etherscan.io](http://etherscan.io/). Collez votre adresse dans la barre de recherche et cela récupérera votre solde et l'historique de vos transactions. Par exemple, voici ce que montre notre [compte de donations](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) sur etherscan.io ",
"HELP_16_Desc_1": "Vous pouvez utiliser un explorateur de blockchain comme [etherscan.io](https://etherscan.io/). Collez votre adresse dans la barre de recherche et cela récupérera votre solde et l'historique de vos transactions. Par exemple, voici ce que montre notre [compte de donations](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) sur etherscan.io ",
"HELP_17_Title": "17) Pourquoi mon solde n'apparaît-il pas quand je déverrouille mon portefeuille ? ",
"HELP_17_Desc_1": "C'est probablement dû au fait que vous vous trouvez derrière un firewall. L'API que nous utilisons pour obtenir le solde et converir celui-ci est souvent bloquée par des firewalls pour des raisons diverses. Vous êtes toujours capable d'envoyer des transactions mais il vous faut employer une autre méthode pour voir le solde, comme etherscan.io ",
"HELP_18_Title": "18) Où est le fichier de mon portefeuille geth ? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "Vous avez une clef privée et une clef publique. La clef privée peut servir à dériver la clef publique mais l'inverse est impossible. Le fait que l'internet et le monde entier utilise ce système cryptographique signifie que, s'il existait un moyen de dériver la clef privée de la clef publique, le risque que courrait votre Ether serait le moindre des problèmes de tout le monde. ",
"HELP_21_Desc_4": "Cela dit, OUI : si quelqu'un possède votre clef privée, il peut envoyer de l'Ether depuis votre compte, de même que si une personne a le mot de passe de votre email, elle peut lire des mails ou en envoyer, ou si c'est le mot de passe de votre compte en banque, elle peut faire des virements. Vous pouvez télécharger la versoin KEystore de votre clef privée qui est la clef privée chiffrée avec un mot de passe. Cela ressemble à avoir un mot de passe protégé par un autre mot de passe. ",
"HELP_21_Desc_5": "Et OUI, en théorie, on peut taper une chaîne de 64 caractères hexadécimaux jusqu'à en trouver un qui correspond. Il est d'ailleurs possible d'écrire un programme qui vérifie très rapidement des clefs privée aléatoires. C'est ce que l'on appelle utiliser la \"brute force\" ou miner des clefs privées. Beaucoup de monde y a pensé très fort et très longtemps. Quelques serveurs haut de gamme peuvent vérifier plus de 1 million de clefs par seconde. Pourtant, même ce chiffre ne donnerait pas accès à un compte suffisamment approvisionné pour en valoir la chandelle ; il est bien plus probable que vous, vos enfant et vos petits-enfants mourront avant d'obtenir une correspondance. ",
"HELP_21_Desc_6": "Si vous connaissez un peu Bitcoin, [ceci remettra les choses en perspective :](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Pour illustrer l'improbabilité de tout ceci : supposons quqe chaque satoshi de chaque bitcoin qui sera jamais produit soit affecté à sa propre clef privée distincte. La probabilité que, parmi ces clefs, s'en trouvent deux qui correspondent à la même adresse serait d'environ 1 sur 100 quintillons. ",
"HELP_21_Desc_7": "[Si vous voulez un argumentaire un peu plus technique :](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Ces nombres n'ont rien à voir avec la technologie des systèmes ; ce sont les maximums autorisés par la thermodynamique. Et ils impliquent clairement qu'une attaque par brute force contre des clefs de 256 bits restera impossible jusqu'à ce que l'on construise des ordinateurs avec autre chose que de la matière et qu'ils occupent autre chose que l'espace. ",
"HELP_21_Desc_6": "Si vous connaissez un peu Bitcoin, [ceci remettra les choses en perspective :](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Pour illustrer l'improbabilité de tout ceci : supposons quqe chaque satoshi de chaque bitcoin qui sera jamais produit soit affecté à sa propre clef privée distincte. La probabilité que, parmi ces clefs, s'en trouvent deux qui correspondent à la même adresse serait d'environ 1 sur 100 quintillons. ",
"HELP_21_Desc_7": "[Si vous voulez un argumentaire un peu plus technique :](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Ces nombres n'ont rien à voir avec la technologie des systèmes ; ce sont les maximums autorisés par la thermodynamique. Et ils impliquent clairement qu'une attaque par brute force contre des clefs de 256 bits restera impossible jusqu'à ce que l'on construise des ordinateurs avec autre chose que de la matière et qu'ils occupent autre chose que l'espace. ",
"HELP_21_Desc_8": "Cela suppose bien entendu que les clefs sont générées d'une manière totalement aléatoire avec suffisamment d'entropie. C'est le cas des clefs générées ici, tout comme celles de Jaxx et de Mist/geth. Les portefeuilles Ethereum sont tous assez bons de ce point de vue. Les clefs générées par des cerveaux humains ne le sont pas, car ces derniers ne sont pas capables de partir d'un nombre parfaitement aléatoire. Il y a eu des cas d'autres problèmes d'entropie insuffisante ou de nombres imparfaitement aléatoires dans le monde de Bitcoin mais il s'agit là d'un tout autre problème qui peut attendre un peu. ",
"HELP_SecCX_Title": "Sécurité - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Où cette extension sauve-t-elle mes informations ? ",
"HELP_SecCX_Desc_2": "Les informations stockées dans cette extension sont sauvegardée via [chrome.storage](http://chrome.storage/), c'est à dire au même endroit que vos mots de passe dans Chrome. ",
"HELP_SecCX_Desc_2": "Les informations stockées dans cette extension sont sauvegardée via [chrome.storage](https://chrome.storage/), c'est à dire au même endroit que vos mots de passe dans Chrome. ",
"HELP_SecCX_Desc_3": "Quelles informations sont sauvegardées ? ",
"HELP_SecCX_Desc_4": "L'adresse, le surnom, la clef privée sont stockés dans chrome.storage. La clef privée est chiffrée par le mot de passe défini à l'ajout du portefeuille. Le surnom et l'adresse du portefeuille ne sont pas chiffrés. ",
"HELP_SecCX_Desc_5": "Pourquoi le surnom et l'adresse du portefeuille ne sont-ils pas chiffrés ? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -282,7 +282,7 @@
"MSG_info1": "Include the current date so the signature cannot be reused on a different date. ",
"MSG_info2": "Include your nickname and where you use the nickname so someone else cannot use it. ",
"MSG_info3": "Include a specific reason for the message so it cannot be reused for a different purpose. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -522,7 +522,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": " This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -536,12 +536,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -651,3 +651,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -227,7 +227,7 @@
"MYWAL_Content_1": "Figyelmeztetés! Arra készülsz, hogy eltávolítod a tárcádat ",
"MYWAL_Content_2": "Győződj meg róla, hogy **elmentetted a privát kulcsodat és/vagy Keystore fájlodat a jelszóval együtt,** mielőtt törlöd őket. ",
"MYWAL_Content_3": "Ha használni akarod ezt a tárcát a MyEtherWallet CX-szel a jövőben, manuálisan újra hozzá kell majd adnod a privát kulcs/JSON-nal és jelszóval. ",
"VIEWWALLET_Subtitle": "Ez lehetővé teszi számodra, hogy különböző változatú privát kulcsokat tölts le és újranyomtasd a papírtárcádat. Ezt megteheted úgy, hogy [importálod a számládat a Geth/Mist-be](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Ha ellenőrizni akarod a számládat, azt ajánljuk, hogy használj blokklánc explorert mint az [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Ez lehetővé teszi számodra, hogy különböző változatú privát kulcsokat tölts le és újranyomtasd a papírtárcádat. Ezt megteheted úgy, hogy [importálod a számládat a Geth/Mist-be](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Ha ellenőrizni akarod a számládat, azt ajánljuk, hogy használj blokklánc explorert mint az [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Ez lehetővé teszi számodra, hogy különböző változatú privát kulcsokat tölts le és újranyomtasd a papírtárcádat. ",
"VIEWWALLET_SuccessMsg": "Sikerült! Itt vannak a tárcád részletei. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -533,7 +533,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -547,12 +547,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -662,3 +662,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -254,7 +254,7 @@
"MYWAL_Content_1": "Peringatan! Anda akan menghapus Dompet ",
"MYWAL_Content_2": "Pastkan Anda telah **menyimpan private key dan/atau File Keystore File dan password** sebelum menghapus Dompet. ",
"MYWAL_Content_3": "Jika Anda akan memakai dompet ini dengan MyEtherWallet CX Anda ke depan, private key/JSON dan password harus ditambahkan lagi secara manual. ",
"VIEWWALLET_Subtitle": "Memungkinkan Anda untuk mencetak Dompet Kertas dari berbagai format atau versi \"private key\". Hal ini diperlukan pada saat anda ingin [mengimpor akun Anda ke Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jika Anda hanya ingin pengecekan saldo, pakailah salah satu layanan blockchain explorer seperti [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Memungkinkan Anda untuk mencetak Dompet Kertas dari berbagai format atau versi \"private key\". Hal ini diperlukan pada saat anda ingin [mengimpor akun Anda ke Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jika Anda hanya ingin pengecekan saldo, pakailah salah satu layanan blockchain explorer seperti [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Untuk pencetakan Dompet Kertas dari berbagai format \"private key\". ",
"VIEWWALLET_SuccessMsg": "Berhasil! Berikut detil dari dompet Anda. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -223,7 +223,7 @@
"MYWAL_Content_1": "Attenzione! Stai per rimuovere il tuo portafoglio ",
"MYWAL_Content_2": "Assicurati di aver **salvato la chiave privata e/o il file Keystore e la password** prima di rimuoverlo. ",
"MYWAL_Content_3": "Se vorrai utilizzare questo portafoglio con MyEtherWallet CX in futuro, dovrai ri-aggiungerlo manualmente tramite la chiave privata/JSON e password. ",
"VIEWWALLET_Subtitle": "Qui è possibile scaricare diverse versioni delle chiavi private e ristampare il portafoglio cartaceo. Potresti volerlo fare per [importare il tuo conto in Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Se vuoi controllare il tuo saldo, ti consigliamo di utilizzare uno strumento per esplorare la *blockchain* come [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Qui è possibile scaricare diverse versioni delle chiavi private e ristampare il portafoglio cartaceo. Potresti volerlo fare per [importare il tuo conto in Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Se vuoi controllare il tuo saldo, ti consigliamo di utilizzare uno strumento per esplorare la *blockchain* come [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Qui è possibile scaricare diverse versioni delle chiavi private e ristampare il portafoglio cartaceo. ",
"VIEWWALLET_SuccessMsg": "Perfetto! Questi sono i dettagli del tuo portafoglio. ",
"VIEWWALLET_ShowPrivKey": "(mostra)",
@ -521,7 +521,7 @@
"HELP_15_Title": "15) Perché il conto che ho appena creato non risulta nello strumento per esplorare la *blockchain*? (es: etherchain, etherscan) ",
"HELP_15_Desc_1": "I conti vengono mostrati in quegli strumenti solamente dopo che c'è stata un'attività sul conto in questione&mdash;ad esempio, dopo che ci hai trasferito degli ether. ",
"HELP_16_Title": "16) Come faccio a controllare il saldo del mio conto? ",
"HELP_16_Desc_1": "Puoi usare uno strumento per l'esplorazione della *blockchain* come [etherscan.io](http://etherscan.io/). Incolla il tuo indirizzo nella barra di ricerca e vedrai il tuo indirizzo e lo storico delle transazioni. Ad esempio, questo è come si presenta il nostro [conto donazioni](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) su etherscan.io ",
"HELP_16_Desc_1": "Puoi usare uno strumento per l'esplorazione della *blockchain* come [etherscan.io](https://etherscan.io/). Incolla il tuo indirizzo nella barra di ricerca e vedrai il tuo indirizzo e lo storico delle transazioni. Ad esempio, questo è come si presenta il nostro [conto donazioni](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) su etherscan.io ",
"HELP_17_Title": "17) Perché non viene mostrato il saldo quando sblocco il mio portafoglio? ",
"HELP_17_Desc_1": "Probabilmente perché sei dietro a un firewall. Le API che utilizziamo per ottenere il saldo e convertirlo sono spesso bloccate dai firewall per qualche ragione. Sarai ancora in grado di inviare transazioni, dovrai solo usare un metodo diverso per vedere il tuo saldo, come etherscan.io ",
"HELP_18_Title": "18) Dov'è il mio file portafoglio di geth? ",
@ -535,12 +535,12 @@
"HELP_21_Desc_3": "In tutto ciò tu hai una chiave privata e una chiave pubblica. Dalla chiave privata si può derivare la chiave pubblica, ma dalla chiave pubblica non si può risalire alla chiave privata. Il fatto che Internet e i segreti del mondo usino questa crittografia significa che se ci fosse un modo per ottenere una chiave privata da una chiave pubblica, i tuoi ether persi sarebbero l'ultimo dei problemi. ",
"HELP_21_Desc_4": "Ora, detto ciò, SÌ se qualcun altro ha la tua chiave privata allora può effettivamente inviare ether dal tuo conto. Proprio come se qualcuno ha la password della tua mail può leggere e spedire la tua mail, o se ha la password del tuo conto bancario potrebbe fare dei trasferimenti. Potresti scaricare la versione Keystore della tua chiave privata che è la chiave privata crittografata con una password. È come avere una password che è a sua volta protetta da un'altra password. ",
"HELP_21_Desc_5": "E SÌ, in teoria potresti semplicemente digitare stringhe di 64 caratteri esadecimali fino a trovarne una che corrisponda. Infatti, persone intelligenti potrebbero scrivere un programma per controllare molto rapidamente chiavi private casuali. Questo procedimento è conosciuto come *\"attacco a forza bruta\"* o *\"mining\"* delle chiavi private. Ci hanno pensato molto e a lungo. Con qualche server di altissimo livello potrebbero essere in grado di controllare più di 1 milione di chiavi al secondo. Però nemmeno controllarne così tante al secondo porterebbe all'accesso in una maniera tale da rendere il costo dell'utilizzo di quei server vagamente vicino all'essere proficuo - è più probabile che tu, e i tuoi pronipoti, moriate prima di trovare una corrispondenza. ",
"HELP_21_Desc_6": "Se sai qualcosa di Bitcoin, [questo ti darà un'idea:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *\"Per illustrare quanto ciò sia improbabile: supponi che ogni satoshi di ogni bitcoin che sarà mai generato sia inviato a una sua chiave privata unica. La probabilità che fra queste chiavi ce ne possano essere due che corrispondano allo stesso indirizzo è circa di uno in 100 trilioni\"*. ",
"HELP_21_Desc_7": "[Se preferisci qualcosa di un po' più tecnico:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *\"Questi numeri non hanno niente a che fare con la tecnologia dei dispositivi; sono i massimi che la termodinamica consente. E implicano fortemente che gli attacchi a forza bruta contro le chiavi a 256 bit saranno impraticabili almeno fino a quando i computer non saranno costruiti con qualcosa di diverso dalla materia e non occuperanno qualcosa di diverso dallo spazio.\"* ",
"HELP_21_Desc_6": "Se sai qualcosa di Bitcoin, [questo ti darà un'idea:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *\"Per illustrare quanto ciò sia improbabile: supponi che ogni satoshi di ogni bitcoin che sarà mai generato sia inviato a una sua chiave privata unica. La probabilità che fra queste chiavi ce ne possano essere due che corrispondano allo stesso indirizzo è circa di uno in 100 trilioni\"*. ",
"HELP_21_Desc_7": "[Se preferisci qualcosa di un po' più tecnico:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *\"Questi numeri non hanno niente a che fare con la tecnologia dei dispositivi; sono i massimi che la termodinamica consente. E implicano fortemente che gli attacchi a forza bruta contro le chiavi a 256 bit saranno impraticabili almeno fino a quando i computer non saranno costruiti con qualcosa di diverso dalla materia e non occuperanno qualcosa di diverso dallo spazio.\"* ",
"HELP_21_Desc_8": "Certo, tutto ciò assume che le chiavi siano generate in una maniera veramente casuale e con sufficiente entropia. Le chiavi generate qui soddisfano questi criteri, come anche Jaxx e Mist/geth. I portafogli Ethereum sono tutti piuttosto buoni. Le chiavi generate dai *brainwallet* non lo sono, dal momento che il cervello di una persona non è capace di creare un seme veramente casuale. Ci sono stati un numero di altri problemi relativi alla mancanza di entropia o a semi non generati in maniera veramente casuale nel mondo di Bitcoin, ma quella è un'altra questione di cui non parleremo oggi. ",
"HELP_SecCX_Title": "Sicurezza - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Dov'è che questa estensione salva le mie informazioni? ",
"HELP_SecCX_Desc_2": "Le informazioni che memorizzi in questa estensione di Chrome sono salvate tramite [chrome.storage](http://chrome.storage/). - è lo stesso posto in cui vengono salvate le tue password quando le salvi in Chrome. ",
"HELP_SecCX_Desc_2": "Le informazioni che memorizzi in questa estensione di Chrome sono salvate tramite [chrome.storage](https://chrome.storage/). - è lo stesso posto in cui vengono salvate le tue password quando le salvi in Chrome. ",
"HELP_SecCX_Desc_3": "Che informazioni sono salvate? ",
"HELP_SecCX_Desc_4": "L'indirizzo, nome, e la chiave privata sono memorizzati in chrome.storage. La chiave privata è crittografata utilizzando la password che hai impostato quando hai aggiunto il portafoglio. Il nome e l'indirizzo del portafoglio non sono crittografati. ",
"HELP_SecCX_Desc_5": "Perché il nome e l'indirizzo del portafoglio non sono crittografati? ",
@ -650,3 +650,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -294,7 +294,7 @@
"MSG_info1": "この署名が別の日付で再度使われないようにするために、現時点の日付を入れてください。 ",
"MSG_info2": "他人に使われないようにするため、あなたのニックネームとそれが使われるところを入れてください。 ",
"MSG_info3": "異なった目的で使用されないようにするために、利用目的を入れてください。 ",
"VIEWWALLET_Subtitle": "異なったバージョンの秘密鍵をダウンロードしたり、お財布紙情報を再印刷することができます。[import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)する時に必要です。残高をチェックするためには、[etherscan.io](http://etherscan.io/)のようなブロックチェーンエクスプローラーサービスを使う事をおすすめします。 ",
"VIEWWALLET_Subtitle": "異なったバージョンの秘密鍵をダウンロードしたり、お財布紙情報を再印刷することができます。[import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)する時に必要です。残高をチェックするためには、[etherscan.io](https://etherscan.io/)のようなブロックチェーンエクスプローラーサービスを使う事をおすすめします。 ",
"VIEWWALLET_Subtitle_Short": "異なったバージョンの秘密鍵をダウンロードしたり、お財布紙情報を再印刷することができます。 ",
"VIEWWALLET_SuccessMsg": "成功しました! お財布の詳細は以下の通りです。 ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -281,7 +281,7 @@
"MSG_info1": "서명을 다른 날짜에 재사용하지 못하도록 현재의 날짜를 포함해주세요. ",
"MSG_info2": "타인이 사용하지 못하도록 당신의 닉네임을 포함해주세요 ",
"MSG_info3": "다른 용도로 사용되는 것을 막으려면 세부적인 내용을 메시지에 포함해주세요. ",
"VIEWWALLET_Subtitle": "다른 버전의 개인 키를 다운로드하거나 종이 지갑 정보를 다시 인쇄할 수 있습니다. [계좌를 Geth/Mist로 가져오기](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)를 진행할 때 필요합니다. 잔액을 확인하려면 [etherscan.io](http://etherscan.io/)과 같은 블록체인 조회 서비스를 사용하는 것을 권장합니다. ",
"VIEWWALLET_Subtitle": "다른 버전의 개인 키를 다운로드하거나 종이 지갑 정보를 다시 인쇄할 수 있습니다. [계좌를 Geth/Mist로 가져오기](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)를 진행할 때 필요합니다. 잔액을 확인하려면 [etherscan.io](https://etherscan.io/)과 같은 블록체인 조회 서비스를 사용하는 것을 권장합니다. ",
"VIEWWALLET_Subtitle_Short": "다른 버전의 개인 키를 다운로드하거나 종이 지갑 정보를 다시 인쇄 할 수 있습니다. ",
"VIEWWALLET_SuccessMsg": "성공했습니다! 지갑의 세부사항은 다음과 같습니다. ",
"VIEWWALLET_ShowPrivKey": "(보기) ",
@ -522,7 +522,7 @@
"HELP_15_Title": "15) 방금 만든 계정이 블록체인 탐색기에 표시되지 않는 이유는 뭔가요? (예, etherchain, etherscan) ",
"HELP_15_Desc_1": "계좌는 거래 활동이 있을 경우에만 블록체인 탐색기에 표시됩니다. 예를 들어, 이더리움을 계좌로 이동시키면 계좌가 활성화됩니다. ",
"HELP_16_Title": "16) 내 계좌의 잔액을 어떻게 확인하나요? ",
"HELP_16_Desc_1": "[etherscan.io] (http://etherscan.io/) 와 같은 블록체인 탐색기를 사용할 수 있습니다. 주소를 검색 창에 붙여넣으면 주소와 거래 내역이 표시됩니다. 예를 들어, 우리의 [기부 계정]은 (http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) 과 같습니다. ",
"HELP_16_Desc_1": "[etherscan.io] (https://etherscan.io/) 와 같은 블록체인 탐색기를 사용할 수 있습니다. 주소를 검색 창에 붙여넣으면 주소와 거래 내역이 표시됩니다. 예를 들어, 우리의 [기부 계정]은 (https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) 과 같습니다. ",
"HELP_17_Title": "17) 내 지갑에서 잔액이 표시되지 않는 이유는 뭔가요? ",
"HELP_17_Desc_1": "그 이유는 방화벽 때문입니다. 우리가 잔액 정보를 얻고 잔액 정보를 변환하는 데 사용하는 API는 어떤 이유로 든 방화벽에 의해 차단되는 경우가 많습니다. 사용자는 계속해서 트랜잭션을 보낼 수 있습니다. 당신은 단지 잔액을 확인하기 위해 etherscan.io 블록체인 탐색 사이트와 같은 다른 방법을 사용해야 될 수 있습니다. ",
"HELP_18_Title": "18) 내 geth 지갑 파일이 어디 있나요? ",
@ -536,12 +536,12 @@
"HELP_21_Desc_3": "이곳에는 개인 키와 공개 키가 존재합니다. 개인 키는 공개 키를 생성시킬 수 있지만, 공개 키는 개인 키로 되돌릴 수 없습니다. 인터넷과 세계의 비밀들이 이 암호를 사용하고 있다는 사실은, 공개 키에서 개인 키로 되돌리는 방법이 있다면 이것이 한 사람의 문제가 아니라 모든 사람의 문제가 될 것입니다. ",
"HELP_21_Desc_4": "만약 누군가가 당신의 개인 키를 소지하고 있다면 당신의 계좌에서 이더리움을 보낼 수 있게 됩니다. 이 얘기는 누군가가 당신의 이메일의 비밀번호를 알고 있다면 당신의 이메일을 읽을 수 있으며, 이메일이나 누군가가 출금할 수 있도록 당신의 은행 계좌 비밀번호를 전송할 수 있다는 것과 마찬가지입니다. 당신은 비밀번호로 암호화된 개인 키인 ‘개인 키의 Keystore 버전’을 다운로드 할 수 있습니다. 이것은 다른 암호로 보호되는 비밀번호를 갖게 되는 것입니다. ",
"HELP_21_Desc_5": "그리고 이론상 누군가가 당신의 계좌를 찾을 때까지 64개의 16진수 문자열을 대입한다면 당신의 계좌가 도난당할 수도 있습니다. 사실 똑똑한 사람들은 임의의 개인 키를 매우 빠르게 검사할 수 있는 프로그램을 만들 수 있습니다. 이것은 ‘무차별 대입 공격’ 또는 ‘개인 키 마이닝’이라고 알려져 있습니다. 사람들은 이것에 대해 오랫동안 고민해 왔습니다. 2~3개의 초고속 서버로 그들은 초당 100만 개 이상의 키를 검사할 수 있습니다. 그러나 초당 수많은 것들은 검사하는 것조차 이 서버를 운영하는 비용을 감당하는게 무의미한 일이 될 것입니다. 개인 키를 알아내기 위해선 어마어마한 시간이 걸립니다. ",
"HELP_21_Desc_6": "당신이 비트코인에 대해 이해하고 있는 사람이라면 [이 링크로 앞으로 상황을 예측할 수 있을 것입니다.](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-willpeple) 이것이 어떻게 되는 것인지 설명하자면 : 여태껏 생성된 비트코인의 모든 사토시가 고유한 자체의 개인 키로 전송했다고 가정해봅시다. 두 가지 키가 같은 키에 해당할 확률은 약 100억분의 1입니다. ",
"HELP_21_Desc_7": "[좀 더 기술적인 것을 원한다면:] (http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *이 숫자는 장치 기술과 아무런 관련이 없습니다. 그것들은 열역학이 허용하는 최대치입니다. 그리고 그것들은 256bit 키에 대한 무차별 대입 공격이 해당 컴퓨터가 다른 물질로 변할 때까지 엄청난 시간이 흘러도 불가능하다는 것을 강하게 암시합니다. ",
"HELP_21_Desc_6": "당신이 비트코인에 대해 이해하고 있는 사람이라면 [이 링크로 앞으로 상황을 예측할 수 있을 것입니다.](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-willpeple) 이것이 어떻게 되는 것인지 설명하자면 : 여태껏 생성된 비트코인의 모든 사토시가 고유한 자체의 개인 키로 전송했다고 가정해봅시다. 두 가지 키가 같은 키에 해당할 확률은 약 100억분의 1입니다. ",
"HELP_21_Desc_7": "[좀 더 기술적인 것을 원한다면:] (https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *이 숫자는 장치 기술과 아무런 관련이 없습니다. 그것들은 열역학이 허용하는 최대치입니다. 그리고 그것들은 256bit 키에 대한 무차별 대입 공격이 해당 컴퓨터가 다른 물질로 변할 때까지 엄청난 시간이 흘러도 불가능하다는 것을 강하게 암시합니다. ",
"HELP_21_Desc_8": "물론, 이 모든 개인 키가 정말로 무작위 방식으로 충분한 엔트로피를 갖고 생성된다고 가정합시다. 이곳에서 생성된 키는 Jaxx 와 Mist/geth와 마찬가지로 해당 기준을 충족시킵니다. 이더리움 지갑들은 모두 좋은 지갑들입니다. 사람의 뇌가 정말로 무작위적인 시드를 만들어내지 못하기 때문에 사람에 의해 만들어진 지갑으로 만들어진 키는 썩 좋지 않습니다. 비트코인 세계에서는 정말로 무작위 방식으로 생성되고 있지 않은 엔트로피나 시드가 부족한 것에 관해 수많은 문제가 있었습니다. 하지만 그것은 언젠가 해결이 될 날을 기다릴 수 있는 것은 별개의 문제입니다. ",
"HELP_SecCX_Title": "보안 - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "이 확장 프로그램이 내 정보를 어디에 저장하나요? ",
"HELP_SecCX_Desc_2": "당신이 Chrome 확장 프로그램에 저장한 정보는 [Chrome.storage](http://chrome.storage/)를 통해 저장됩니다. - 이것은 당신이 Chrome에 비밀번호를 저장한 위치와 같은 위치에 저장됩니다. ",
"HELP_SecCX_Desc_2": "당신이 Chrome 확장 프로그램에 저장한 정보는 [Chrome.storage](https://chrome.storage/)를 통해 저장됩니다. - 이것은 당신이 Chrome에 비밀번호를 저장한 위치와 같은 위치에 저장됩니다. ",
"HELP_SecCX_Desc_3": "어떤 정보가 저장되나요? ",
"HELP_SecCX_Desc_4": "주소, 닉네임, 개인 키가 Chrome 스토리지에 저장됩니다. 개인 키는 지갑을 추가할 때 생성된 비밀번호로 암호화됩니다. 닉네임, 지갑 주소는 암호화되지 않습니다. ",
"HELP_SecCX_Desc_5": "닉네임과 지갑 주소는 왜 암호화되지 않나요? ",
@ -651,3 +651,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -280,7 +280,7 @@
"MSG_info1": "Voeg de huidige datum toe zodat je handtekening niet opnieuw kan worden gebruikt op een andere datum. ",
"MSG_info2": "Voeg je nickname toe en waar je deze gebruikt zodat anderen deze niet kunnen gebruiken. ",
"MSG_info3": "Geef een specifieke reden op voor de boodschap, zodat deze niet kan worden hergebruikt voor een ander doel. ",
"VIEWWALLET_Subtitle": "Hiermee kun je verschillende versies van je prive sleutels downloaden en je papieren wallet opnieuw afdrukken. Je zou dit kunnen doen om [je account in Geth/Mist te importeren](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Als je enkel je saldo wilt raadplegen, adviseren we je om gebruik te maken van een blockchain explorer zoals [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Hiermee kun je verschillende versies van je prive sleutels downloaden en je papieren wallet opnieuw afdrukken. Je zou dit kunnen doen om [je account in Geth/Mist te importeren](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Als je enkel je saldo wilt raadplegen, adviseren we je om gebruik te maken van een blockchain explorer zoals [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Hiermee kun je verschillende versies van je prive sleutels downloaden en je papieren wallet opnieuw afdrukken. ",
"VIEWWALLET_SuccessMsg": "Gelukt! Hier zijn je wallet details. ",
"VIEWWALLET_ShowPrivKey": "(laat zien)",
@ -521,7 +521,7 @@
"HELP_15_Title": "15) Hoe komt het dat het wallet wat ik zojuist heb aangemaakt niet in de blockchain explorer terug te vinden is? (bijvoorbeeld: etherchain, etherscan) ",
"HELP_15_Desc_1": "Adresen zullen enkel in een blockchain explorer worden weergegeven zodra er activiteit op een account heeft plaats gevonden. Bijvoorbeeld, zodra je er wat Ether naar toe verzonden hebt. ",
"HELP_16_Title": "16) Hoe check ik het saldo van mijn account? ",
"HELP_16_Desc_1": "Je kunt hiervoor een blockchain explorer gebruiken zoals bijvoorbeeld [etherscan.io](http://etherscan.io/). Plak daar je adres in de zoekbalk en je adres en transactie geschiedenis zullen worden getoond. Bekijk bijvoobeeld hoe ons [donatie account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) eruit ziet op etherscan.io ",
"HELP_16_Desc_1": "Je kunt hiervoor een blockchain explorer gebruiken zoals bijvoorbeeld [etherscan.io](https://etherscan.io/). Plak daar je adres in de zoekbalk en je adres en transactie geschiedenis zullen worden getoond. Bekijk bijvoobeeld hoe ons [donatie account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) eruit ziet op etherscan.io ",
"HELP_17_Title": "17) Waarom wordt mijn saldo niet weergegeven nadat ik mijn wallet heb ontsleuteld? ",
"HELP_17_Desc_1": "Dit wordt zeer waarschijnlijk veroorzaakt door het feit dat je achter een firwall zit. De API waarvan we gebruik maken om je saldo op te halen en te converteren wordt vaak geblokkeerd door firewalls om wat voor reden dan ook. Het is nog steeds mogelijk om transacties te verzenden, je hebt enkel een andere methode nodig om je saldo the checken, zoals bijvoorbeeld etherscan.io ",
"HELP_18_Title": "18) Waar is mijn Geth wallet bestand? ",
@ -535,12 +535,12 @@
"HELP_21_Desc_3": "Hierbij heb je een prive sleutel en een publieke sleutel. Vanuit de prive sleutel kan de publieke sleutel afgeleid worden, maar de publieke sleutel kan niet terug omgezet worden in de prive sleutel. Het feit dat het internet en s werelds geheimen gebruik maken van deze cryptografie betekend dat indien er een manier is om van publieke sleutel naar prive sleutel te gaan, dat jouw verloren ether wel het minste van een ieders probleem is. ",
"HELP_21_Desc_4": "Nu we dat duidelijk hebben: JA, als iemand anders je prive sleutel heeft kunnen ze inderdaad ether vanuit jouw account versturen. Net zoals dat iemand die je wachtwoord van je email heeft, je email kan lezen en sturen, of met het wachtwoord van je bank rekening geld kunnen overmaken. Je zou de Keystore versie van je prive sleutel kunnen downloaden, dat is je prive sleutel die is versleuteld (encrypted) met een wachtwoord. Dit is alsof je een wachtwoord hebt want je vervolgens nog eens beveiligd met een ander wachtwoord. ",
"HELP_21_Desc_5": "En JA, in theorie zou je een serie van 64 hexadecimale karakters kunnen intypen tot je er een hebt die matched. Sterker nog, een slim persoon zou een programma kunnen schrijven om heel snel willekeurige prive sleutels te controleren. Dit wordt ook wel \"brute-forcing\" van prive sleutels genoemd. Mensen hebben hier lang en goed over nagedacht. Met enkele krachtige servers zouden ze misschien wel zon miljoen sleutels per seconde kunnen controleren. Echter, zelfs wanneer er zoveel sleutels per seconde gecontroleed kunnen worden zou de opbrengst ervan niet eens in de buurt komen bij de kosten om de servers te onderhouden - het is waarschijnlijker dat jij, en je achterkleinkinderen, zijn overleden voordat je een match vind. ",
"HELP_21_Desc_6": "Als je Bitcoin een beetje kent, [biedt dit een aardig perspectief:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[Als je het iets technischer wilt:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "Als je Bitcoin een beetje kent, [biedt dit een aardig perspectief:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[Als je het iets technischer wilt:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Uiteraard gaat bovenstaande er vanuit dat de sleutels worden gegenereerd met een volledige willekeur & met afdoende entropie. De sleutels die hier gegenreerd worden voldoen aan dat criterium, net als Jaxx en Mist/geth. De Ethereum wallets zijn allemaal best goed. Sleutels gegenereerd door \"brainwallets\" doen dit niet, omdat een het brein van een persoon niet capabel is om een werkelijk willekeurige \"seed\" te maken. Er zijn een heel aantal kwesties geweest met betrekking tot het gebrek entropie en \"seeds\" die niet in een volledig willekeurige manier waren gemaakt in Bitcoin-land, maar dat is een ander verhaal en kan wachten tot een andere keer. ",
"HELP_SecCX_Title": "Beveiliging - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Waar bewaard deze extentie mijn informatie? ",
"HELP_SecCX_Desc_2": "De informatie die je bewaard in deze Chrome Extensie wordt opgeslagen via [chrome.storage](http://chrome.storage/). - dit is dezelfde plek als waar je wachtwoorden staan opgeslagen als je je wachtwoorden bewaard in Chrome. ",
"HELP_SecCX_Desc_2": "De informatie die je bewaard in deze Chrome Extensie wordt opgeslagen via [chrome.storage](https://chrome.storage/). - dit is dezelfde plek als waar je wachtwoorden staan opgeslagen als je je wachtwoorden bewaard in Chrome. ",
"HELP_SecCX_Desc_3": "Welke informatie wordt bewaard? ",
"HELP_SecCX_Desc_4": "Het adres, nickname en prive sleutel worden bewaard in chrome.storage. De prive sleutel is versleuteld (encrypted) met het wachtwoord wat je hebt ingesteld toen je je wallet hebt toegevoegd. De nickname en het wallet adres zijn niet versleuteld. ",
"HELP_SecCX_Desc_5": "Waarom zijn de nickname en adres niet versleuteld? ",
@ -650,3 +650,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -291,7 +291,7 @@
"MYWAL_Content_1": "Advarsel! Du er i ferd med å fjerne lommeboken din ",
"MYWAL_Content_2": "Vær sikker på at du har **lagret den private nøkkelen/JSON-filen og passordet** tilknyttet denne lommeboken før du fjerner den. ",
"MYWAL_Content_3": "Hvis du ønsker å bruke denne lommeboken med din MyEtherWallet Chrome-utvidelse i fremtiden, må du manuelt legge den til igjen ved å bruke den private nøkkelen/JSON og passord. ",
"VIEWWALLET_Subtitle": "Dette gir deg muligheten til å laste ned ulike versjoner av private nøkler og skrive ut papirlommeboken din på nytt. Du vil kanskje gjøre dette for å [importere kontoen din til Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Hvis du bare ønsker å sjekke saldoen din, anbefaler vi at du bruker en \"blockchain explorer\" som f.eks. [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Dette gir deg muligheten til å laste ned ulike versjoner av private nøkler og skrive ut papirlommeboken din på nytt. Du vil kanskje gjøre dette for å [importere kontoen din til Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Hvis du bare ønsker å sjekke saldoen din, anbefaler vi at du bruker en \"blockchain explorer\" som f.eks. [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Dette gir deg muligheten til å laste ned ulike versjoner av private nøkler og skrive ut papirlommeboken din på nytt. ",
"VIEWWALLET_SuccessMsg": "Suksess! Her er detaljene om din lommebok. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Hvorfor har ikke kontoen jeg nettopp opprettet dukket opp i blokkjede-utforskeren? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Kontoer vil kun dukke opp i en blokkjede-utforsker når kontoen har hatt aktivitet&mdash;for eksempel, når du har overført Ether til den. ",
"HELP_16_Title": "16) Hvordan kan jeg sjekke saldoen på kontoen min? ",
"HELP_16_Desc_1": "Du kan bruke en blokkjede-utforsker som [etherscan.io](http://etherscan.io/). Lim inn adressen i søkefeltet og den vil finne fram adressen og transaksjonshistorikken. For eksempel, her ser du hvordan vår [donasjonskonto](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) ser ut på etherscan.io ",
"HELP_16_Desc_1": "Du kan bruke en blokkjede-utforsker som [etherscan.io](https://etherscan.io/). Lim inn adressen i søkefeltet og den vil finne fram adressen og transaksjonshistorikken. For eksempel, her ser du hvordan vår [donasjonskonto](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) ser ut på etherscan.io ",
"HELP_17_Title": "17) Hvorfor vises ikke saldoen min når jeg låser opp lommeboken min? ",
"HELP_17_Desc_1": "Dette er mest sannsynlig fordi du er bak en brannmur. API-en vi bruker for å innhente saldoen blokkeres ofte av brannmurer av ymse årsaker. Du vil fortsatt være i stand til å sende transaksjoner, du må bare bruke en annen metode for å se nevnte saldo, som etherscan.io ",
"HELP_18_Title": "18) Hvor er min geth lommebok-fil ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "I denne har du en privat nøkkel og en offentlig nøkkel. Den private nøkkelen kan utlede den offentlige nøkkelen, men den offentlige nøkkelen kan ikke brukes for å finne den private nøkkelen. Det faktum at internett og verdens hemmeligheter bruker denne kryptografien betyr at hvis det blir funnet en måte å gå fra offentlige til private nøkler på, så vil dine tapte Ether være det minste av alles problemer. ",
"HELP_21_Desc_4": "Når det er sagt, JA, hvis noen andre har din private nøkkel, så kan de såvisst sende ether fra din konto. Akkurat som hvis noen har passordet til e-posten din, så kan de lese og sende din e-post, eller passordet til bankkontoen din, så kan de overføre penger. Du kunne laste ned keystore-versjonen av den private nøkkelen din, som er den private nøkkelen som er kryptert med et passord. Dette blir som å ha et passord som er beskyttet av et annet passord. ",
"HELP_21_Desc_5": "og JA, i teorien kunne du bare taste inn en streng med 64 hexadesimaltegn helt dil du fant en som passet. Faktisk kunne smarte folk skrive et program som svært hurtig kunne sjekke tilfeldige private nøkler. Dette kalles \"brute-forcing\" eller \"mining\" private nøkler. Folk har tenkt lenge og hardt på dette. Med noen få svært gode servere, kunne de kanskje klare å sjekke >1M nøkler/sekund. Likevel, selv når så mange sjekkes per sekund, ville det ikke gi tilgang midler som ville gjøre det i nærheten av å være lønnsomt å kjøre disse serverne. - Det er mer sannsynlig at du, eller dine oldebarn, vil dø før du får en match. ",
"HELP_21_Desc_6": "Hvis du vet noe om Bitcoin, [dette vil sette det i perspektiv:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *For å illustrere hvor usannsynlig det er: anta at alle satoshi av alle bitcoin som noensinne blir generert ble sendt til hver sin egen unike private nøkkel. Sannsynligheten for at det blant disse nøklene kunne være to som ville korrespondere med samme adresse er ca 1 til 10^20. ",
"HELP_21_Desc_7": "[Hvis du ønsker en mer teknisk forklaring:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Disse tallene har ikke noe å gjøre med teknologien til enhetene; de er det maksimale som termodynamikken vil tillate. Og de impliserer sterkt at \"brute-force\"-angrep mot 256-bit nøkler vil være uoppnåelig fram til datamaskiner lages av noe annet enn materie og befinner seg i noe annet enn rom. ",
"HELP_21_Desc_6": "Hvis du vet noe om Bitcoin, [dette vil sette det i perspektiv:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *For å illustrere hvor usannsynlig det er: anta at alle satoshi av alle bitcoin som noensinne blir generert ble sendt til hver sin egen unike private nøkkel. Sannsynligheten for at det blant disse nøklene kunne være to som ville korrespondere med samme adresse er ca 1 til 10^20. ",
"HELP_21_Desc_7": "[Hvis du ønsker en mer teknisk forklaring:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Disse tallene har ikke noe å gjøre med teknologien til enhetene; de er det maksimale som termodynamikken vil tillate. Og de impliserer sterkt at \"brute-force\"-angrep mot 256-bit nøkler vil være uoppnåelig fram til datamaskiner lages av noe annet enn materie og befinner seg i noe annet enn rom. ",
"HELP_21_Desc_8": "Selvsagt betinger alt dette at nøkler blir generert på en virkelig tilfeldig måte & med tilstrekkelig entropi. Nøklene som genereres her tilfredsstiller dette kriteriet, det samme gjør Jaxx og Mist/geth. Alle Ethereum-lommebøker er OK. Nøkler som genereres av \"brainwallets\" er ikke like gode, siden en persons hjerne ikke er i stand til å lage en virkelig tilfeldig \"seed\". Det har vært noen andre tilfeller av manglende entropi eller \"seeds\" som ikke er generert på en virkelig tilfeldig måte i Bitcoin-land, men det er en historie som kan vente til en annen dag. ",
"HELP_SecCX_Title": "Datasikkerhet - MyEtherWallet CX (Chrome-utvidelsen) ",
"HELP_SecCX_Desc_1": "Hvor lagrer denne utvidelsen informasjonen min? ",
"HELP_SecCX_Desc_2": "Informasjonen som du lager i denne Chrome-utvidelsen lagres via [chrome.storage](http://chrome.storage/). - dette er samme sted som passordene dine lagres når du lagrer passord i Chrome. ",
"HELP_SecCX_Desc_2": "Informasjonen som du lager i denne Chrome-utvidelsen lagres via [chrome.storage](https://chrome.storage/). - dette er samme sted som passordene dine lagres når du lagrer passord i Chrome. ",
"HELP_SecCX_Desc_3": "Hvilken informasjon lages? ",
"HELP_SecCX_Desc_4": "Adresser, kallenavn og private nøkler lagres i chrome.storage. Den private nøkkelen er kryptert ved hjelp av passordet du satte da du la til lommeboken. Kallenavn og lommebok-adresser er ikke kryptert. ",
"HELP_SecCX_Desc_5": "Hvorfor er ikke kallenavn og lommebok-adresser kryptert? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -237,7 +237,7 @@
"MYWAL_Content_1": "Uwaga! Zaraz usuniesz swój portfel ",
"MYWAL_Content_2": "Upewnij się, że **zapisałeś klucz prywatny/plik Keystore i hasło** powiązane z tym portfelem zanim je usuniesz. ",
"MYWAL_Content_3": "Jeśli będziesz chciał w przyszłości używać ten portfel ze swoim MyEtherWallet CX, będziesz musiał go ponownie dodać używając klucza prywatnego/pliku JSON i hasła. ",
"VIEWWALLET_Subtitle": "Ta zakładka pozwoli Ci na odczyt kluczy prywatnych, pobranie kopii portfeli oraz wydrukowanie portfeli papierowych. Pobrane za jej pomocą portfele możesz [zaimportować do Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jeśli chcesz sprawdzić stan Twojego konta, zalecamy użyć eksploratora bloków np. [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Ta zakładka pozwoli Ci na odczyt kluczy prywatnych, pobranie kopii portfeli oraz wydrukowanie portfeli papierowych. Pobrane za jej pomocą portfele możesz [zaimportować do Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Jeśli chcesz sprawdzić stan Twojego konta, zalecamy użyć eksploratora bloków np. [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Ta zakładka pozwala Ci na pobranie różnych typów kluczy prywatnych oraz ponowne wydrukowanie portfeli papierowych. ",
"VIEWWALLET_SuccessMsg": "Sukces! Oto dane twojego portfela. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,9 +532,9 @@
"HELP_15_Title": "15) Dlaczego portfel, który właśnie wygenerowałem nie pokazuje się w eksploratorze bloków? (np. etherchain, etherscan) ",
"HELP_15_Desc_1": "Adres pojawi się w eksploratorze bloków dopiero jak adres portfela będzie uczestniczył w jakichś transakcjach, np. jak wyślesz do niego jakieś środki. ",
"HELP_16_Title": "16) Jak sprawdzić stan mojego konta? ",
"HELP_16_Desc_1": "Możesz użyć eksploratora bloków jak [etherscan.io](http://etherscan.io/). Wklej swój adres w wyszukiwarkę na stronie eksploratora, pokaże ona stan Twojego konta oraz historię transakcji. Tak na przykład wygląda nasze [konto donacji](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) na etherscan.io. ",
"HELP_16_Desc_1": "Możesz użyć eksploratora bloków jak [etherscan.io](https://etherscan.io/). Wklej swój adres w wyszukiwarkę na stronie eksploratora, pokaże ona stan Twojego konta oraz historię transakcji. Tak na przykład wygląda nasze [konto donacji](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) na etherscan.io. ",
"HELP_17_Title": "17) Dlaczeg stan mojego konta nie pojawia się, kiedy odblokowuje mój portfel? ",
"HELP_17_Desc_1": "Najprawdopodobniej przyczyną tego jest firewall. API, które używamy do odczytu stanu konta oraz jego konwersji jest często blokowane przez firewall z różnych przyczyn. Wciąż możesz wysyłać transakcje, jednak stan konta musisz sprawdzać w inny sposób, np. na [etherscan.io](http://etherscan.io/) ",
"HELP_17_Desc_1": "Najprawdopodobniej przyczyną tego jest firewall. API, które używamy do odczytu stanu konta oraz jego konwersji jest często blokowane przez firewall z różnych przyczyn. Wciąż możesz wysyłać transakcje, jednak stan konta musisz sprawdzać w inny sposób, np. na [etherscan.io](https://etherscan.io/) ",
"HELP_18_Title": "18) Gdzie jest plik mojego portfela w geth? ",
"HELP_19_Title": "19) Gdzie jest plik mojego portfela w Mist? ",
"HELP_19_Desc_1": "Pliki programu Mist można znaleźć zazwyczaj w lokalizacjach wymienionych w pkt. 18, ale prościej jest uruchomić Mist, wybrać \"Accounts\" w górnym pasku, następnie \"Backup\" i \"Accounts\". Otworzy się folder, w którym znajdują się wspomniane pliki. ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "W tego typu zabezpieczeniu mamy 2 klucze: klucz prywatny i klucz publiczny. Z klucza prywatnego możemy szybko otrzymać klucz publiczny, ale otrzymanie klucza prywatnego z klucza publicznego jest niemożliwe. Biorąc pod uwagę, że cały internet i wszystkie sekrety świata używają tej metody kryptograficznej oznacza, że gdyby istniał sposób na otrzymanie klucza prywatnego z publicznego, to utrata Twoich środków z konta Ethereum byłaby najmniejszym zmartwieniem w świecie. ",
"HELP_21_Desc_4": "Idąc dalej, TAK jeżeli ktoś miałby Twój klucz prywatny mógłby z łatwością wypłacić środki z Twojego konta. Tak samo, jak by ktoś miał hasło do Twojego konta pocztowego, mógłby czytać Twoje maile, lub gdyby miał hasło bankowe, mógłby wypłacać z niego pieniądze. Możesz ściągnąć plik Keystore Twojego portfela, który jest kluczem prywatnym zaszyfrowanym hasłem. To jest tak jak by mieć hasło, które jest chronione innym hasłem. ",
"HELP_21_Desc_5": "Więc TAK, teoretycznie można by po prostu wpisywać 64 znaki w kodzie szesnastkowym do momentu trafienia na taki, który nie jest pusty. Co więcej zdolni ludzie mogą napisać program, który będzie bardzo szybko, automatycznie sprawdzał kolejne losowe kombinacje kluczy. Taka metoda nazywa się \"brute-forcing\" lub \"mining\". Różni ludzie zastanawiali się nad jej zastosowaniem długo i intensywnie. Z pomocą kilku wysokiej klasy serwerów mogliby być w stanie sprawdzać ponad 1 milion kluczy na sekundę. Jednak nawet wtedy koszt utrzymania pracy tych serwerów byłby wiele razy wyższy niż potencjalne zyski ze znalezienia jakichkolwiek środków. Bardziej prawdopodobne byłoby, że pierwsze trafienie nastąpi dopiero po śmierci Twojej i Twoich prawnuków. ",
"HELP_21_Desc_6": "Jeśli wiesz coś na temat Bitcoina, [to może dać Ci perspektywę:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Aby zilustrować jak mało prawdopodobne to jest: załóżmy, że każdy satoshi (najmniejsza część Bitcoina, 0.00000001 BTC), każdego Bitcoina jaki kiedykolwiek będzie istnieć (21 milionów), został wysłany na swój własny unikalny klucz prywatny. Prawdopodobieństwo, że spośród wszystkich tych kluczy 2 odpowiadałyby tym samym adresom jest jak 1 do 100 kwintylionów. ",
"HELP_21_Desc_7": "[Jeżeli byś chciał coś bardziej technicznego:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Te liczby nie mają nic wspólnego z technologią na jakiej opiera się urządzenie. Są maksimami na jakie pozwala termodynamika, co silnie sugeruje, że skuteczne ataki brute-force przeciwko 256-bitowym kluczom będą nieosiągalne, dopóki komputery nie będą zbudowane z czegoś innego niż materia i będą zajmować trochę więcej niż wszechświat. ",
"HELP_21_Desc_6": "Jeśli wiesz coś na temat Bitcoina, [to może dać Ci perspektywę:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Aby zilustrować jak mało prawdopodobne to jest: załóżmy, że każdy satoshi (najmniejsza część Bitcoina, 0.00000001 BTC), każdego Bitcoina jaki kiedykolwiek będzie istnieć (21 milionów), został wysłany na swój własny unikalny klucz prywatny. Prawdopodobieństwo, że spośród wszystkich tych kluczy 2 odpowiadałyby tym samym adresom jest jak 1 do 100 kwintylionów. ",
"HELP_21_Desc_7": "[Jeżeli byś chciał coś bardziej technicznego:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Te liczby nie mają nic wspólnego z technologią na jakiej opiera się urządzenie. Są maksimami na jakie pozwala termodynamika, co silnie sugeruje, że skuteczne ataki brute-force przeciwko 256-bitowym kluczom będą nieosiągalne, dopóki komputery nie będą zbudowane z czegoś innego niż materia i będą zajmować trochę więcej niż wszechświat. ",
"HELP_21_Desc_8": "Oczywiście to wszystko ma miejsce przy założeniu, że klucze są generowane w prawdziwie losowy sposób i z wystarczającą entropią. Klucze tu wygenerowane spełniają te kryteria, tak samo jak klucze w Jaxx i Mist/geth. Portfele Ethereum są w większości całkiem niezłe. Z drugiej strony np. klucze wygenerowane przez ludzki umysł nie spełniają tych kryteriów, jako że ludzki umysł nie jest w stanie wygenerować prawdziwie losowego źródła. W otoczeniu Bitcoina w przeszłości pojawiło się kilka problemów związanych z brakiem odpowiedniej entropii lub brakiem pełnej losowości, ale to całkiem inny temat, być może na inny dzień. ",
"HELP_SecCX_Title": "Bezpieczeństwo - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Gdzie są zapisywane informacje przechowywane przez to rozszerzenie? ",
"HELP_SecCX_Desc_2": "Informacje przechowywane przez to Rozszerzenie Chrome jest zapisywane przez [chrome.storage](http://chrome.storage/). - w tym samym miejscu są przechowywane hasła zapisywane w przeglądarce Chrome. ",
"HELP_SecCX_Desc_2": "Informacje przechowywane przez to Rozszerzenie Chrome jest zapisywane przez [chrome.storage](https://chrome.storage/). - w tym samym miejscu są przechowywane hasła zapisywane w przeglądarce Chrome. ",
"HELP_SecCX_Desc_3": "Jakie informacje są zapisywane? ",
"HELP_SecCX_Desc_4": "Adres, nazwa konta, klucz prywatny są przechowywane w chrome.storage. Klucz prywatny jest zaszyfrowany hasłem jakie podano przy zakładaniu portfela. Nazwa i adres nie są szyfrowane. ",
"HELP_SecCX_Desc_5": "Dlaczego adres i nazwa konta nie są szyfrowane? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -227,7 +227,7 @@
"MYWAL_Content_1": "Cuidado! Você está prestes a remover sua carteira ",
"MYWAL_Content_2": "Certifique-se de que **salvou a chave privada e / ou o Arquivo do Keystore e a senha** antes de removê-la. ",
"MYWAL_Content_3": "Se pretender utilizar esta carteira com o MyEtherWallet CX no futuro, terá de voltar a adicioná-la manualmente utilizando a chave privada/JSON e a palavra-passe. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -228,7 +228,7 @@
"MYWAL_Content_1": "Внимание! Вы собираетесь удалить кошелёк ",
"MYWAL_Content_2": "Убедитесь, что Вы **сохранили закрытый ключ или файл Keystore / JSON и пароль** от этого кошелька, прежде чем Вы удалите этот кошелёк. ",
"MYWAL_Content_3": "Если Вы планируете в будущем использовать этот кошелёк в MyEtherWallet CX, Вам надо будет вручную заново добавить его, указав закрытый ключ или файл JSON и пароль. ",
"VIEWWALLET_Subtitle": "Позволяет скачать закрытые ключи в различных форматах, а также повторно напечатать Ваши бумажные кошельки. Вам это понадобится, когда Вы захотите [импортировать Ваши счета в geth или Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Для проверки баланса Ваших счетов мы рекомендуем использовать браузер блокчейна, например [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Позволяет скачать закрытые ключи в различных форматах, а также повторно напечатать Ваши бумажные кошельки. Вам это понадобится, когда Вы захотите [импортировать Ваши счета в geth или Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Для проверки баланса Ваших счетов мы рекомендуем использовать браузер блокчейна, например [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Позволяет Вам скачать Ваши закрытые ключи в различных форматах, а также повторно напечатать Ваши бумажные кошельки. ",
"VIEWWALLET_SuccessMsg": "Поздравляем! Вот информация о Вашем кошельке. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -227,7 +227,7 @@
"MYWAL_Content_1": "Warning! You are about to remove your wallet ",
"MYWAL_Content_2": "Be sure you have **saved the private key and/or Keystore File and the password** before you remove it. ",
"MYWAL_Content_3": "If you want to use this wallet with your MyEtherWallet CX in the future, you will need to manually re-add it using the private key/JSON and password. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -292,7 +292,7 @@
"MYWAL_Content_1": "Warning! You are about to remove your wallet ",
"MYWAL_Content_2": "Be sure you have **saved the private key and/or Keystore File and the password** before you remove it. ",
"MYWAL_Content_3": "If you want to use this wallet with your MyEtherWallet CX in the future, you will need to manually re-add it using the private key/JSON and password. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -237,7 +237,7 @@
"MYWAL_Content_1": "Varning! Du är på väg att ta bort din plånbok ",
"MYWAL_Content_2": "Kontrollera att du har **sparat den privata nyckeln / Keystore filen och lösenordet** som tillhör den här plånboken innan du tar bort den. ",
"MYWAL_Content_3": "Om du vill använda plånboken med MyEtherWallet CX i framtiden, måste du manuellt lägga till den med hjälp av den privata nyckeln / JSON filen och lösenordet. ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -522,7 +522,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": " This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -536,12 +536,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -651,3 +651,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -292,7 +292,7 @@
"ADD_DigitalBitbox_0a": "Re-open MyEtherWallet on a secure (SSL) connection ",
"ADD_DigitalBitbox_0b": "Re-open MyEtherWallet using [Chrome](https://www.google.com/chrome/browser/desktop/) or [Opera](https://www.opera.com/) ",
"ADD_DigitalBitbox_scan": "Connect your Digital Bitbox ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "This allows you to download different versions of private keys and re-print your paper wallet. You may want to do this in order to [import your account into Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). If you want to check your balance, we recommend using a blockchain explorer like [etherscan.io](https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "This allows you to download different versions of private keys and re-print your paper wallet. ",
"VIEWWALLET_SuccessMsg": "Success! Here are your wallet details. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your account and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your account and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -287,7 +287,7 @@
"MYWAL_Content_1": "Cảnh Báo! Bạn Muốn gỡ bỏ Ví của bạn ",
"MYWAL_Content_2": "Hãy chắc chắn bạn đã **Lưu giữ Private Key hoặc Tập Tin chứa định dạng Keystore và mật khẩu** Trước khi bạn gỡ bỏ nó. ",
"MYWAL_Content_3": "Nếu bạn muốn sử dụng địa chỉ Ví này với MyEtherWallet CX trong tương lai, bạn sẽ cần phải tự thêm vào lại bằng cách sử dụng tập tin Private Key / JSON và mật khẩu. ",
"VIEWWALLET_Subtitle": "Việc này cho phép bạn tải về các phiên bản khác nhau của Private Key và in lại ví giấy của bạn. Bạn có thể muốn làm điều này để [nhập tài khoản của bạn vào Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Nếu bạn muốn kiễm tra số dư của bạn, chúng tôi khuyên bạn sử dụng một blockchain explorer như [etherscan.io] (http://etherscan.io/). ",
"VIEWWALLET_Subtitle": "Việc này cho phép bạn tải về các phiên bản khác nhau của Private Key và in lại ví giấy của bạn. Bạn có thể muốn làm điều này để [nhập tài khoản của bạn vào Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/). Nếu bạn muốn kiễm tra số dư của bạn, chúng tôi khuyên bạn sử dụng một blockchain explorer như [etherscan.io] (https://etherscan.io/). ",
"VIEWWALLET_Subtitle_Short": "Việc này cho phép bạn tải về các phiên bản khác nhau của Private Key và in lại ví giấy của bạn. ",
"VIEWWALLET_SuccessMsg": "Đã Thành Công! Đây là thông tin chi tiết về Ví của bạn. ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Vì sao tài khoản của tôi vừa tạo lại không tồn tại trên Blockchain Explorer? (bao gồm: etherchain, etherscan) ",
"HELP_15_Desc_1": "Tài khoản của bạn chỉ tồn tại duy nhất trên một Blockchain Explorer và tài khoản được kích hoạt khi bởi chính nó khi bạn dùng tài khoản đó và chuyển Ether vào tức khắc tài khoản sử dụng sẽ hiển thị trên hệ thống Blockchain Explorer thích hợp. ",
"HELP_16_Title": "16) Làm thế nào dễ kiễm tra số dư hiện tại của tài khoản? ",
"HELP_16_Desc_1": "Bạn có thể sử dụng Blockchain Explorer dễ kiễm tra, Ví dụ: [etherscan.io](http://etherscan.io/). Dán địa chỉ của bạn vào khung tìm kiếm và nó sẽ hiển thị tài khoản của bạn và toạn bộ lịch sữ giao dịch đã thực hiện đối với địa chỉ này. Ví Dụ: Đây là địa chỉ của chúng tôi [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) được trông thấy trên etherscan.io ",
"HELP_16_Desc_1": "Bạn có thể sử dụng Blockchain Explorer dễ kiễm tra, Ví dụ: [etherscan.io](https://etherscan.io/). Dán địa chỉ của bạn vào khung tìm kiếm và nó sẽ hiển thị tài khoản của bạn và toạn bộ lịch sữ giao dịch đã thực hiện đối với địa chỉ này. Ví Dụ: Đây là địa chỉ của chúng tôi [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) được trông thấy trên etherscan.io ",
"HELP_17_Title": "17) Tại sao số dư tài khoản của tôi không hiển thị khi tôi truy cập vào tài khoản? ",
"HELP_17_Desc_1": "Vấn đề này rất có thể xảy ra nếu như máy tính của bạn đang kích hoạt tường lửa. Các API mà chúng tôi sử dụng nhằm tải xuống số Dư của hiện có của tài khoản và chuyển đổi số dư thường bị chặn bởi tường lửa bởi bất kì lý do nào. Nhưng bạn vẫn có thể gửi đi các giao dịch và bạn chỉ cần sử dụng một phương pháp khác dễ kiễm tra số dư của bạn hiện tại trước và sau khi giao dịch được thực hiện, ví dụ: etherscan.io ",
"HELP_18_Title": "18) Tập tin chứa định dạng Geth của ví tôi nằm ở đâu? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "Tại đây bạn đang sở hữu private key và public key. private key có thể dùng thay thế cho public key, nhưng public key không thể dùng nhằm thay thế và dùng dễ phục hồi lại private key. Thực tế trên internet và các dữ liệu cần được bảo mật của thế giới đang sử dụng loại mật mã học này, có nghĩa nếu một cách nào đó nhằm dùng public key dễ phục hồi lại private key, Thì lượng Ether mà bạn bị đánh cắp nó không phải là vấn đề lớn so với nhiều vấn đề mang tính quan trọng rất lớn của những tổ chức tài chính và chính phủ trên toàn cầu. ",
"HELP_21_Desc_4": "Hiện tại chỉ khẳng định rằng nếu ai đó sở hữu được Private key của bạn thì thực sự họ mới có khả năng chuyển số Ether trong tài khoản của bạn đi được. Giống như nếu ai đó có được mật khẩu email của bạn, họ có thể đọc và gửi email, hoặc mật khẩu tài khoản ngân hàng của bạn, họ mới có thể đánh cắp tiền của bạn đi được. Bạn có thể tải về định dạng Keystore bởi vì nó là định dạng đã mã hoá dữ liệu từ Private key của bạn cùng với mật khẩu giải mã khác. Trường hợp này giống như hiện tại bạn đang có một mật khẩu A nhưng được bảo vệ bởi một mật khẩu B khác và nó giúp tài khoản của bạn càng khó bị đánh mất hơn. ",
"HELP_21_Desc_5": "Vẫn có thẻ xảy ra, theo lý thuyết thì bạn sẽ sử dụng một chuỗi gồn 64 ký tự cho đến khi bạn nhận được một kết quả đúng. Thực tế, một cá nhân thông minh có thể lập trình lên một chương trình rà kết quả đúng với Private key của bạn một cách nhanh chóng. Trường hợp này giống như \"brute-forcing\" hoặc \"mining\" private keys. Nhưng viêc làm này vẫn mất rất nhièu thời gian và rất khó. Cùng với một hệ thống Server công nghệ cao, họ có khả năng dò ngẫu nhiên 1 triệu ký tự / giây. Tuy nhiên, Việc kiễm tra ngẩu nghiên này nhằm mang lại quyền đột nhập vào tài khoản của bạn sẽ phải mất một lượng chi phí rất cao đễ duy trì hệ thống Server của họ - và dễ rà soát cho đến khi hoàn toàn chính xác được Private key của bạn thì có lẽ cá nhân đó đã già vì phải mất cả gần trăm năm dễ cho ra kết quả chính xác. ",
"HELP_21_Desc_6": "Nếu bạn hiểu toàn bộ về Bitcoin, [Điều này có thể xem qua tại:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Nhằm làm rõ cho việc: Cho rằng mỗi satoshi của mỗi bitcoin từng được tạo ra đã gửi đến nó những private key được nó sở hữu mà không có trường hợp khác thay thế. Xác xuất dễ có một mã khoá bị trùng lặp tại hai địa chỉ khác nhau là một trong 100 quintillion, bởi vậy được coi là hoàn toàn không thể. ",
"HELP_21_Desc_7": "[Nếu bạn cần một phương pháp bảo mật cao hơn có thể tham khảo:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Đối với đoạn mã của Private thì hầu như những công nghệ tiên tiến trên máy tính của bạn chỉ là vô nghĩa, vì khi người nào đó muốn dò ngẫu nhiên nó thì họ không cần thiết phải tấn công vào thiết bị của bạn. Nhưng đối với một mã khoá 265-bit sẽ bất khả thi đối với việc làm trên trừ khi máy tính của họ được xây dựng bởi một cái gì đó khác biệt và cực kì tiên tiến thì mới rà được và cho ra kết quả tốt nhất và trường hợp này sẽ cần rất rất nhiều thời gian và những công nghệ đó có lẽ còn phải mất rất nhiều thời gian trong tương lai dễ nghiên cứu . ",
"HELP_21_Desc_6": "Nếu bạn hiểu toàn bộ về Bitcoin, [Điều này có thể xem qua tại:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *Nhằm làm rõ cho việc: Cho rằng mỗi satoshi của mỗi bitcoin từng được tạo ra đã gửi đến nó những private key được nó sở hữu mà không có trường hợp khác thay thế. Xác xuất dễ có một mã khoá bị trùng lặp tại hai địa chỉ khác nhau là một trong 100 quintillion, bởi vậy được coi là hoàn toàn không thể. ",
"HELP_21_Desc_7": "[Nếu bạn cần một phương pháp bảo mật cao hơn có thể tham khảo:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *Đối với đoạn mã của Private thì hầu như những công nghệ tiên tiến trên máy tính của bạn chỉ là vô nghĩa, vì khi người nào đó muốn dò ngẫu nhiên nó thì họ không cần thiết phải tấn công vào thiết bị của bạn. Nhưng đối với một mã khoá 265-bit sẽ bất khả thi đối với việc làm trên trừ khi máy tính của họ được xây dựng bởi một cái gì đó khác biệt và cực kì tiên tiến thì mới rà được và cho ra kết quả tốt nhất và trường hợp này sẽ cần rất rất nhiều thời gian và những công nghệ đó có lẽ còn phải mất rất nhiều thời gian trong tương lai dễ nghiên cứu . ",
"HELP_21_Desc_8": "Tất cả những giả đinh trên nhằm xác định rõ đoạn mã được tạo ra một cách hoàn toàn ngẫu nhiên. các mã khoá được tạo ra ở đây đáp ứng các tiêu chí, mà có thể tương tích đc với Jaxx và Mist/Geth. Ví Ethereum là tất cả những gì tuyệt vời nhất. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Bảo mật - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Những thông tin dữ liệu được kho tiện ích lưu trữ ở đâu? ",
"HELP_SecCX_Desc_2": "Các thông tin dữ liệu được lưu trữ tại kho tiện ích của trình duyệt Chrome thông qua [chrome.storage](http://chrome.storage/). - Đây cũng là nơi mà mật khẩu của bạn được lưu trữ khi bạn chọn cài đặt lưu lại mật khẩu ở trình duyệt Chrome. ",
"HELP_SecCX_Desc_2": "Các thông tin dữ liệu được lưu trữ tại kho tiện ích của trình duyệt Chrome thông qua [chrome.storage](https://chrome.storage/). - Đây cũng là nơi mà mật khẩu của bạn được lưu trữ khi bạn chọn cài đặt lưu lại mật khẩu ở trình duyệt Chrome. ",
"HELP_SecCX_Desc_3": "Những loại thông tin nào sẽ được lưu trữ? ",
"HELP_SecCX_Desc_4": "Địa chỉ, tên gọi và Private key sẽ được lưu trữ tại chrome.storage. Private key sẽ được mã hoá và sử dụng mật khẩu mà bạn thiết lập trong lúc bạn đang thực hiện thêm Ví nhưng địa chỉ Ví và tên Ví thì không bị mã hoá. ",
"HELP_SecCX_Desc_5": "Vì sao địa chỉ và tên gọi lại không cần thiết mã hoá? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -231,7 +231,7 @@
"MYWAL_Content_1": "警告!你将移除你的钱包: ",
"MYWAL_Content_2": "确保在移除以前你已经保存了私钥和Keystore文件并记住了密码。 ",
"MYWAL_Content_3": "如果你想将来在MyEtherWallet插件中使用该钱包你需要手动添加私钥/JSON文件和密码。 ",
"VIEWWALLET_Subtitle": "这允许你下载不同格式的私钥和重新打印你的纸钱包。为了将[你的账户导入到Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/),你可能需要这个操作。如果你想查看你的余额,我们推荐使用区块浏览器,例如[etherscan.io](http://etherscan.io/)。 ",
"VIEWWALLET_Subtitle": "这允许你下载不同格式的私钥和重新打印你的纸钱包。为了将[你的账户导入到Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/),你可能需要这个操作。如果你想查看你的余额,我们推荐使用区块浏览器,例如[etherscan.io](https://etherscan.io/)。 ",
"VIEWWALLET_Subtitle_Short": "这允许你下载不同格式的私钥和重新打印你的纸钱包。 ",
"VIEWWALLET_SuccessMsg": "成功!这是你的钱包细节! ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -532,7 +532,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": "This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -546,12 +546,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",
@ -661,3 +661,4 @@
"ONBOARD_resume": "It looks like you didn't finish reading through these slides last time. ProTip: Finish reading through the slides 😉"
}
}

View File

@ -282,7 +282,7 @@
"MSG_info1": "填入當前時間來避免簽名在其他不同時間被重複利用。 ",
"MSG_info2": "填入你的暱稱及你使用該暱稱的場合來避免其他人使用",
"MSG_info3": "填入這個訊息的源由來避免被用在其他目的。 ",
"VIEWWALLET_Subtitle": "這可以讓你下載不同版本的私鑰並且重新印製出你的紙錢包。你可能會需要這個功能來將你的帳戶[讀入Geth/Mist](http://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)。 如果你想要檢查你的帳號餘額,我們建議你使用區塊鏈瀏覽網頁像是[etherscan.io](http://etherscan.io/)。 ",
"VIEWWALLET_Subtitle": "這可以讓你下載不同版本的私鑰並且重新印製出你的紙錢包。你可能會需要這個功能來將你的帳戶[讀入Geth/Mist](https://ethereum.stackexchange.com/questions/465/how-to-import-a-plain-private-key-into-geth/)。 如果你想要檢查你的帳號餘額,我們建議你使用區塊鏈瀏覽網頁像是[etherscan.io](https://etherscan.io/)。 ",
"VIEWWALLET_Subtitle_Short": "這可以讓你下載不同版本的私鑰並且重新印製出你的紙錢包。 ",
"VIEWWALLET_SuccessMsg": "成功!這些是你的錢包內容。 ",
"VIEWWALLET_ShowPrivKey": "(show)",
@ -522,7 +522,7 @@
"HELP_15_Title": "15) Why hasn't the account I just created show up in the blockchain explorer? (ie: etherchain, etherscan) ",
"HELP_15_Desc_1": "Accounts will only show up in a blockchain explorer once the account has activity on it&mdash;for example, once you have transferred some Ether to it. ",
"HELP_16_Title": "16) How do I check the balance of my account? ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](http://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](http://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_16_Desc_1": "You can use a blockchain explorer like [etherscan.io](https://etherscan.io/). Paste your address into the search bar and it will pull up your address and transaction history. For example, here's what our [donation account](https://etherscan.io/address/0x7cb57b5a97eabe94205c07890be4c1ad31e486a8) looks like on etherscan.io ",
"HELP_17_Title": "17) Why isn't my balance showing up when I unlock my wallet? ",
"HELP_17_Desc_1": " This is most likely due to the fact that you are behind a firewall. The API that we use to get the balance and convert said balance is often blocked by firewalls for whatever reason. You will still be able to send transactions, you just need to use a different method to see said balance, like etherscan.io ",
"HELP_18_Title": "18) Where is my geth wallet file? ",
@ -536,12 +536,12 @@
"HELP_21_Desc_3": "In this you have a private key and a public key. The private key can derive the public key, but the public key cannot be turned back into the private key. The fact that the internet and the worlds secrets are using this cryptography means that if there is a way to go from public key to private key, your lost ether is the least of everyones problems. ",
"HELP_21_Desc_4": "Now, that said, YES if someone else has your private key then they can indeed send ether from your account. Just like if someone has your password to your email, they can read and send your email, or the password to your bank account, they could make transfers. You could download the Keystore version of your private key which is the private key that is encrypted with a password. This is like having a password that is also protected by another password. ",
"HELP_21_Desc_5": "And YES, in theory you could just type in a string of 64 hexadecimal characters until you got one that matched. In fact, smart people could write a program to very quickly check random private keys. This is known as \"brute-forcing\" or \"mining\" private keys. People have thought about this long and hard. With a few very high end servers, they may be able to check 1M+ keys / second. However, even checking that many per second would not yield access to make the cost of running those servers even close to worthwhile - it is more likely you, and your great-grandchildren, will die before getting a match. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](http://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](http://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_6": "If you know anything about Bitcoin, [this will put it in perspective:](https://bitcoin.stackexchange.com/questions/32331/two-people-with-same-public-address-how-will-people-network-know-how-to-deliver) *To illustrate how unlikely this is: suppose every satoshi of every bitcoin ever to be generated was sent to its own unique private keys. The probability that among those keys there could be two that would correspond to the same address is roughly one in 100 quintillion. ",
"HELP_21_Desc_7": "[If you want something a bit more technical:](https://security.stackexchange.com/questions/25375/why-not-use-larger-cipher-keys/25392#25392) *These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. ",
"HELP_21_Desc_8": "Of course, this all assumes that keys are generated in a truly random way & with sufficient entropy. The keys generated here meet that criteria, as do Jaxx and Mist/geth. The Ethereum wallets are all pretty good. Keys generated by brainwallets do not, as a person's brain is not capable of creating a truly random seed. There have been a number of other issues regarding lack of entropy or seeds not being generated in a truly random way in Bitcoin-land, but that's a separate issue that can wait for another day. ",
"HELP_SecCX_Title": "Security - MyEtherWallet CX ",
"HELP_SecCX_Desc_1": "Where is this extension saving my information? ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](http://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_2": "The information you store in this Chrome Extension is saved via [chrome.storage](https://chrome.storage/). - this is the same place your passwords are saved when you save your password in Chrome. ",
"HELP_SecCX_Desc_3": "What information is saved? ",
"HELP_SecCX_Desc_4": "The address, nickname, private key is stored in chrome.storage. The private key is encrypted using the password you set when you added the wallet. The nickname and wallet address is not encrypted. ",
"HELP_SecCX_Desc_5": "Why aren't the nickname and wallet address encrypted? ",

View File

@ -1,95 +0,0 @@
"use strict";
var __extends = (this && this.__extends) || (function () {
var extendStatics = Object.setPrototypeOf ||
({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||
function (d, b) { for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p]; };
return function (d, b) {
extendStatics(d, b);
function __() { this.constructor = d; }
d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
})();
exports.__esModule = true;
var ts = require("typescript");
var Lint = require("tslint");
var ErrorTolerantWalker_1 = require("../node_modules/tslint-microsoft-contrib/utils/ErrorTolerantWalker");
var JsxAttribute_1 = require("../node_modules/tslint-microsoft-contrib/utils/JsxAttribute");
var FAILURE_STRING = 'Anchor tags with an external link must use https';
/**
* Implementation of the no-external-http-link rule.
*/
var Rule = /** @class */ (function (_super) {
__extends(Rule, _super);
function Rule() {
return _super !== null && _super.apply(this, arguments) || this;
}
Rule.prototype.apply = function (sourceFile) {
if (sourceFile.languageVariant === ts.LanguageVariant.JSX) {
return this.applyWithWalker(new NoExternalHttpLinkRuleWalker(sourceFile, this.getOptions()));
}
else {
return [];
}
};
Rule.metadata = {
ruleName: 'tno-external-http-link',
type: 'functionality',
description: 'Anchor tags with an external link must use https',
options: null,
optionsDescription: '',
typescriptOnly: true,
issueClass: 'SDL',
issueType: 'Error',
severity: 'Critical',
level: 'Mandatory',
group: 'Security',
commonWeaknessEnumeration: '242,676'
};
return Rule;
}(Lint.Rules.AbstractRule));
exports.Rule = Rule;
var NoExternalHttpLinkRuleWalker = /** @class */ (function (_super) {
__extends(NoExternalHttpLinkRuleWalker, _super);
function NoExternalHttpLinkRuleWalker() {
return _super !== null && _super.apply(this, arguments) || this;
}
NoExternalHttpLinkRuleWalker.prototype.visitJsxElement = function (node) {
var openingElement = node.openingElement;
this.validateOpeningElement(openingElement);
_super.prototype.visitJsxElement.call(this, node);
};
NoExternalHttpLinkRuleWalker.prototype.visitJsxSelfClosingElement = function (node) {
this.validateOpeningElement(node);
_super.prototype.visitJsxSelfClosingElement.call(this, node);
};
NoExternalHttpLinkRuleWalker.prototype.validateOpeningElement = function (openingElement) {
if (openingElement.tagName.getText() === 'a') {
var allAttributes = JsxAttribute_1.getJsxAttributesFromJsxElement(openingElement);
var href = allAttributes.href;
if (href !== null && !isSafeHrefAttributeValue(href) && JsxAttribute_1.getStringLiteral(href) !== 'undefined') {
this.addFailureAt(openingElement.getStart(), openingElement.getWidth(), FAILURE_STRING);
}
}
};
return NoExternalHttpLinkRuleWalker;
}(ErrorTolerantWalker_1.ErrorTolerantWalker));
function isSafeHrefAttributeValue(attribute) {
if (JsxAttribute_1.isEmpty(attribute)) {
return false;
}
if (attribute.initializer.kind === ts.SyntaxKind.JsxExpression) {
var expression = attribute.initializer;
if (expression.expression !== null &&
expression.expression.kind !== ts.SyntaxKind.StringLiteral) {
return true; // attribute value is not a string literal, so do not validate
}
}
var stringValue = JsxAttribute_1.getStringLiteral(attribute);
if (stringValue === '#') {
return true;
}
else if (stringValue === null || stringValue.length === 0) {
return false;
}
return stringValue.indexOf('https://') >= 0;
}

View File

@ -1,96 +0,0 @@
import * as ts from 'typescript';
import * as Lint from 'tslint';
import { ErrorTolerantWalker } from '../node_modules/tslint-microsoft-contrib/utils/ErrorTolerantWalker';
import { ExtendedMetadata } from '../node_modules/tslint-microsoft-contrib/utils/ExtendedMetadata';
import { Utils } from '../node_modules/tslint-microsoft-contrib/utils/Utils';
import {
getJsxAttributesFromJsxElement,
getStringLiteral,
isEmpty
} from '../node_modules/tslint-microsoft-contrib/utils/JsxAttribute';
const FAILURE_STRING = 'Anchor tags with an external link must use https';
/**
* Implementation of the no-external-http-link rule.
*/
export class Rule extends Lint.Rules.AbstractRule {
public static metadata: ExtendedMetadata = {
ruleName: 'tno-external-http-link',
type: 'functionality',
description: 'Anchor tags with an external link must use https',
options: null,
optionsDescription: '',
typescriptOnly: true,
issueClass: 'SDL',
issueType: 'Error',
severity: 'Critical',
level: 'Mandatory',
group: 'Security',
commonWeaknessEnumeration: '242,676'
};
public apply(sourceFile: ts.SourceFile): Lint.RuleFailure[] {
if (sourceFile.languageVariant === ts.LanguageVariant.JSX) {
return this.applyWithWalker(new NoExternalHttpLinkRuleWalker(sourceFile, this.getOptions()));
} else {
return [];
}
}
}
class NoExternalHttpLinkRuleWalker extends ErrorTolerantWalker {
protected visitJsxElement(node: ts.JsxElement): void {
const openingElement: ts.JsxOpeningElement = node.openingElement;
this.validateOpeningElement(openingElement);
super.visitJsxElement(node);
}
protected visitJsxSelfClosingElement(node: ts.JsxSelfClosingElement): void {
this.validateOpeningElement(node);
super.visitJsxSelfClosingElement(node);
}
private validateOpeningElement(openingElement: ts.JsxOpeningLikeElement): void {
if (openingElement.tagName.getText() === 'a') {
const allAttributes: { [propName: string]: ts.JsxAttribute } = getJsxAttributesFromJsxElement(
openingElement
);
const href: ts.JsxAttribute = allAttributes.href;
if (
href !== null &&
!isSafeHrefAttributeValue(href) &&
getStringLiteral(href) !== 'undefined'
) {
this.addFailureAt(openingElement.getStart(), openingElement.getWidth(), FAILURE_STRING);
}
}
}
}
function isSafeHrefAttributeValue(attribute: ts.JsxAttribute): boolean {
if (isEmpty(attribute)) {
return false;
}
if (attribute.initializer.kind === ts.SyntaxKind.JsxExpression) {
const expression: ts.JsxExpression = <ts.JsxExpression>attribute.initializer;
if (
expression.expression !== null &&
expression.expression.kind !== ts.SyntaxKind.StringLiteral
) {
return true; // attribute value is not a string literal, so do not validate
}
}
const stringValue = getStringLiteral(attribute);
if (stringValue === '#') {
return true;
} else if (stringValue === null || stringValue.length === 0) {
return false;
}
return stringValue.indexOf('https://') >= 0;
}

View File

@ -5,7 +5,7 @@ import { makeCustomNodeId, makeNodeConfigFromCustomConfig } from 'utils/node';
const custNode = {
name: 'Test Config',
url: 'http://somecustomconfig.org/',
url: 'https://somecustomconfig.org/',
port: 443,
network: 'ETH'
};

View File

@ -7,11 +7,11 @@ import {
const custNode = {
name: 'Test Config',
url: 'http://somecustomconfig.org/',
url: 'https://somecustomconfig.org/',
port: 443,
network: 'ETH'
};
const custNodeId = 'http://somecustomconfig.org/:443';
const custNodeId = 'https://somecustomconfig.org/:443';
describe('makeCustomNodeId', () => {
it('should construct an ID from url:port', () => {

View File

@ -25,8 +25,8 @@
"comment-format": false,
"ordered-imports": false,
"react-anchor-blank-noopener": true,
"no-external-http-link": true,
"no-http-string": [true, "http://localhost:.*"],
"react-no-dangerous-html": true
},
"rulesDirectory": ["node_modules/tslint-microsoft-contrib", "custom_linting_rules"]
"rulesDirectory": ["node_modules/tslint-microsoft-contrib"]
}