kirk-baird commented on issue #7: HKDF
URL:
https://github.com/apache/incubator-milagro-crypto-rust/issues/7#issuecomment-521496272
I've added these to a [WIP
branch](https://github.com/sigp/incubator-milagro-crypto-rust/tree/bls-standard)
They still need significant testing.
GuillaumeCisco edited a comment on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521329526
What I tried:
Using the file `test_pair_FP256BN.c` which use `CURVE_Order_FP256BN`.
Creating the .so (from python wrapper generated
GuillaumeCisco commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521329526
What I tried:
Using the file `test_pair_FP256BN.c` which use `CURVE_Order_FP256BN`.
Creating the .so (from python wrapper generated
GuillaumeCisco edited a comment on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521321028
Thanks.
I need a little help on this one.
If I create rom.c like:
```c
#include
#include
#include
#include
GuillaumeCisco commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521321028
Thanks.
I need a little help on this one.
If I create rom.c like:
```c
#include
#include
#include
#include
#include
kealan commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521253357
For the constants you may have to write a c function which you wrap with
CFFI. Something like this in C.
#include
#include
#include
GuillaumeCisco commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521249497
Thanks for the precision, using make with a python virtual env set on python
2.7 built the target folder successfully.
I now have files like
GuillaumeCisco edited a comment on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521240128
Quick question, is `bls_ZZZ.py.in` a generated file?
What `.py.in` stands for?
could we generate a `rom_ZZZ.py.in` file?
kealan commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521242102
Try and build the library and you will see what is happening. The
bls_ZZZ.py.in is the template file that gets overwritten. In the rom files
there are
GuillaumeCisco edited a comment on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521240128
Quick question, is `bls_ZZZ.py.in` generated files?
What `.py.in` stands for?
could we generate a `rom_ZZZ.py.in` file?
kealan commented on issue #39: Python test wrappers - python 3?
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/39#issuecomment-521236653
ZZZ is the curve that the library builds with.
This is an automated
kealan commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521236249
Hi My advice would be just to copy the bls example.
This is an automated message from
GuillaumeCisco closed issue #37: Difference with skair39/milagro-crypto-c
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/37
This is an automated message from the Apache Git Service.
To respond to the
GuillaumeCisco commented on issue #37: Difference with skair39/milagro-crypto-c
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/37#issuecomment-521234124
Thanks for the precision
This is an automated message
GuillaumeCisco commented on issue #39: Python test wrappers - python 3?
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/39#issuecomment-521232032
Thanks for the confirmation.
By the way, what's the `_ZZZ` suffix stands for?
I've already inspected it and it worked
GuillaumeCisco commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521231448
Thank you very much @kealan for this confirmation.
Could you help me `begin` in this translation. I'm not familiar with ffi and
need a
kealan commented on issue #37: Difference with skair39/milagro-crypto-c
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/37#issuecomment-521169961
Yes that seems to be an old version of this code.
This is an
kealan commented on issue #38: Python wrappers
URL:
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521169501
Hi There is only Python support for high level functions. It would be
straightforward to extend the wrappers to level code.
GuillaumeCisco opened a new issue #39: Python test wrappers - python 3?
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/39
Are current python tests for python wrappers are compatible with python 3?
It looks like not :/
Can someone confirm me that?
Thanks,
GuillaumeCisco opened a new issue #38: Python wrappers
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/38
Hello there.
I'm trying to implement some idemix support for the fabric hyperledger tool.
Main thread here:
GuillaumeCisco opened a new issue #37: Difference with skair39/milagro-crypto-c
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/37
Hello guys, is there any difference between you work and this one:
https://github.com/skair39/milagro-crypto-c
Looks like yours is the
21 matches
Mail list logo
