Authority begins... New Developments:

There is now a new subcategory of requests - the Authority requests (they contain an

<Authority>

token, have

<PlayerId>Authority</PlayerId>

and must be digitally signed by the Authority key which is embedded into the executable. Currently there is only one Authority request:
AuthPublish - authority request for a new card to be published. The publisher will, if possible honor this request and return the new card, as requested.

Also, there's a new project in OpenTCG (there's now 12 projects), the AuthorityClient. The AuthorityClient allows someone possesing the Authority Private Key (therefore me :P) to send authority commands to the services.

Implemented Today:
* Additional check in TradeRequests - check if cards are expired. [Untested]
* PublisherDB - Maintains an in-memory database of all known card-contents. They are loaded on startup by searching a given folder for xml files.
* Publisher support for AuthPublish requests. [Untested as there is yet no functional AuthorityClient]
* AuthorityClient - Startup, basic UI and Authority Key Loading (does not yet test if the key is actually an Authority key, but hey.).
* New Important Key generated and stored - the Authority Key. Can be accessed (the public one of course) as OpenTCG.Security.CommSecurity.AuthorityKey  ¶ 11:50 PM