Cyphrme/Coze

Issues

• Active

  #25 opened 6 months ago by mprimeaux
  5

• Duplicate JSON keys create misleading verification results in the web UI

  #26 opened 6 months ago by DavidBuchanan314
  1

• MapItem is unsafe, and MapSlice does not have a well-defined order

  #10 opened a year ago by peterbourgon
  53

• Use JSONv2 when production ready

  #15 opened a year ago by zamicol
  2

• Enforce Canonical Base 64 encoding.

  #18 opened a year ago by zamicol
  3

• Unsigned Alg and Tmb

  #24 opened 10 months ago by zamicol
  0

• Consider documenting that `rvk` denotes expiry for Coze keys.

  #21 opened 10 months ago by zamicol
  2

• implement pure python or python wrapper lib

  #22 opened 10 months ago by GonzRon
  2

• implement kyber (liboqs) ciphers for Coze

  #23 opened 10 months ago by GonzRon
  1

• Locally hosted Cyphr.me's verifier.

  #6 opened a year ago by zamicol
  0

• Further constraints on Ed25519

  #16 opened a year ago by zamicol
  0

• Think about adding "MustMarshal" and "MarshalPretty"

  #19 opened a year ago by zamicol
  0

• Base64 encoding can only elide padding when the size of encoded data is known

  #17 opened a year ago by peterbourgon
  7

• cmd

  #3 opened a year ago by zamicol
  2

• Expunge "cryptographic agility" from Coze vocabulary

  #12 opened a year ago by zamicol
  2

• Make new repositories for the specification and implementations

  #13 opened a year ago by zamicol
  0

• JSON doesn't define "integer" -- int values need to be strings

  #14 opened a year ago by peterbourgon
  11

• JSON round-trip fails for MapSlice

  #11 opened a year ago by clfs
  4

• Godoc in 1.19 does not appear to link to packages as documented.

  #7 opened a year ago by zamicol
  0

• 404 in Readme.md

  #5 opened 2 years ago by donuts-are-good
  1

• Issues

  #4 opened 2 years ago by aunzaa
  2