Am 08-01-2014 03:06, schrieb Theo de Raadt:
Am 08-01-2014 03:02, schrieb Aleksandar Lazic:
Am 08-01-2014 02:50, schrieb Theo de Raadt:
Autoinstall does not handle this type of problem either.
Is there a plan to be able to handle such a problem with autoinstall?
Yes... get a CF card which
On 8 January 2014 12:02, Martin Pieuchot mpieuc...@nolizard.org wrote:
I find it really difficult to understand and work with the code of
rtsock.c because of the following defines:
/* Sleazy use of local variables throughout file, warning */
#define dst
This may or may not be useful. We can embed the message after the
signature and reduce the number of files in half. It's not a lot of
code. (This is how the crypto_sign API originally worked, but we've
since added some metadata, so we still need to destruct and
reconstruct the crypto_sign inputs
On Wed, Jan 08, 2014 at 03:53:32PM -0500, Ted Unangst wrote:
This may or may not be useful. We can embed the message after the
signature and reduce the number of files in half. It's not a lot of
code. (This is how the crypto_sign API originally worked, but we've
since added some metadata, so
