Jordan Rose 395e36e9f2 zkgroup: Add ExpiringProfileKeyCredential ...

Like ProfileKeyCredential, but with an expiration timestamp embedded
in it. This has its own credential type and response type, but uses
the same request type as a "classic" ProfileKeyCredential, and
generates presentations usable with AnyProfileKeyCredential-
Presentation, so that existing server code accepting presentations
will automatically do the right thing.

Adoption for servers:

- Update secret params
- When presentations are saved in group state, use 
  ProfileKeyCredentialPresentation.getStructurallyValidV1PresentationBytes()
  to maintain backwards compatibility with existing clients.
- Add an endpoint to issue ExpiringProfileKeyCredentials
- (future) Remove the endpoint that issues regular ProfileKeyCredentials

Adoption for clients, after the server has updated:

- Update public params
- Start fetching and using ExpiringProfileKeyCredentials instead of 
  regular ProfileKeyCredentials (the old endpoint will eventually
  go away)
- Node: To bring types into harmony, a receipt's expiration time has
  been changed to a `number` instead of a `bigint`

2022-06-17 13:10:10 -07:00

..

java/org/signal/libsignal

zkgroup: Add ExpiringProfileKeyCredential

2022-06-17 13:10:10 -07:00

resources/META-INF/proguard

Java: Add a ProGuard file to preserve our JNI bindings

2022-03-29 17:08:48 -07:00