micro-ecc | ECDH and ECDSA for 8-bit , 32-bit , and 64-bit processors

by kmackay C++ Version: v1.1 License: BSD-2-Clause

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | micro-ecc Summary

micro-ecc is a C++ library typically used in Hardware applications. micro-ecc has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

A small and fast ECDH and ECDSA implementation for 8-bit, 32-bit, and 64-bit processors. The static version of micro-ecc (ie, where the curve was selected at compile-time) can be found in the "static" branch.

Support

Quality

Security

License

Reuse

Support

micro-ecc has a medium active ecosystem.

It has 954 star(s) with 364 fork(s). There are 81 watchers for this library.

It had no major release in the last 12 months.

There are 18 open issues and 131 have been closed. On average issues are closed in 630 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of micro-ecc is v1.1

Quality

micro-ecc has no bugs reported.

Security

micro-ecc has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

micro-ecc is licensed under the BSD-2-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

micro-ecc releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of micro-ecc

Get all kandi verified functions for this library.

micro-ecc Key Features

No Key Features are available at this moment for micro-ecc.

micro-ecc Examples and Code Snippets

No Code Snippets are available at this moment for micro-ecc.

Community Discussions

Trending Discussions on micro-ecc

Linker: Moving all functions but two to a specific memory region

ECDSA Signing and Verifying issue between python ECDSA and C micro-ecc library

preprocessing for TaskScheduler-Library doesn't work - multiple definition Error

QUESTION

Linker: Moving all functions but two to a specific memory region

Asked 2020-Feb-20 at 11:35

I am working on firmware for a PIC32MX microcontroller. The program memory should be split into three segments:

Section 1: interrupt service routine and main function (startup_region)
Section 2: 50% of remaining program memory (program1)
Section 3: 50% of remaining program memory (program2)

The firmware is only stored in either Section 2 or 3. The other is reserved for future updates. As such the active region can safely override the other to store the update. A config bit is flipped and the main() function of Section 0 now jumps to the other program on reboot.

As such I need the linker to put all functions except isr and main into Section 1 and everything else into Section 2. Section 3 must be left completely empty, as it may be overridden in the future.

I already tried to achieve this by modifying the default linker script, however I had no success.

linkerscript.ld:

...

ANSWER

Answered 2020-Feb-20 at 11:35

The object file main.o is not the same as the function’s memory segment .tex.main. If this object file produces some other text segments they will be placed elsewhere. This is what you see in your map file.

As @Ctx mentioned the syntax of your text segment is wrong instead of *(*.text) it should be

Source https://stackoverflow.com/questions/60309570

QUESTION

ECDSA Signing and Verifying issue between python ECDSA and C micro-ecc library

Asked 2019-May-15 at 22:08

I am facing an issue when I do the following :

Created a Public Private key pair using python for ECDSA SECP256k1 curve and printed it on the terminal.
Copy pasted the key pair in Python script and in visual studio (C coding that uses micro-ecc library). So that new key is not generated everytime I run the code.
Sign a message ("Hello") in Python using the private key and print both the signature and message on the terminal. I know that the message has to be hashed first using a standard hashing algorithm such as SHA256, but in this case I am using the message directly for signing.
Copy the signature and the same message (hash) into Visual studio.
When I call the verify API in visual studio the verification fails all though it makes use of the same public key, message, signature and the curve.

Libraries I am using:

micro-ecc for C in visual studio https://github.com/kmackay/micro-ecc
ECDSA for python https://github.com/warner/python-ecdsa

Other things I have tested and ensured:

Signing and verifying both in python works fine for a same key pair say (sk,vk).
Signing and verifying both in visual studio works fine for a same key pair say (sk,vk).
Signing using microECC in Visual Studio and verifying using ECDSA in python fails, also signing using ECDSA and verifying using microECC in fails.
I am sure about the key Copy pasted from terminal is actually the intended key, because I have cross verified the verifying key from the copied signing Key and it is matching.

First I generate the keys by running this script

GenerateKeys.py

...

ANSWER

Answered 2019-May-15 at 22:08

The ECDSA signing procedure is a two-stage process:

a hash digest is calculated from the message
this digest is then signed.

Python ECDSA uses SHA-1 by default unless otherwise stated.

The SHA-1 digest for the message 'Hello' is hex encoded: f7ff9e8b7bb2e09b70935a5d785e0cc5d9d0abf0.

This means you need to use this digest when calling the uECC_verify function.

Validation

Replace in your .c code the msg array with the following line of code:

Source https://stackoverflow.com/questions/56142232

QUESTION

preprocessing for TaskScheduler-Library doesn't work - multiple definition Error

Asked 2018-May-14 at 14:09

I'm facing problems getting multiple definition errors for an entire Library. As soon as I include the TaskScheduler library in another header-file (except the .ino) I get the error.

For clarification: below is not my actual code that I want to be fixed! I reduced it to the minimum that still has the error(tested in Eclipse sloeber and Arduino IDE) :

Project.ino :

...

ANSWER

Answered 2018-May-11 at 16:26

In C/C++ if you define a function inside 2 separate "translation modules" (i.e. ".cpp" files), you will get this error, because the linker doesn't know which one to use for the final program.

You Project.ino seems to compile as it's own translation module - "sloeber.ino.cpp", so if you have the same function definition included in both WifiHelper.cpp and sloeber.ino.cpp you will get this error.

First make sure that you don't include stuff twice. To be absolutely sure you can add guards around your #include:

Source https://stackoverflow.com/questions/50291528

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install micro-ecc

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: