Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

JWE implementation that is separate from DIDComm and crypto-implementation agnostic #1409

Closed
DRK3 opened this issue Mar 3, 2020 · 0 comments · Fixed by #1479
Closed

JWE implementation that is separate from DIDComm and crypto-implementation agnostic #1409

DRK3 opened this issue Mar 3, 2020 · 0 comments · Fixed by #1479
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@DRK3
Copy link
Contributor

DRK3 commented Mar 3, 2020

Make it possible for another project to import a JWE package independent of DIDComm. The other project would then be able to decide what package it will use to build the envelope.

@fqutishat fqutishat added the enhancement New feature or request label Mar 3, 2020
@fqutishat fqutishat added this to the 0.1.3 milestone Mar 3, 2020
@DRK3 DRK3 changed the title Refactor JWE to be seperate from Didcomm and crypto libraries Refactor JWE to be separate from Didcomm Mar 10, 2020
@DRK3 DRK3 changed the title Refactor JWE to be separate from Didcomm Refactor JWE to be separate from DIDComm Mar 10, 2020
@DRK3 DRK3 changed the title Refactor JWE to be separate from DIDComm Refactor JWE to be separate from DIDComm and crypto-implementation agnostic Mar 10, 2020
@DRK3 DRK3 changed the title Refactor JWE to be separate from DIDComm and crypto-implementation agnostic JWE implementation that is separate from DIDComm and crypto-implementation agnostic Mar 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

Successfully merging a pull request may close this issue.

2 participants