This has been added to the website, thanks!
-Jason
On Mar 29, 2013, at 6:20 AM, owner-t...@openbsd.org wrote:
> The pre-dawn daily digest
> Volume 1 : Issue 3537 : "index" Format
>
> Messages in this Issue:
> 201303/498: Re: goodbye to some isa devices
> 201303/499: Re: /usr.bin/colldef and
Reyk,
When 'rsa' is specified for ikeauth in iked.conf, parse.y ->
print_policy() reports 'eap ""' where ### is a random
number, observed to be between 1 and 255. If 'rsa' is not specified in
iked.conf, print_policy() correctly reports 'rsa'. This is seen when
running "iked -dv".
This doe
Stu,
I am in the US. While I am no lawyer, I believe the export
resctrictions are on the actual cryptography software, namely OpenSSL,
which is developed in your neck of the woods. As my patch doesn't
provide any actual cryptography, just using existing methods, it should
be ok. But, as I
Reyk,
I've taken the liberty of patching ca.c, crypto.c, ikev2.h, parse.y,
iked.8 and iked.conf.5. I'm no expert on this, but this seems to work
for me. SAs and Flows are established, it hasn't crashed, and I'm
passing data.
Let me know what you think.
Thanks,
-Jason
diff -u sbin/iked.or
