1 2016-12-01 14:36:21 <nazarewk> how do i generate blocks on testnet?
 2 2016-12-01 14:50:54 <jonasschnelli> nazarewk: better use regtest.
 3 2016-12-01 15:09:48 <venzen> nazarewk: there is also miners being tested on testnet so the difficulty can be high sometimes :)
 4 2016-12-01 15:10:04 <venzen> regtest, just use your CPU
 5 2016-12-01 15:11:21 <venzen> jonasschnelli: writing unit tests at the moment with same test vectors used in your test.c file
 6 2016-12-01 15:12:00 <jonasschnelli> venzen: yes. Reminds me of missing test vectors...
 7 2016-12-01 15:12:32 <venzen> i'm using: https://tools.ietf.org/html/draft-agl-tls-chacha20poly1305-04#section-7
 8 2016-12-01 15:15:19 <jonasschnelli> venzen: Yes. I think you can use those... but the @openssh AEAD is slightly different
 9 2016-12-01 15:21:09 <venzen> jonasschnelli: my unit tests for chacha20 and poly1305 succeed with those vectors
10 2016-12-01 15:21:51 <jonasschnelli> Yes. But what we need are also tests for the ChaCha20Poly1305@openssh AEAD (64byte key material direct test).
11 2016-12-01 15:22:13 <jonasschnelli> But testing chacha20 and poly1305 independently is more important I guess
12 2016-12-01 15:22:19 <venzen> jonasschnelli: but the AEAD unit tests fail with the above vectors (there is only one set) - i suspect I am applying them wrong. I'll deal with that after i complete the test module
13 2016-12-01 15:23:13 <venzen> jonasschnelli: ok, i see you just commented about that, yes the ietf vectors are for 32 bit keys
14 2016-12-01 15:23:53 <venzen> correction: they use 32 byte keys for testing AEAD
15 2016-12-01 15:24:20 <jonasschnelli> the IEFT ChaCha20Poly1305 AEAD is different from the openssh one
16 2016-12-01 15:24:29 <jonasschnelli> The openssh one uses two keys
17 2016-12-01 15:25:36 <venzen> ok, do you have a link for those vectors or should i just copy them from test.c
18 2016-12-01 15:35:12 <jonasschnelli> venzen: I think there are no vectors for the @openssh AEAD
19 2016-12-01 15:35:17 <jonasschnelli> Maybe check openssh's sources