user37515: In the browser, I'm using AES-256-CBC with 128bit IV & PBKDF2 to encrypt the mnemonic
"tell file snow green proof evil six squeeze budget various orbit clock" 

with a password 
"s0mesuperl0ng!password@!" 

with 30,000 rounds it's taking roughly 22 seconds. It feels too long, but I don't want to make it insecure. 
Can I safely reduce the rounds to make it a bit faster? and if so what would be the minimum? 
Could I get away with 10,000?

user5273: 
Can I safely reduce the rounds to make it a bit faster? and if so what would be the minimum?
Could I get away with 10,000?

Anyone trying to crack your encrypted data is not going to be limited by the speed of javascript executing in a browser. They'll be running FPGAs or something much faster than that. So 20,000, 10,000 or 0 doesn't make any sort of difference here.
Where I learned this

37515: <p>In the browser, I'm using AES-256-CBC with 128bit IV &amp; PBKDF2 to encrypt the mnemonic</p>

<pre><code>"tell file snow green proof evil six squeeze budget various orbit clock" 
</code></pre>

<p>with a password </p>

<pre><code>"s0mesuperl0ng!password@!" 
</code></pre>

<p>with 30,000 rounds it's taking roughly 22 seconds. It feels too long, but I don't want to make it insecure. </p>

<p>Can I safely reduce the rounds to make it a bit faster? and if so what would be the minimum? </p>

<p>Could I get away with 10,000?</p>
 5273: <blockquote>
<p>Can I safely reduce the rounds to make it a bit faster? and if so what would be the minimum?</p>
<p>Could I get away with 10,000?</p>
</blockquote>
<p>Anyone trying to crack your encrypted data is not going to be limited by the speed of javascript executing in a browser. They'll be running FPGAs or something much faster than that. So 20,000, 10,000 or 0 doesn't make any sort of difference here.</p>
<p><a href="https://bitcointalk.org/index.php?topic=812894.msg10907427#msg10907427" rel="nofollow noreferrer">Where I learned this</a></p>
