[GitHub] [incubator-milagro-crypto-rust] kealan merged pull request #2: Formatting and gitignore

2019-07-03 Thread GitBox
kealan merged pull request #2: Formatting and gitignore
URL: https://github.com/apache/incubator-milagro-crypto-rust/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW commented on issue #22: AES encryption/decryption optimized with Intel AES-NI.

2019-07-16 Thread GitBox
JohnMcW commented on issue #22: AES encryption/decryption optimized with Intel 
AES-NI.
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/22#issuecomment-511836012
 
 
   This issue was https://issues.apache.org/jira/browse/MILAGRO-37 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW opened a new issue #22: AES encryption/decryption optimized with Intel AES-NI.

2019-07-16 Thread GitBox
JohnMcW opened a new issue #22: AES encryption/decryption optimized with Intel 
AES-NI.
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/22
 
 
   We may want to support AES encryption/decryption optimized with Intel AES-NI 
in case of common server platform in case we dont already use an hsm. Algorithm 
proposed:
   1. Detect if the system has AES-NI enabled
   2. In case it has, use the AES-NI primitive
   3. Otherwise switch back to software AES.
   
https://software.intel.com/sites/default/files/article/165683/aes-wp-2012-09-22-v01.pdf


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW commented on issue #4: Docker Container Deployment

2019-07-16 Thread GitBox
JohnMcW commented on issue #4: Docker Container Deployment
URL: 
https://github.com/apache/incubator-milagro-dta/issues/4#issuecomment-511838387
 
 
   This issue was https://issues.apache.org/jira/browse/MILAGRO-33 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW opened a new issue #4: Docker Container Deployment

2019-07-16 Thread GitBox
JohnMcW opened a new issue #4: Docker Container Deployment
URL: https://github.com/apache/incubator-milagro-dta/issues/4
 
 
   As a user, I would like to deploy the Milagro Server in a Docker container.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] JohnMcW commented on issue #6: Web/documentation needs refresh

2019-07-16 Thread GitBox
JohnMcW commented on issue #6: Web/documentation needs refresh
URL: https://github.com/apache/incubator-milagro/issues/6#issuecomment-511830343
 
 
   Was issue https://issues.apache.org/jira/browse/MILAGRO-27 in Apache Jira 
(this issue will be closed presently)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW opened a new issue #2: Config/Install Script

2019-07-16 Thread GitBox
JohnMcW opened a new issue #2: Config/Install Script
URL: https://github.com/apache/incubator-milagro-dta/issues/2
 
 
   As a user, I want to have a configuration/install method that sets up the 
instance of the Milagro Server for my intended use.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW opened a new issue #24: Modern C++17 Wrapper.

2019-07-16 Thread GitBox
JohnMcW opened a new issue #24: Modern C++17 Wrapper.
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/24
 
 
   After the first release will have a stabilized code and we wrap the current 
c code to c+17 in a couple of week. The current c+ wrapper is just old style C. 
So we will start directly from the c library.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW commented on issue #24: Modern C++17 Wrapper.

2019-07-16 Thread GitBox
JohnMcW commented on issue #24: Modern C++17 Wrapper.
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/24#issuecomment-511839872
 
 
   This issue was https://issues.apache.org/jira/browse/MILAGRO-30 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW opened a new issue #1: Decentralized Custody

2019-07-16 Thread GitBox
JohnMcW opened a new issue #1: Decentralized Custody
URL: https://github.com/apache/incubator-milagro-dta/issues/1
 
 
   As a user, I would like to configure my Milagro Server as both a principal 
and beneficiary, and to use another Milagro Server as the fiduciary.
   
![Milagro%20Node](https://user-images.githubusercontent.com/95958/61301330-95897200-a7db-11e9-9b22-03f0cd14106d.png)
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW commented on issue #3: Distributed Trust Authorities

2019-07-16 Thread GitBox
JohnMcW commented on issue #3: Distributed Trust Authorities
URL: 
https://github.com/apache/incubator-milagro-dta/issues/3#issuecomment-511837572
 
 
   This issue was https://issues.apache.org/jira/browse/MILAGRO-16 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW opened a new issue #25: FP_ZERO redefintion in amcl.h prevents compiling

2019-07-16 Thread GitBox
JohnMcW opened a new issue #25: FP_ZERO redefintion in amcl.h prevents compiling
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/25
 
 
   Enviroment : gcc-7 7.3.0-27ubuntu1~18.04
   Additional Libraries: Protocol Buffers. 
   
![Screenshot%20from%202019-03-31%2014-54-11](https://user-images.githubusercontent.com/95958/61303115-ddf65f00-a7de-11e9-85cd-b40902adeeae.png)
   The current amcl crypto that i am using as backend, redefine FP_ZERO, that 
it is by default defined in math.h in libgcc that it is included in protocol 
buffers, since i am rewriting dta and rps with protobuf3 using amcl.
   This leads to users to be not able to compile. The solution is quite 
trivial, just put
   #ifndef FP_ZERO
   #define FP_ZERO 0
   #endif
   This will solve the issue.
   Best Regards,
   Giorgio


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] JohnMcW commented on issue #25: FP_ZERO redefintion in amcl.h prevents compiling

2019-07-16 Thread GitBox
JohnMcW commented on issue #25: FP_ZERO redefintion in amcl.h prevents compiling
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/25#issuecomment-511843087
 
 
   This issue was https://issues.apache.org/jira/browse/MILAGRO-23 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW commented on issue #2: Config/Install Script

2019-07-16 Thread GitBox
JohnMcW commented on issue #2: Config/Install Script
URL: 
https://github.com/apache/incubator-milagro-dta/issues/2#issuecomment-511834518
 
 
   This was issue https://issues.apache.org/jira/browse/MILAGRO-34 in Apache 
Jira - that issue will be closed presently


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW opened a new issue #5: PKCS11 Integration

2019-07-16 Thread GitBox
JohnMcW opened a new issue #5: PKCS11 Integration
URL: https://github.com/apache/incubator-milagro-dta/issues/5
 
 
   As a user, I want my Milagro Server's secrets protected with an HSM.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] JohnMcW opened a new issue #3: Distributed Trust Authorities

2019-07-16 Thread GitBox
JohnMcW opened a new issue #3: Distributed Trust Authorities
URL: https://github.com/apache/incubator-milagro-dta/issues/3
 
 
   Trusted Authority will be in possession of a master secret
   They will be required to issue cryptographic part-secrets (shares of Milagro 
Tokens), and to protect their own part-secrets. They will be completely law 
abiding within their own individual jurisdictions. They will be expected to be 
open and transparent, and to have a reputation for honesty.
   Distributed Trust Authorities (D-TAs) - Distributed Trust Authorities are 
services run by the stakeholders in a Milagro partition which issue Milagro 
Tokens to People, Apps or Things who petition to obtain them. Distributed Trust 
Authorities may run their own IdPs, or outsource entirely this function.

   The initial version of the D-TA should be derived from the code used in 
Milagro
   The D-TA should be written in Golang in order to utilize this technology's 
strengths
   The D-TA should have the following functionalities:
   Generate Server Keys
   Generate Client Keys
   Generate Time Permits


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #25: FP_ZERO redefintion in amcl.h prevents compiling

2019-07-16 Thread GitBox
kealan commented on issue #25: FP_ZERO redefintion in amcl.h prevents compiling
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/25#issuecomment-511849516
 
 
   This issue has already been spotted and fixed. Please use the develop branch 
until we release the code.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] JohnMcW opened a new issue #19: Add docusaurus headers to markdown files in the docs directory

2019-08-13 Thread GitBox
JohnMcW opened a new issue #19: Add docusaurus headers to markdown files in the 
docs directory
URL: https://github.com/apache/incubator-milagro-crypto-js/issues/19
 
 
   We copy the markdown files from this library's docs directory into this repo:
   
   https://github.com/apache/incubator-milagro/tree/develop/docs/cryptojs
   
   Then use Docusaurus to build the Milagro website here:
   
   http://milagro.apache.org/docs/amcl-javascript-api/
   
   However, Docusaurus requires that each md file has a header in the following 
format:
   
   ```
   ---
   id: aes
   title: AES
   sidebar_label: AES
   ---
   ```
   
   (this is for aes.md)
   
   Please can you add these headers in this repo so that they don't have to be 
added manually each time we need to update the docs site?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-rust] kirk-baird opened a new issue #7: HKDF

2019-08-13 Thread GitBox
kirk-baird opened a new issue #7: HKDF
URL: https://github.com/apache/incubator-milagro-crypto-rust/issues/7
 
 
   # Issue
   As part of the BLS Standard HKDF is being used as part of the hash to curve 
function.
   
   # Required changes
   1) Building HMAC's for the hashing algorithm according to [this 
standard](https://tools.ietf.org/html/rfc2104)
   2) Adding `HKDF-Extract` and `HKDF-Extend` from [this 
standard](https://tools.ietf.org/html/rfc5869).
   
   # Proposal
   As the sha256/384/512 algorithms have already been implemented I suggest 
simply adding a `hmac` function and the two functions for HKDF to each of those 
structs.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-rust] kirk-baird opened a new pull request #6: Documentation

2019-08-13 Thread GitBox
kirk-baird opened a new pull request #6: Documentation
URL: https://github.com/apache/incubator-milagro-crypto-rust/pull/6
 
 
   There are not functional changes in this PR just increase the Documentation 
of methods and add a reference to the paper where the Montgomery calculations 
were proposed.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london opened a new pull request #13: Updating Website

2019-08-13 Thread GitBox
spector-in-london opened a new pull request #13: Updating Website
URL: https://github.com/apache/incubator-milagro/pull/13
 
 
   Moving develop branch into master to run asf-site build script


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco opened a new issue #37: Difference with skair39/milagro-crypto-c

2019-08-14 Thread GitBox
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 official and the other a old one.
   
   Could you confirm me that?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco opened a new issue #38: Python wrappers

2019-08-14 Thread GitBox
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: https://lists.hyperledger.org/g/fabric/message/6625
   
   I wonder if all the python wrappers are available for the milagro crypto c 
libreary.
   For exemple. I need to translate this:
   go implementation:
   ```go
   // RandModOrder returns a random element in 0, ..., GroupOrder-1
   func RandModOrder(rng *amcl.RAND) *FP256BN.BIG {
  // curve order q
  q := FP256BN.NewBIGints(FP256BN.CURVE_Order)
   
  // Take random element in Zq
  return FP256BN.Randomnum(q, rng)
   }
   ```
   or 
   java implementation
   ```java
   public static BIG randModOrder(RAND rng) {
   BIG q = new BIG(ROM.CURVE_Order);
   
   // Takes random element in this Zq.
   return BIG.randomnum(q, rng);
   }
   ```
   
   to python code.
   Is this achievable right now?

   Thanks,


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco opened a new issue #39: Python test wrappers - python 3?

2019-08-14 Thread GitBox
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,


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #37: Difference with skair39/milagro-crypto-c

2019-08-14 Thread GitBox
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 automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan opened a new issue #29: Add ECIES test vectors

2019-07-31 Thread GitBox
kealan opened a new issue #29: Add ECIES test vectors
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/29
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] jaromil commented on issue #32: Miller loop test fail in Zenroom using BLS383

2019-08-04 Thread GitBox
jaromil commented on issue #32: Miller loop test fail in Zenroom using BLS383
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/32#issuecomment-517983739
 
 
   Hi Kealan, thanks for your reply! about the Miller Loop test on BLS383 (the 
only curve I can easily test right now in Zenroom), I confirm the 
non-deterministic failure of the test (passes once ever 4 or 5 execution times) 
also with the current develop branch. Zenroom code used for the test:
   ```lua
   ECP = require('zenroom_ecp')
   ECP2 = require('zenroom_ecp2')
   G1 = ECP.generator()
   G2 = ECP2.generator()
   r = ECP.order()
   -- generate a big random number of maximum INT size and apply modulo of the 
curve's order  
   function R() return INT.modrand(r) end
   P1 = G1 * R() -- Pick a random point in G1
   Q1 = G2 * R() -- Pick a random point in G2
   -- Test that miller(sQ,P) = miller(Q,P)^s, s random"
   s = R()
   g1 = ECP2.miller( Q1*s, P1)
   g2 = ECP2.miller( Q1, P1)^s
   assert(g1 == g2)
   ```
   
   About the other points, in the hope are useful, hereby my opinions:
   1. Publish an annotated diff of the repository history pre and post ASF, 
eliminating cosmetic changes (whitespace and emails) and build system changes, 
to focus on what changes in the code between the last commit on "version 4" and 
the first commit on the new repo.
   2. Milagro is wonderful in many ways, one of them is that it is a generic 
base library for crypto providing choice among a number of curves. If it is no 
effort to maintain "old" curves then I recommend keeping them around. It is 
also what made OpenSSL dominate the scene so far so this is mostly a strategic 
choice, if at par with effort.
   2a. If there would be anything that I'd shave off Milagro that would be RSA.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #32: Miller loop test fail in Zenroom using BLS383

2019-08-04 Thread GitBox
kealan commented on issue #32: Miller loop test fail in Zenroom using BLS383
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/32#issuecomment-517981429
 
 
   Hi Yes it is pity what happened with the commit history. We should have been 
developing on Apache from the start.
   
   The project is hoping to make a release next week or at least start the 
process. Until then I would not look at the master branch but use the develop 
branch. 
   
   I would be concerned if what you say doesn't work on the develop branch. It 
would be strange as the tests pass and the schemes built on top of pairing 
work. 
   
   Also, is there an argument for reducing the number of curves. What do we 
need BLS383 when we have BLS12-381? Do we need to support BN254CX etc.?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] GregTheGreek closed pull request #20: Greg/release/v0.1.4

2019-08-16 Thread GitBox
GregTheGreek closed pull request #20: Greg/release/v0.1.4
URL: https://github.com/apache/incubator-milagro-crypto-js/pull/20
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] GregTheGreek opened a new pull request #20: Greg/release/v0.1.4

2019-08-16 Thread GitBox
GregTheGreek opened a new pull request #20: Greg/release/v0.1.4
URL: https://github.com/apache/incubator-milagro-crypto-js/pull/20
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london merged pull request #11: Cryptodocsv1

2019-08-12 Thread GitBox
spector-in-london merged pull request #11: Cryptodocsv1
URL: https://github.com/apache/incubator-milagro/pull/11
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london merged pull request #10: Dev

2019-08-12 Thread GitBox
spector-in-london merged pull request #10: Dev
URL: https://github.com/apache/incubator-milagro/pull/10
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london merged pull request #9: README.md update

2019-08-12 Thread GitBox
spector-in-london merged pull request #9: README.md update
URL: https://github.com/apache/incubator-milagro/pull/9
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london opened a new pull request #10: Dev

2019-08-12 Thread GitBox
spector-in-london opened a new pull request #10: Dev
URL: https://github.com/apache/incubator-milagro/pull/10
 
 
   Merge Dev


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london merged pull request #8: Update footer to non-archived repo.

2019-08-12 Thread GitBox
spector-in-london merged pull request #8: Update footer to non-archived repo.
URL: https://github.com/apache/incubator-milagro/pull/8
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london opened a new pull request #11: Cryptodocsv1

2019-08-12 Thread GitBox
spector-in-london opened a new pull request #11: Cryptodocsv1
URL: https://github.com/apache/incubator-milagro/pull/11
 
 
   Merge


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london opened a new pull request #9: README.md update

2019-08-12 Thread GitBox
spector-in-london opened a new pull request #9: README.md update
URL: https://github.com/apache/incubator-milagro/pull/9
 
 
   updated Readme.md


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london commented on issue #8: Update footer to non-archived repo.

2019-08-12 Thread GitBox
spector-in-london commented on issue #8: Update footer to non-archived repo.
URL: https://github.com/apache/incubator-milagro/pull/8#issuecomment-520357069
 
 
   Hi, yes it should. We're going to fix this.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-rust] kirk-baird commented on issue #7: HKDF

2019-08-14 Thread GitBox
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.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-15 Thread GitBox
kealan commented on issue #38: Python wrappers
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521591519
 
 
   You are welcome. You have the idea now - just build the library for the 
curve you are interested in.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-15 Thread GitBox
kealan commented on issue #38: Python wrappers
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521540065
 
 
   It could be that you need to link the dependent components;
   
   See if you can build and run one of the examples after installation;
   
   1. use BLS381 in config.mk 
   2. make; cd target/default; make install
   3. cp target/default/examples/example_bls_BLS381.c  /tmp
   4. cd tmp
   5. edit /tmp/example_bls_BLS381.c
   
   #include 
   #include 
   #include 
   #include 
   #include 
   
   #if CURVE_SECURITY_BLS381 == 128
   #include 
   #elif CURVE_SECURITY_BLS381 == 192
   #include 
   #elif CURVE_SECURITY_BLS381 == 256
   #include 
   #endif
   
   6. Build 
   
   gcc -O0 -g ./example_bls_BLS381.c $(pkg-config --libs --cflags amcl) -o 
example_bls_BLS381
   
   For a new library that you want a CFFI interface you need to do the linking 
- that seems to be the only step you are missing.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #38: Python wrappers

2019-08-15 Thread GitBox
GuillaumeCisco commented on issue #38: Python wrappers
URL: 
https://github.com/apache/incubator-milagro-crypto-c/issues/38#issuecomment-521572957
 
 
   Ok I succeeded runing this example, on a fresh environment, using these 
steps:
   
   `sudo apt-get install -y git cmake build-essential python python-dev 
python-pip libffi-dev doxygen doxygen-latex parallel `
   `pip install cffi` (in a virtual env)
   Do not modify config.mk
   `make`
   `cd target/default`
   `sudo make install` (sudo is important for installing in /usr/... folders)
   `cp ./example_bls_BLS381.c /tmp`
   `cd /tmp`
   Edit `example_bls_BLS381.c` for replacing imports"
   ```
   #include "config_curve_BLS381.h"
   #include "randapi.h"
   
   #if CURVE_SECURITY_BLS381 == 128
   #include "bls_BLS381.h"
   #elif CURVE_SECURITY_BLS381 == 192
   #include "bls192_BLS381.h"
   #elif CURVE_SECURITY_BLS381 == 256
   #include "bls256_BLS381.h"
   #endif
   ```
   to
   ```
   #include 
   #include 
   
   #if CURVE_SECURITY_BLS381 == 128
   #include 
   #elif CURVE_SECURITY_BLS381 == 192
   #include 
   #elif CURVE_SECURITY_BLS381 == 256
   #include 
   #endif
   ```
   Then compile it"
   `gcc -O0 -g ./example_bls_BLS381.c $(pkg-config --libs --cflags amcl) -o 
example_bls_BLS381`
   Try it:
   ```
   $> ./example_bls_BLS381 
   ./example_bls_BLS381: error while loading shared libraries: 
libamcl_core.so.1: cannot open shared object file: No such file or directory
   ```
   Find where is `libamcl_core.so`.
   ```
$> sudo find / -name libamcl_core.so
   /usr/local/lib/libamcl_core.so
   ```
   exporting library
   `export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib/`
   Try again:
   ```
   ./example_bls_BLS381 
   SEED: 78d0fb6705ce77dee47d03eb5b9c5d30
   
   
   Testing BLS signature for curve BLS381
   Private key SK1: 
1ab4d90898292c30524488630453308cd2fa1f9d76c15f98b1025138f81bf1da
   Public key PKTMP: 
0f0bcdc9de4968355e30302ef97e8ec0dd344f87aeb35f6c556dc810a0a506a7aa5e8a4ae3063ad7de241511445e708006796e2ba3b366fda588937fa5cead3a9b6e0e6c29eb328339cd1afb3e0c838f39d2a5f438122c35529658cccd789c700f33fd318079ec077f7c17b89d5c94fe1d3fab02cde565854a93458dce002241281a7e2d9f58d8a88952fc7fe0260991bc6c2971004a78c9724a18f5fa4c4995b2a2697b9cb0d0adddfae6f500b0732173f092971cbaaaba13c8ffb4ec09
   Public key PK1: 
0f0bcdc9de4968355e30302ef97e8ec0dd344f87aeb35f6c556dc810a0a506a7aa5e8a4ae3063ad7de241511445e708006796e2ba3b366fda588937fa5cead3a9b6e0e6c29eb328339cd1afb3e0c838f39d2a5f438122c35529658cccd789c700f33fd318079ec077f7c17b89d5c94fe1d3fab02cde565854a93458dce002241281a7e2d9f58d8a88952fc7fe0260991bc6c2971004a78c9724a18f5fa4c4995b2a2697b9cb0d0adddfae6f500b0732173f092971cbaaaba13c8ffb4ec09
   Private key SK2: 
2c78985d1620cf5f585fb95fa12643f35874f8ac3e27b1a72793244734eadb2b
   Public key PK2: 
00e083bfbf91ccb04e332758ae84aecd23948b349a36d271e9444c04d2cd9263e4cd2b7df79187a71f2d2a2059524938169b09f3ce0e8be623ede589bb5b8d999d023222a20827089897217667b11d8d659bb42b1b55127659b5d2dda50af5eb0e7b36d785d1db7ffcfbbee023c6330ad39440bf8ed287657ea7a3b4b30445de1eb512f8764d3ce7b2a1aa6505e267d81155e430e7248c20ee62d7dc7836d1835f9c0cbf0d551f469ff2e2a7ffcaab46be00162e30e09a382f02396828bbabf9
   Private key SK3: 
2c78985d1620cf5f585fb95fa12643f35874f8ac3e27b1a72793244734eadb2b
   Public key PK3: 
00e083bfbf91ccb04e332758ae84aecd23948b349a36d271e9444c04d2cd9263e4cd2b7df79187a71f2d2a2059524938169b09f3ce0e8be623ede589bb5b8d999d023222a20827089897217667b11d8d659bb42b1b55127659b5d2dda50af5eb0e7b36d785d1db7ffcfbbee023c6330ad39440bf8ed287657ea7a3b4b30445de1eb512f8764d3ce7b2a1aa6505e267d81155e430e7248c20ee62d7dc7836d1835f9c0cbf0d551f469ff2e2a7ffcaab46be00162e30e09a382f02396828bbabf9
   
   SIG1: 
0308be9a543a978c9a5b143fc8aed6482bdbe5f9dd969693b65c9b2bfdea25e1a611bcbf96f8899bfea06ef71c30bf70ad
   SIG2: 
0216d5cbfd2e29445a42bfa7075a28fdf139d4d9c48f31c7233c8b9822929148bdf0fadf315f082c2377ed08cf5dd57f5b
   SIG3: 
02082ab439b2c6d366199ae44fcdf72f15529a3af88f413a471196a69aaf65ccddf9ace8a9975426c6080148ca2d30ac9b
   
   Success: Signature is valid
   Success: Signature is valid
   Success: Signature is valid
   Public key PK: 
08c2ead7baac23a8b648d6572fd2b3cfe06a0a3d31dafdde14f901fdc582be72647fcc088d33b923ddcc63eba62723e81403ce9283381ab0b56d398da01b7886064eb5679d164cd1fb2efcac21f56d19247d40b7a52a4e6463c792bfb41909f40b1024ffdf0a7fdfc4f92c437f00dde3ac8bbff6c6bbe65a8393aa488d6b5af7f7919acee8262eb240915619b95a65f4017785c554211282bd3d2478fcb236d4fa7c459a6a7b2067785d1a50ae00c9ea5a4921d80a41b8b26b7ce6f34d3a8b2a
   
   Error: Aggregated signature is invalid (expected result) 
   SIG: 
030b5620207d709e2991413830ba052fc15199731442f8b868217de7cceaa5406c27261c76eb942b426d0c031e8a349836
   
   Success: Aggregated signature is valid
   message Zest message
   Error: Invalid Signature (expected result) 
   message test message
   Signature SIG1: 

[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #39: Python test wrappers - python 3?

2019-08-14 Thread GitBox
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 with python3 on 
https://github.com/skair39/milagro-crypto-c
   I will adapt my patch to this project.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #39: Python test wrappers - python 3?

2019-08-14 Thread GitBox
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 message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
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?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 only constants so I don't see that you would need a wrapper for them.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 `bls_BLS381.py`...
   If I understand it correctly, `.py.in` are only template files for a 
building over a specific curve. Here `BLS381`.
   In my particular case, I should build these files against `FP256BN`.
   I also tried the `./scripts/buildMulti.sh` and saw no new files :/
   I also looked at the config.mk file.
   I can see: `AMCL_CURVE:=ED25519,NIST256,GOLDILOCKS,BLS381`
   Replacing it by `AMCL_CURVE:=FP256BN` and then running `make`, produced 
files like `bls_FP256BN.py` files which is what I'm looking for :)
   
   Thanks! I'm still discovering this project and your help is greatly 
appreciated.
   I also see a folder `target/default/lib`  with *.so files (I'm on linux).
   `libamcl_bls_FP256BN.so`
   `libamcl_core_FP256BN.so`
   `libamcl_curve_FP256BN.so`
   `libamcl_mpin_FP256BN.so`
   `libamcl_pariing_FP256BN.so`
   `libamcl_rsa_FP256BN.so`
   `libamcl_wcc_FP256BN.so`
   `libamcl_x509.so`
   
   We have three templates:
   `bls_ZZZ.py.in`
   `mpin_ZZZ.py.in`
   `wcc_ZZZ.py.in`
   Should we create these others templates too?
   `core_ZZZ.py.in`
   `curve_ZZZ.py.in`
   `pairing_ZZZ.py.in`
   `rsa_ZZZ.py.in`
   
   Now I need an extra help about handling the constants from 
`rom_curve_FP256BN.c` for example.
   How from python could I load the `CURVE_Order_FP256BN`.
   I guess this will be translated to a python tuple... but can't figure out 
how to import it.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 little help.
   I'll try a to make a Pull Request for supporting the `rom.c` file, if you 
can help me on this, it would be great!


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco closed issue #37: Difference with skair39/milagro-crypto-c

2019-08-14 Thread GitBox
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 message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #37: Difference with skair39/milagro-crypto-c

2019-08-14 Thread GitBox
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 from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
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?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 
   #include 
   #include 
   
   int main()
   {
 BIG_384_58 q2;
 BIG_384_58 r2;
   
 printf("BLS381\n");  
 BIG_384_58_rcopy(q2,Modulus_BLS381);
 printf("q (381) = 0x");
 BIG_384_58_output(q2);  
 printf("\n");  
 BIG_384_58_rcopy(r2,CURVE_Order_BLS381);
 printf("r (257) = 0x");
   }


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] kealan opened a new issue #21: Add SSS to BLS

2019-08-19 Thread GitBox
kealan opened a new issue #21: Add SSS to BLS
URL: https://github.com/apache/incubator-milagro-crypto-js/issues/21
 
 
   Add Shamir's Secret Sharing (SSS) algorithm to enable this functionality
   
   1. Split BLS secret key into shares
   2. Recombine BLS signatures shares using SSS so that they form the original 
signature


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] Mikerah opened a new pull request #18: Added missing parameters to ECDH DSA function

2019-08-13 Thread GitBox
Mikerah opened a new pull request #18: Added missing parameters to ECDH DSA 
function
URL: https://github.com/apache/incubator-milagro-crypto-js/pull/18
 
 
   I added some missing parameters, namely `S` (private key) and `F` (message 
to sign) to `ECPSP_DSA`.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-js] Mikerah closed pull request #18: Added missing parameters to ECDH DSA function

2019-08-13 Thread GitBox
Mikerah closed pull request #18: Added missing parameters to ECDH DSA function
URL: https://github.com/apache/incubator-milagro-crypto-js/pull/18
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london closed issue #6: Web/documentation needs refresh

2019-08-13 Thread GitBox
spector-in-london closed issue #6: Web/documentation needs refresh
URL: https://github.com/apache/incubator-milagro/issues/6
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london commented on issue #6: Web/documentation needs refresh

2019-08-13 Thread GitBox
spector-in-london commented on issue #6: Web/documentation needs refresh
URL: https://github.com/apache/incubator-milagro/issues/6#issuecomment-520853611
 
 
   Let's close issue.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london opened a new pull request #12: Fixes

2019-08-13 Thread GitBox
spector-in-london opened a new pull request #12: Fixes
URL: https://github.com/apache/incubator-milagro/pull/12
 
 
   Merging fixes into develop


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro] spector-in-london merged pull request #12: Fixes

2019-08-13 Thread GitBox
spector-in-london merged pull request #12: Fixes
URL: https://github.com/apache/incubator-milagro/pull/12
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 
   #include 
   
   int main()
   {
   BIG_256_56 q2;
   BIG_256_28 r2;
   
   printf("BLS381\n");
   BIG_256_56_rcopy(q2, Modulus_FP256BN);
   printf("q (381) = 0x");
   BIG_256_56_output(q2);
   printf("\n");
   BIG_256_28_rcopy(r2 ,CURVE_Order_FP256BN);
   printf("r (257) = 0x");
   }
   ```
   
   Then how do I wrap it with cffi?
   If I write something like:
   ```python
   import cffi
   import platform
   
   ffi = cffi.FFI()
   ffi.cdef("""
  int main();
   """)
   
   
   if (platform.system() == 'Windows'):
   libamcl_wcc_FP256BN = ffi.dlopen("libamcl_wcc_FP256BN.dll")
   libamcl_core = ffi.dlopen("libamcl_core.dll")
   elif (platform.system() == 'Darwin'):
   libamcl_wcc_FP256BN = ffi.dlopen("libamcl_wcc_FP256BN.dylib")
   libamcl_core = ffi.dlopen("libamcl_core.dylib")
   else:
   libamcl_wcc_FP256BN = ffi.dlopen("libamcl_wcc_FP256BN.so")
   libamcl_core = ffi.dlopen("libamcl_core.so")
   
   libamcl_core.main()
   
   ```
   It won't work, as there is no link between rom.c and `libamcl_core`.
   I should create a .so file from the rom.c, right?
   I have no knowledge in cffi and will learn how to use it.
   But a little help would be great ;)
   Also is it possible to simply export constant from a C code for importing it 
after from python?
   
   Thanks


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 
   
   int main()
   {
   BIG_256_56 q2;
   BIG_256_28 r2;
   
   printf("BLS381\n");
   BIG_256_56_rcopy(q2, Modulus_FP256BN);
   printf("q (381) = 0x");
   BIG_256_56_output(q2);
   printf("\n");
   BIG_256_28_rcopy(r2 ,CURVE_Order_FP256BN);
   printf("r (257) = 0x");
   }
   ```
   
   Then how do I wrap it with cffi?
   If I write something like:
   ```python
   #include 
   #include 
   #include 
   #include 
   #include 
   
   int main()
   {
   BIG_256_56 q2;
   BIG_256_28 r2;
   
   printf("BLS381\n");
   BIG_256_56_rcopy(q2, Modulus_FP256BN);
   printf("q (381) = 0x");
   BIG_256_56_output(q2);
   printf("\n");
   BIG_256_28_rcopy(r2 ,CURVE_Order_FP256BN);
   printf("r (257) = 0x");
   }
   ```
   It won't work, as there is no link between rom.c and `libamcl_core`.
   I should create a .so file from the rom.c, right?
   I have no knowledge in cffi and will learn how to use it.
   But a little help would be great ;)
   Also is it possible to simply export constant from a C code for importing it 
after from python?
   
   Thanks


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco commented on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 directory) using:
   `gcc -g -I../../include -I../../../../include -fPIC -Wall -Wextra 
../../test/test_pair_FP256BN.c -shared -o ./test_pair_FP256BN.so`
   Then:
   ```
   $> python
   Python 2.7.15+ (default, Nov 27 2018, 23:36:35) 
   [GCC 7.3.0] on linux2
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import test_pair_FP256BN
   Traceback (most recent call last):
 File "", line 1, in 
   ImportError: ./test_pair_FP256BN.so: undefined symbol: CURVE_Order_FP256BN
   ```
   There is something I'm not doing correctly...


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] GuillaumeCisco edited a comment on issue #38: Python wrappers

2019-08-14 Thread GitBox
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 directory) using:
   `gcc -g -I../../include -I../../../../include -fPIC -Wall -Wextra 
../../test/test_pair_FP256BN.c -shared -o ./test_pair_FP256BN.so`
   With a file named test_pair_FP256BN.py:
   ```
   import cffi
   
   ffi = cffi.FFI()
   ffi.cdef("""
  int main();
   """)
   
   
   lib = ffi.dlopen("./rom.so")
   lib.main()
   ```
   
   Then:
   ```
   $> python
   Python 2.7.15+ (default, Nov 27 2018, 23:36:35) 
   [GCC 7.3.0] on linux2
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import test_pair_FP256BN
   Traceback (most recent call last):
 File "", line 1, in 
   ImportError: ./test_pair_FP256BN.so: undefined symbol: CURVE_Order_FP256BN
   ```
   There is something I'm not doing correctly...


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan opened a new issue #41: fix test_output_functions_ZZZ.c.in on Fedora

2019-08-22 Thread GitBox
kealan opened a new issue #41: fix test_output_functions_ZZZ.c.in on Fedora
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/41
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed pull request #6: Update open-api.yaml

2019-08-20 Thread GitBox
howardkitto closed pull request #6: Update open-api.yaml
URL: https://github.com/apache/incubator-milagro-dta/pull/6
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto commented on issue #6: Update open-api.yaml

2019-08-20 Thread GitBox
howardkitto commented on issue #6: Update open-api.yaml
URL: 
https://github.com/apache/incubator-milagro-dta/pull/6#issuecomment-523033182
 
 
   Updated Open API.yaml - not yet tested


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] spector-in-london closed issue #40: add sss to bls

2019-08-27 Thread GitBox
spector-in-london closed issue #40: add sss  to bls
URL: https://github.com/apache/incubator-milagro-crypto-c/issues/40
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] spector-in-london merged pull request #47: BLS SSS

2019-08-27 Thread GitBox
spector-in-london merged pull request #47: BLS SSS
URL: https://github.com/apache/incubator-milagro-crypto-c/pull/47
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] spector-in-london commented on issue #47: BLS SSS

2019-08-27 Thread GitBox
spector-in-london commented on issue #47: BLS SSS
URL: 
https://github.com/apache/incubator-milagro-crypto-c/pull/47#issuecomment-525209629
 
 
   Awesome.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan opened a new pull request #48: update license

2019-08-27 Thread GitBox
kealan opened a new pull request #48: update license
URL: https://github.com/apache/incubator-milagro-crypto-c/pull/48
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan opened a new issue #8: Add BLS-SSS golang wrapper

2019-08-27 Thread GitBox
kealan opened a new issue #8: Add BLS-SSS golang wrapper
URL: https://github.com/apache/incubator-milagro-dta/issues/8
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-crypto-c] kealan merged pull request #48: update license

2019-08-27 Thread GitBox
kealan merged pull request #48: update license
URL: https://github.com/apache/incubator-milagro-crypto-c/pull/48
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan merged pull request #9: update README build instructions

2019-08-27 Thread GitBox
kealan merged pull request #9: update README build instructions
URL: https://github.com/apache/incubator-milagro-dta/pull/9
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan opened a new pull request #9: update README build instructions

2019-08-27 Thread GitBox
kealan opened a new pull request #9: update README build instructions
URL: https://github.com/apache/incubator-milagro-dta/pull/9
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] fluidjax merged pull request #19: Fix Invalid method sig

2019-08-30 Thread GitBox
fluidjax merged pull request #19: Fix Invalid method sig
URL: https://github.com/apache/incubator-milagro-dta/pull/19
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] fluidjax merged pull request #18: Add order/secret request validation

2019-08-30 Thread GitBox
fluidjax merged pull request #18: Add order/secret request validation
URL: https://github.com/apache/incubator-milagro-dta/pull/18
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] fluidjax opened a new pull request #18: Add order/secret request validation

2019-08-30 Thread GitBox
fluidjax opened a new pull request #18: Add order/secret request validation
URL: https://github.com/apache/incubator-milagro-dta/pull/18
 
 
   Add validation to trap /order & /order/secret beneficiary inconsistencies.
   1) Create error when beneficiaries are not specified at all
   2) Create error when Beneficiaries specified in both, and different
   3) Ignore Beneficiary in /order/secret when the beneficiary has already been 
specified in /order.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan merged pull request #10: update headers in crypto code

2019-08-28 Thread GitBox
kealan merged pull request #10: update headers in crypto code
URL: https://github.com/apache/incubator-milagro-dta/pull/10
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan opened a new pull request #10: update headers in crypto code

2019-08-28 Thread GitBox
kealan opened a new pull request #10: update headers in crypto code
URL: https://github.com/apache/incubator-milagro-dta/pull/10
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto opened a new pull request #21: Initial dta

2019-08-30 Thread GitBox
howardkitto opened a new pull request #21: Initial dta
URL: https://github.com/apache/incubator-milagro-dta/pull/21
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] smihaylov merged pull request #21: Initial dta

2019-08-30 Thread GitBox
smihaylov merged pull request #21: Initial dta
URL: https://github.com/apache/incubator-milagro-dta/pull/21
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto opened a new issue #22: Build Instructions for Mac

2019-08-30 Thread GitBox
howardkitto opened a new issue #22: Build Instructions for Mac
URL: https://github.com/apache/incubator-milagro-dta/issues/22
 
 
   Can we update the readme page to help developers who use macs


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto opened a new issue #23: build_static.sh doesn't run on Ubuntu

2019-08-30 Thread GitBox
howardkitto opened a new issue #23: build_static.sh doesn't run on Ubuntu
URL: https://github.com/apache/incubator-milagro-dta/issues/23
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto commented on issue #8: Add BLS-SSS golang wrapper

2019-08-30 Thread GitBox
howardkitto commented on issue #8: Add BLS-SSS golang wrapper
URL: 
https://github.com/apache/incubator-milagro-dta/issues/8#issuecomment-526632117
 
 
   BLS is now supported in Identity documents


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed issue #8: Add BLS-SSS golang wrapper

2019-08-30 Thread GitBox
howardkitto closed issue #8: Add BLS-SSS golang wrapper
URL: https://github.com/apache/incubator-milagro-dta/issues/8
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] smihaylov opened a new pull request #20: Update copyright in LICENSE

2019-08-30 Thread GitBox
smihaylov opened a new pull request #20: Update copyright in LICENSE
URL: https://github.com/apache/incubator-milagro-dta/pull/20
 
 
   Update go-ipfs to version 0.4.22


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed issue #4: Docker Container Deployment

2019-08-30 Thread GitBox
howardkitto closed issue #4: Docker Container Deployment
URL: https://github.com/apache/incubator-milagro-dta/issues/4
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed issue #1: Decentralized Custody

2019-08-30 Thread GitBox
howardkitto closed issue #1: Decentralized Custody
URL: https://github.com/apache/incubator-milagro-dta/issues/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed issue #2: Config/Install Script

2019-08-30 Thread GitBox
howardkitto closed issue #2: Config/Install Script
URL: https://github.com/apache/incubator-milagro-dta/issues/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto merged pull request #17: Bugfix btcopen api

2019-08-30 Thread GitBox
howardkitto merged pull request #17: Bugfix btcopen api
URL: https://github.com/apache/incubator-milagro-dta/pull/17
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] fluidjax opened a new pull request #24: Beneficiary fix

2019-09-04 Thread GitBox
fluidjax opened a new pull request #24: Beneficiary fix
URL: https://github.com/apache/incubator-milagro-dta/pull/24
 
 
   Fix: When Beneficiary is specified, ensure the Bitcoin Wallet is generated 
with the EC keys from beneficiary not principal
   Add: 2 End to End tests, to test when Principal != Beneficiary


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan merged pull request #12: add code to cmake to enable shared build

2019-08-28 Thread GitBox
kealan merged pull request #12: add code to cmake to enable shared build
URL: https://github.com/apache/incubator-milagro-dta/pull/12
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] kealan opened a new pull request #12: add code to cmake to enable shared build

2019-08-28 Thread GitBox
kealan opened a new pull request #12: add code to cmake to enable shared build
URL: https://github.com/apache/incubator-milagro-dta/pull/12
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto opened a new pull request #11: merged install instructions

2019-08-28 Thread GitBox
howardkitto opened a new pull request #11: merged install instructions
URL: https://github.com/apache/incubator-milagro-dta/pull/11
 
 
   Added some extra detail to readme file


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto closed pull request #11: merged install instructions

2019-08-28 Thread GitBox
howardkitto closed pull request #11: merged install instructions
URL: https://github.com/apache/incubator-milagro-dta/pull/11
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto opened a new pull request #13: Update readme

2019-08-28 Thread GitBox
howardkitto opened a new pull request #13: Update readme
URL: https://github.com/apache/incubator-milagro-dta/pull/13
 
 
   The Readme file now has a better description of the product and the 
installation and build instructions for Ubuntu have been tested and updated.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] howardkitto merged pull request #13: Update readme

2019-08-28 Thread GitBox
howardkitto merged pull request #13: Update readme
URL: https://github.com/apache/incubator-milagro-dta/pull/13
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



[GitHub] [incubator-milagro-dta] smihaylov merged pull request #16: set default cors allow to *

2019-08-29 Thread GitBox
smihaylov merged pull request #16: set default cors allow to *
URL: https://github.com/apache/incubator-milagro-dta/pull/16
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org
For additional commands, e-mail: issues-h...@milagro.apache.org



  1   2   3   4   5   6   7   >