Here's an example of using some code I've been playing around with lately.

https://www.youtube.com/watch?v=h_ycJAASZmw

The basic idea is to use MimeKit at the core, for creating cryptographically signed PGP MME envelopes, and encrypt them, to establish trust and privacy between the client and the server, such that the client can supply the actual code to execute in the web service, allowing for basically having one web service endpoint, solving "everything".

In addition to the PGP parts, this also have lots of other advantages, such as compressing the request and response (since PGP also compresses its PGP messages), and sending multiple files in one HTTP request (MIME supports "multiparts"), allowing for the client's code to reference files in the MIME request, and also itself decide which files to return from server (assuming it's authorized to read the files).

Basically, a secure implementation for letting the client supply the code that the web service endpoint executes ...

Thoughts ...?

Q; Security concerns I should think of before releasing this...?