Giter Site home page Giter Site logo

build-trust / ockam Goto Github PK

View Code? Open in Web Editor NEW
4.3K 57.0 557.0 74.61 MB

Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.

Home Page: https://ockam.io

License: Apache License 2.0

Elixir 20.77% Rust 73.72% TypeScript 0.21% Shell 2.15% Erlang 0.38% Makefile 0.19% Swift 2.58%
messaging authentication key-management identity trust kafka rust security end-to-end-encryption encrypted-connections

ockam's People

Contributors

0xkelvin avatar adrianbenavides avatar antoinevg avatar bitwalker avatar davide-baldo avatar dependabot[bot] avatar etorreborre avatar glenngillen avatar hairyhum avatar hargut avatar lameferret avatar leonzchang avatar malnick avatar mattgreg avatar metaclips avatar michealkeines avatar miles170 avatar mrinalwadhwa avatar murex971 avatar nazmulidris avatar neil2468 avatar nidnogg avatar ockam-team avatar polvorin avatar robinbudd avatar sanjodeundiak avatar shanesveller avatar spacekookie avatar thomcc avatar twittner avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ockam's Issues

Introduction and Framing Contributions

Hello,

I am jumping in to start some threads and contribute to issues. At present I am unable to contribute to the code repository directly until I receive appropriate clearance through my main employer. There should not be any issue, though it can take time. Until then, this note is on file to set scope of involvement and anticipated contributions.

In my role at Dolby I am responsible for scouting and assessing new possibilities of technology and business models. Over the last four years, a key theme has been on connected audio devices. I lead a technical team setting out some of the more longer term aspects, implications, designs, performance, possibilities and user experiences. This is within the Technology Incubation Group led by Mike Hollier.

There is a clear future where audio devices will be present and need to be co-ordinated at a scale beyond human intervention - imaging 60 billion microphones to choose from in routing audio with appropriate security and privacy. There are deep adjacent threads in my team on what this means for society, ethics, privacy and the implications of the post privacy audio world already upon us. My involvement with Ockam is exploratory around the possibility of a secure distributed approach that can scale and offer what is needed in addition to any audio processing in the realm of DUAD (distributed uncertain and asynchronous audio devices).

At this stage, some notes and scope limiting of my contribution

  • Contribution to issues and comments only, with inline example code but no code contribution to the main repository
  • Expressed opinions are personal and rising from personal technology experience and perspective
  • The interest of Dolby is associative through myself, but not direct or indicative of any business relationship at this stage

Looking forward to the release and response to the great work and ideas in the API!

Glenn Dickins
Principal Architect of Convergence, Dolby
Honorary Professor, Australian National University
http:.//www.dickins.com

Releases for Windows are throwing errors on build 0.2.7

If you have a question, please don’t file an issue, instead, ask the Ockam team on Slack

Expected Behavior

When running the Ockam client for windows (both i386 and x64 releases), in version 0.2.7, the client should register a new DID when calling: ockam register <alias>.

Actual Behavior

The client looks to be registering ok, but the persistance back to disk shows some errors.

image

Steps to Reproduce the Problem

1. Download the 0.2.7 release for windows (x386 or x64)
2. Extract the release and run the client (ockam) from a command prompt

Environment

  • Ockam Version: 0.2.7
  • Operating System: Windows 10 (version 1809)

Add RPC Plugin Framework

We need a plugin framework that allows outside contribution while also allow us as maintainers to stay opinionated about library usage and dependency management. To this end, we should add an RPC plugin framework that would allow a developer to build an independent binary which could be placed in a well known location that would then be scanned by ockam on startup. The ockam process would start any plugin binaries in this well known location, and they would register themselves with the ockam process.

This plugin architecture should be used to allow any type of singer package to be implemented to start. The pkcs11 package should be refactored to use this framework.

Vault - Migrate tests to a unit test framework

Vault test code currently uses simple conditionals to check error state and printf to report on the state of each test case. Vault code, and the C library as a whole, should migrate to a unit test framework to simplify test cases and make it easy to expand test coverage.

Desired features:

  • Output in a format supported by Azure Pipelines (xUnit looks desirable)
  • Platform independent code/embedded friendly
  • Open-source license

CEO

If you have a question, please don’t file an issue, instead, ask the Ockam team on Slack

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

1.
2.
3.

Environment

  • Ockam Version:
  • Operating System

Vault - Support Mbed Crypto

Add support for the following functions to allow for testing without external hardware:
-Random number generation
-Key pair generation/public key retrieval (Curve25519 to start)
-ECDH
-HKDF
-AES GCM

C - fix files that don't comply with editorconfig

Multiple files in implementations/c don't comply with editorconfig

vagrant ssh builder-debian -c "npx [email protected] check implementations/c"

In #97 we'll automate this test to make it pass we likely need to ignore some folders in editorconfig

[{third-party,_build}/**]
indent_style = ignore
indent_size = ignore
end_of_line = ignore
trim_trailing_whitespace = ignore
charset = ignore

Any folders starting with . are already ignored like .build

Vault - Accept non-null pointer with 0 length for encrypt/decrypt

Expected Behavior

ockam_vault_aes_gcm_encrypt and ockam_vault_aes_gcm_decrypt should accept a non-NULL pointer to the en-/de-crypt buffer, with 0 length. As it is, the user must special-case the calls whenever a 0-length payload is submitted.

Actual Behavior

The functions fail if length is 0 but pointer is not NULL

Steps to Reproduce the Problem

Environment

  • Ockam Version:
  • Operating System:

Typos on README

Few typos on the README, e.g.,

  • Overview point 2
  • Command Line, first sentence

Expected Behavior

n/a

Actual Behavior

n/a

Steps to Reproduce the Problem

n.a

Environment

n/a

Vault - Establish common parameter checking in vault interface

Parameter checking is currently in each individual Vault. This can lead to inconsistencies across implementations. A common set of parameter checks must be established in the vault interface C file.

Questions to consider:

  • What parameters are required and what are optional
  • Are valid buffer pointers allowed with a size of 0 passed in

Vault - Improve configuration and status reporting

A Vault interface configuration structure needs to be modified to handle slot locations as slots are currently hardcoded into a Vault implementation.

Additionally, a Vault interface can currently be built to use Curve25519 or NIST P-256 but it has no way of reporting what curve it has been built for. The protocols calling into a Vault interface need to be able to determine if a Vault implementation will be able to support the communication they're handling. A Vault implementation's test cases should also use the status reporting to determine what tests to run.

goreleaser is broken

» ./build run -i goreleaser release --skip-publish --rm-dist

   • releasing using goreleaser 0.95.2...
   • could not load config, using defaults
   • RUNNING BEFORE HOOKS
   • GETTING AND VALIDATING GIT STATE
   ⨯ release failed after 0.01s error=current folder is not a git repository

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.