On Tue, Jul 21, 2009 at 10:46, Dr. Stephen Henson wrote:
> On Tue, Jul 21, 2009, Fred Keet wrote:
>> At this point I've got code that generates the ec keys from the sect163k1
>> curve, and then signs a block of data. When I compare this with the ecsign
>> utility they provide (apparently built on M
On Tue, Jul 21, 2009, Fred Keet wrote:
>
> At this point I've got code that generates the ec keys from the sect163k1
> curve, and then signs a block of data. When I compare this with the ecsign
> utility they provide (apparently built on Miracl) the two signatures do not
> match, so it seems th
Mike Frysinger wrote:
On Mon, Jul 20, 2009 at 09:51, Fred Keet wrote:
I'm in the process of writing an application that signs binary data for
loading
onto a Analog Devices BlackFin microprocessor. These chips have "built in"
support for verification of code. The chip gets loaded with the EC p
On Mon, Jul 20, 2009 at 09:51, Fred Keet wrote:
> I'm in the process of writing an application that signs binary data for
> loading
> onto a Analog Devices BlackFin microprocessor. These chips have "built in"
> support for verification of code. The chip gets loaded with the EC public
> key,
> and t
I'm in the process of writing an application that signs binary data for
loading
onto a Analog Devices BlackFin microprocessor. These chips have "built in"
support for verification of code. The chip gets loaded with the EC
public key,
and then you just update the code and signature on every upda
