mirror of
https://github.com/firefly-iii/firefly-iii.git
synced 2025-02-25 18:45:27 -06:00
New translations firefly.php (Dutch)
This commit is contained in:
parent
244f174dc9
commit
458606381e
@ -416,9 +416,9 @@ return [
|
||||
'password_changed' => 'Je wachtwoord is veranderd!',
|
||||
'should_change' => 'Vul ook echt een ander wachtwoord in.',
|
||||
'invalid_password' => 'Ongeldig wachtwoord!',
|
||||
'what_is_pw_security' => 'What is "verify password security"?',
|
||||
'secure_pw_title' => 'How to choose a secure password',
|
||||
'secure_pw_history' => 'In August 2017 well known security researcher Troy Hunt released a list of 306 million stolen passwords. These passwords were stolen during breakins at companies like LinkedIn, Adobe and NeoPets (and many more).',
|
||||
'what_is_pw_security' => 'Wat is "Bevestig wachtwoordsterkte"?',
|
||||
'secure_pw_title' => 'Hoe kies je een veilig wachtwoord',
|
||||
'secure_pw_history' => 'De bekende security onderzoeker Troy Hunt gaf in augustus 2017 een lijst vrij van 306 miljoen gestolen wachtwoorden. Deze wachtwoorden waren gestolen tijdens hacks van bekende bedrijven zoals LinkedIn, Adobe en NeoPets (en vele anderen).',
|
||||
'secure_pw_check_box' => 'By checking the box, Firefly III will send the SHA1 hash of your password to <a href="https://www.troyhunt.com/introducing-306-million-freely-downloadable-pwned-passwords/">the website of Troy Hunt</a> to see if it is on the list. This will stop you from using unsafe passwords as is recommended in the latest <a href="https://pages.nist.gov/800-63-3/sp800-63b.html">NIST Special Publication</a> on this subject.',
|
||||
'secure_pw_sha1' => 'But I thought SHA1 was broken?',
|
||||
'secure_pw_hash_speed' => 'Yes, but not in this context. As you can read on <a href="https://shattered.io/">the website detailing how they broke SHA1</a>, it is now slightly easier to find a "collision": another string that results in the same SHA1-hash. It now only takes 10,000 years using a single-GPU machine.',
|
||||
|
Loading…
Reference in New Issue
Block a user