[openpgp] Weekly github digest (OpenPGP Github Activity Summ ary)

Repository Activity Summary Bot <[email protected]>
Newsgroups gmane.ietf.openpgp
Message-ID <[email protected]>


Events without label "editorial"

Issues
------
* openpgp-pqc/draft-openpgp-pqc (+11/-0/💬2)
  11 issues created:
  - Identify signature types (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/206 
  - names of SLH functions (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/202 
  - signature context parameters (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/201 
  - normalize order of arguments `EdDSA.Verify` and `ML-DSA.Verify` (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/200 
  - is it "EC" or "ECC"? (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/199 
  - Align digest algorithm constraints: "Key Binding Signatures" and "Minimum Digest Size for PQ(/T) Signatures" (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/198 
  - Trim `mlkem-ops` section (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/194 
  - why do the ECDH and EdDSA tables need the "Field size" property? (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/193 
  - Normalize KEM artifact tables (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/192 
  - What is the difference between `X25519-KEM` and `x25519kem` and `x25519Kem`? (likewise for x448) (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/191 
  - Why does `ECDH-KEM.Decaps()` take an `ecdhPublicKey` as a parameter? (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/190 

  2 issues received 2 new comments:
  - #201 signature context parameters (1 by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/201 
  - #45 PKESK wire format concern (1 by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/issues/45 



Pull requests
-------------
* openpgp-pqc/draft-openpgp-pqc (+7/-1/💬9)
  7 pull requests submitted:
  - Correct octet lengths in the IANA table (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/205 
  - Normalize text in Key Generation Procedure sections (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/204 
  - Add sub-section headers for key material formats (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/203 
  - Cleanup ecdhPublicKey in ECDH-KEM.Decaps() (by fluppe2)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/197 
  - Unified terminology: X25519-KEM and X448-KEM (by fluppe2)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/196 
  - KEK combiner takes ECDH pubkey and ciphertext as input (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/195 
  - Fix some nits (by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/189 

  4 pull requests received 9 new comments:
  - #205 Correct octet lengths in the IANA table (1 by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/205 
  - #196 Unified terminology: X25519-KEM and X448-KEM (3 by dkg, fluppe2)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/196 
  - #189 Fix some nits (3 by dkg)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/189 
  - #188 Specify minimum requirements for signature digest sizes (2 by TJ-91, wussler)
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/188 

  1 pull requests merged:
  - Specify minimum requirements for signature digest sizes
    https://github.com/openpgp-pqc/draft-openpgp-pqc/pull/188 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/openpgp-pqc/draft-openpgp-pqc


-- 
To have a summary like this sent to your list, see: https://github.com/ietf-github-services/activity-summary

_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.