GitLab

The URL to the server to which issuance records and revocation commands are sent now no longer needs to be put in the scheme, and may thus be kept private to the issuer. Instead multiple URLs are now in the scheme, which are only required to host revocation records for irmaclients and requestors to update their revocation state.

feat: switch to SQL revocation database for revocation server, and to simple in-memory database for requestors

Requestors only need to be aware of the last x revocation records and none of the other record types.

Addionally:
- pass revocation configuration into RevocationStorage
- refactor irma.NewConfiguration functions to use options struct
- split RevocationStorage helper functions into separate structs
- add credentialtype to revocation record wrapper in irmago

feat: support revocation sessions in IRMA server, and move revocation code from irmaconfig.go to its own file

feat: rename --authmethod to --auth-method flag to irma session for consistency with Configuration struct

- emit version number when running `irma` without subcommand
- `irma session` example uses default `irma server` port

Closes #44

When passing --server to irma session, it would erroneously complain about
--url also being set.

fix: both irmaserver and irmaclient now early reject session requests referring nonexisting identifiers

feat: Breaking change: support conjunctions of disjunctions of conjunctions when requesting attributes in any of the three supported session types

Instead of requesting several attributes, one can now request several groups of attributes. Within each such group, attributes belonging to the same credential type always come from the same credential instance. This affects all three session types, as in each of them attributes can be disclosed.

feat: Support --url for session. Some code duplication was unavoidable without splitting up requestorserver.initialize

Verifying an individual scheme no emits the same warnings and errors as verifying multiple schemes.

Resolves #28
Resolves #29
Resolves #30
Co-authored-by: Confiks <confiks@scriptbase.org>