Page History

...

Announcements

Announcements

Hyperledger Meetup in BelgradeAries Workshop/Connectathon December 3-5 in Provo, Utah (details to follow)
Internet Identity Workshop — want to coordinate demos
Bootcamp Russia: Event Location
Hyperledger Maintainers Summit: Minneapolis October 8-10Bootcamp Russia: Event Location
Aries Workshop/Connectathon December 3-5 in Provo, Utah (details to follow)

Summary of Prior Call

Indy Node
- September: 1.10.0
  - Refactoring for PBFT View Change and BLS signature
  - Bug fixesPBFT view change
  - Indy Node and Indy Plenum support for Ubuntu 18.04 is at risk for September
- October: 1.11.0
  - PBFT view change
Indy SDK
- September: 1.12.0
  - Fully qualified DIDs
  - Platform Updates: MacOS, CentOS
- Future
  - GitLab migration alongside Jenkins (Foundation)?
  - Aries / Indy split: next step is aries-core-wallet
  - Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
Ursa
- September: 0.2.0
  - ZKP / ZKLang improvements
  - Debian packages
  - Encryption for Anoncreds 2.0
  - Refactor multi-signature BLS in addition to aggregated signature
Aries
- Lots of progress on language libraries, frameworks, and agents.
Indy Catalyst
- Production deployment testing: volume loads.
- Won't go live in production at BC.gov until October.
- Not yet migrated to Hyperledger. Needs more documentation.

...

Future calls:
- Cancel the call September 30 for IIW
- Cancel the call October 14
Non-secrets in the Indy Wallet
- Cam is working on pluggable crypto. They wallet shouldn't decide what encryption you should be using.
- Use cases where we would want to move keys between wallets
  - Moving the link secret / credential data from one device to another (synchronized storage).
  - Debug use cases
  - Richard's hit other uses cases that were better solved with DID Doc, pre-signing, signing API.
- Work-around with the web-crypto API
Fully Qualified DID support in Indy SDK
Ubuntu 18.04 on Indy Node
- Want to support 18.04 and 16.04 simultaneously (until 20.04 comes out).
- Cam has a PR, and is working on incorporating feedback.
Security reports
Ursa and AMCL: Discussed in the Ursa call (August 21), but no decision yet.
fuzzing libindy https://github.com/AxelNennker/indy-sdk/tree/fuzzing/
`cargo +nightly fuzz run fuzz_target_1 -- -only_ascii=1`
Worried about unsafe code in libindy
```
ignisvulpis@namenlos:~/development/hyperledger/indy-sdk/libindy$ find src -name \*\.rs -exec fgrep unsafe {} \; | wc -l
61
```

Non-secrets in the Indy Wallet
- Cam is working on pluggable crypto. They wallet shouldn't decide what encryption you should be using.
- Use cases where we would want to move keys between wallets
  - Moving the link secret / credential data from one device to another (synchronized storage).
  - Debug use cases
  - Richard's hit other uses cases that were better solved with DID Doc, pre-signing, signing API.
- Work-around with the web-crypto API
Fully Qualified DID support in Indy SDKUrsa and AMCL: Discussed in the Ursa call (August 21), but no decision yet.
Define pull request review process for Indy Node.
- Should define the process, including how we handle exceptions (emergency fixes shouldn't be blocked, but would require notification)
- What is important in a good review?
- If a review must be skipped, should note it in the Git commit message.
Handling pull requests.
- How to handle old pull requests that failed DCO Checks? Close?
  - Closing the PR doesn't get rid of the work. The author can reopen at any time.
- How to handle pull requests for IOS / Swift wrappers? Close and encourage the move to Aries?
- How to handle pull requests for LibVCX? Deprecate?
- Close PR https://github.com/hyperledger/indy-sdk/pull/1048 as something that will be replaced by the advanced schema work?
- HIPE pull requests: https://github.com/hyperledger/indy-hipe/pulls
- Kyle will continue reviewing PRs, but does not want to be a bottleneck slowing down the process.

...