Mathematical Mesh: Reference Implementation

This section presents the related specifications and standard, the terms that are used as terms of art within the documents and the terms used as requirements language.

This document is not normative and does not contain requirements language

The terms of art used in this document are described in the Mesh Architecture Guide .

The architecture of the Mathematical Mesh is described in the Mesh Architecture Guide . The Mesh documentation set and related specifications are described in this document.

The implementation status of the reference code base is described in the companion document .

The Mesh Reference library was developed using Visual Studio 2017 Community Edition using PHB?s Build Tools extensions. The reference code itself is currently limited to C# libraries. The code should in theory run under other operating systems but this has not been tested recently. Development under different development environments is also possible but would require re-engineering to make use of the line mode versions of the build tools.

Visual Studio 2017 Community Edition is currently available at no cost for a wide range of non-commercial development including personal use and development of Open Source software. For full details, please consult the license published by Microsoft.

Over half the code in the reference code library is generated using code generators. These are used to ensure that the specification, examples and reference code are always kept in synchronization. The build tools are published under an MIT License and are available in two forms: As stand-alone tools to be run from the command line. As a VSIX package that integrates into the Visual Studio environment. The source distribution is configured to use the tools integrated into the Visual Studio environment. If development on other platforms is desired, the simplest approach is likely to be to write a tool that reads the Visual Studio configuration files and generates the corresponding files for use with make. The VSIX package is available from the Visual Studio extensions gallery:

The source code for the build tools is available from:

The Mesh reference library source code is published under an MIT license and is available from:

To compile the code it is necessary to Create a signing key Create batch files for pre and post build tasks

The purpose of signing assemblies is so that they can be authenticated during the load process. For this to be secure, it is of course essential that each developer has their own key. To create a software developer signing key, the Visual Studio 'sn' tool is used. To run the tool, start the Visual Studio Developer Console in administrator mode. This requires the following steps: Move to a directory you want to write to. Set the machine to create user based keys Create a new key and write it to a file. Copy the file from the key to a container. Delete the container. Locate the private key file Give permission to use the key. This is of course one of the tasks we would like to automate with the Mesh tools in due course but that presents a bootstrap problem.

cd hallam]]>

sn -m N]]>

sn -k fred.snk]]>

sn -i fred.snk SigningKeyDeveloper]]>

del fred.snk]]>

]]>

Visual Studio allows projects to specify batch files to be run before and after a project build. Since the actions to be taken are likely to change from developer to developer, these are specified in separate batch files. All that is necessary to build the code without warnings is to specify a set of dummy batch files with the following names and place them somewhere in the command line $PATH environment variable. The files required are: VSPreBuild.bat VSPostBuild.bat VSPostBuildWindows.bat VSPostBuildOSX.bat VSPostBuildLinux.bat The following code will prevent error messages being thrown:

The reference code examples are designed to illustrate how the Mesh might be used in an application rather than be standalone tools in their own right. The Mesh is designed to make it each for developers to add security to their own applications rather than providing the applications themselves.

On the Windows platform, the server runs in the context of the platform Web server and must be granted permission to bind to the range of server addresses used using the netsh command. From a command prompt with administrator privileges, run the following command:

/.well-known/mmm/ \user=\]]> Where is the DNS domain name under which the service is run, is the Windows domain name of the machine and the account name. To start the service from the command line type:

]]> The server does not require administration privileges.

The profile manager wizard demonstrates functions that are performed on an administration device. These include creating a completely new profile and initial configuration of applications, connecting a device to the profile and recovery of the profile from escrow data. To run the client from the command line, place the executable image in a location that it will be found in the PATH variable and type:

The Profile connection wizard demonstrates the much more restricted functionality that would be required in a Mesh connected application and/or a profile manager for a non-administration device. To run the client from the command line, place the executable image in a location that it will be found in the PATH variable and type:

All private key data is stored using the Windows public key store. At minimum, this ensures that private keys are obfuscated and encrypted under the account password to protect the data against casual extraction attacks. On a machine with cryptographic hardware support such as a TPM or HSM, extraction of the private key may be infeasible without physical access to the machine and possibly require sophisticated diagnostic equipment.

Separate settings are used for production and test code. Test Code should use the Registry Hive: HKEY_CURRENT_USER\SOFTWARE\CryptoMesh Production code should use the hive HKEY_CURRENT_USER\SOFTWARE\MathematicalMesh In either case the sub structure is: Contains the set of Mesh Portal Accounts for the user. The default value is the account name of the default account. The Name of the each key is a portal account name and the value a REG_SZ entry containing the UDF of the profile master key. Contains the set of Mesh Profiles for the user. The default value is the UDF of the default profile master key. The Name of each key is the UDF of the master key and the value a REG_SZ entry containing the file location of the cached copy of the personal profile. Contains the set of Device profiles in the same format as the PersonalProfiles.

The profile data itself is stored in data files at the location specified in the registry. The files are standard XML files in UTF8 encoding.

[[Not yet implemented, subject to change.] All configuration information is stored in the user directory ~/.mmm Keys are stored in SSH key file format using the customary name and extension conventions for that application.

The application ExampleGenerator shows the use of the Mesh in an application using the convenience API. It is the application program used to generate the examples in the reference document. ExampleGenerator implements a client that connects to a remote Web Service, creates new personal profile with an escrow entry with offline recovery codes, attaches applications and other devices, updates an application profile, deletes all the profile data from the local machine and then restores them using the recovery codes and escrow entry.

The libraries are designed to support testing and development use. For this reason, the client side of the libraries is divided into the following main classes: Provides a logical connection to a remote or simulated Mesh service. Provides the interface to a Mesh service which may be an actual remote service accessed via a network connection, or local code running in the same process as the client to simulate a Mesh service for testing purposes. Provides an interface to Mesh data stored on the local machine. Provide the high level application interface to the Mesh combining access through the MeshClient and MeshMachine. The relationship between these parts is shown in . The application programmer will typically need only the MeshSession class. The principal classes in the Mesh Client side API. This division makes it possible to test Mesh clients and server implementations in a single process with a single debugger which is usually more convenient than spinning up a separate development session for the client and service.

Most Mesh operations are performed within the context of a specific PersonalProfile registered on the current machine. This context is provided by an instance of the PersonalSession class. An instance of the MeshSession class is used for operations that are not bound to a specific PersonalProfile registered on the machine. These operations are: Binding a new PersonalProfile to the machine. Offline key recovery. Requesting and completing a device connection request from the new device. Acquiring a PersonalSession instance.

The primary interface for the application programmer is the MeshSession class. To create a mesh session class, the following steps are required: Initialize the Mesh code for the intended platform Request a new MeshSession instance. Although C# code is nominally 'write once, run anywhere', this approach does not ensure use of platform specific features such as the Windows registry or protected storage for cryptographic keys. Calling MeshWindows.Initialize() causes the platform specific code for the Windows to be initialized in production mode. Alternatively, calls to MeshLinux.Initialize() or MeshOSX.Initialize() causes the platform specific code for those platforms to be initialized. The code to initialize a production instance of the code is shown in :

If the user has already created a PersonalProfile and connected it to the machine, it will automatically be read from local storage. The instance will automatically create MeshClient instances as required to establish a web service using the default transport (HTTP) to the service as necessary (see ). Connecting to a remote service from a Windows platform. The server implementation is managed in the same fashion. Internally, the MeshService and MeshClient classes are both descended from the same parent.

Since the purpose of the ExampleGenerator is to create examples for the documentation, it is not necessary for the JSON Remote Procedure Calls to actually be ?Remote?. Instead the ?Local? Procedure Call mode is used in which the client and server both run in the same process with the client API invoking the server dispatch methods through an interface that performs JSON serialization and deserialization but does not invoke the network transport. Connecting to a direct service for testing. A direct connection to the service provider may be established by either specifying the portal to use in the initialization of MeshSession or by setting the default portal property of the MeshPortal class as is done here .

This time, we initialize a specific version of the platform dependent code and specify that it is to be initialized as test code rather than production. This will cause all persistent data stored on the machine (keys, profiles) to be stored in locations marked as test locations. The EraseTest() method causes all data stored in test locations to be erased from the machine, thus ensuring that the test begins from a known state with no results from previous runs. When writing test code, it is frequently useful to create multiple independent MeshSessions to simulate multiple machines. To prevent data written to one machine interfering with another, a new simulated machine is created for each session using the MeshMachineCached class

The user experience is improved if the application indicates whether their choice of portal account name is acceptable or not while they are entering it. The Validate method allows the user's choice of account name to be validated .

The portal address is given in the usual username@domain format, for example alice@example.com.

Creating a PersonalProfile has two steps: Create a DeviceProfile (if necessary) Create the PersonalProfile Create an account bound to the profile at the portal. These steps are shown in .

The application could have overridden the default values of DeviceID and DeviceDescription when creating the device.

Having created a potentially valuable profile, we probably want to back it up. To do this, we create an instance of the OfflineEscrowEntry class with the desired quorum and number of shares (2 out of 4) .

We can test our escrow parameters by deleting the profile from the current machine using the Delete method .

Profile recovery has two steps: Reconstruct the shared secret from the recovery shares. Recover the profile. In this case our recovery shares are the first and the third key shares we just generated. The Recover method recovers the profile and rebinds it to the existing portal .

Device connection involves two devices, the device to be connected and the device used to approve the request. The new device: Create a device profile for the new device. Request connection to the new device Wait for the result. These calls are shown .

In a real example, we would want to show the connection authentication code to the user so that they can verify that they are responding to the right request on the approval device. On the approval device, the application Requests a list of pending requests using ConnectPending. Accepts or Rejects devices using ConnectClose.

Application profiles are created in the same manner as personal profiles .

Changes to the Application Profile are written to the RegistrationApplication instance and then committed using the Update() method.

If you are building Mesh applications in another language, the least effort approach may be to rewrite the PROTOGEN build tool to target your language. Protogen does support generation of C header files that may be used to drive a parser. If however you are adding Mesh support for an application that already uses JSON based protocols, you might want to edit the generator scripting files to generate code for your existing libraries.

A lightweight API providing the minimal features required to Mesh enable an application is required. Such an API should exclude most account management features: Creating new Personal Profiles and portal accounts. Key escrow, recovery List, accept pending device connection requests This leaves the following features: Create Device Profile Request device connection Get Personal Profile Get, Update, Application Profile In addition to providing less functionality, an implementation of the lightweight binding is likely to be written in a 'flattened' style rather than the abstracted, object oriented approach of the reference code.

This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Organization: Comodo Group Inc. Implementer: Phillip Hallam-Baker Maturity: Experimental Prototype This implementation was used to produce the reference section and all the examples in this document. Since the conversion of specification to code is automatic, there is a high degree of assurance that the reference implementation is consistent with this document.

The draft-xx branch describes the code used to create version xx of this document. The main current limitations are that the code only supports RSA key pairs and for ease of development the server does not persist keys across sessions. Nor does the implementation currently support the HTTP payload authentication and encryption layer or make use of TLS. These could be easily fixed. The client and server are implemented as libraries that may be called from a multi-protocol server. A standalone server will be provided in a future release. Only the JSON encoding is currently implemented. The JSON-B, JSON-C, ASN.1 and TLS Schema implementations are all supported by the code generation tool but not currently implemented as the build tool bindings for those encodings have not yet been finalized or documented. The key restrictions for TLS key exchange have not yet been implemented. The code has only been tested on Windows 10 but passed compatibility testing for both Mono and dotNetCore 2.0 run times which should in theory permit use on Linux and OSX platforms.

The code is released under an MIT License Source code is available from GitHub at https://github.com/hallambaker/Mathematical-Mesh

The implementation and specification documentation were developed in Visual Studio using the PHB Build Tools suite.

Contact Phillip Hallam-Baker phill@hallambaker.com

Security Considerations are addressed in the companion document

This document specifies no actions for IANA

Comodo Group: Egemen Tas, Melhi Abdulhayo?lu, Rob Stradling, Robin Alden.