Basic high level PKI is now functionally completed.
VRWorlds-CA basically seems to do what it needs to do. It creates and manages root certificates and intermediates/signer certificates and exports encrypted files which can be used by the kudo servers (security servers) for VRWorlds and encrypted backup archives to keep offsite.
Lots of testing left.
The intention was that critical info should be encrypted, and that all communications should be using SSL and I didn't want to leave that to last, so i did it first.
Now, onward to building the server side components to assimilate the data produced by the CA. Also need to work on rearchitecting the existing VRWorlds-3DOM library repository into basically a set of server common libraries, and a browser library and the beginnings of the basic scaffolds for the 4 backend server types (Kudo, World, Entity, Avatar). I already have pieces of these scattered here and there and they all need structure.
All of the server parts are .net core and the browser is whatever is needed to run in Unity.
Working on first hello-world functionality, which is to log into an Avatar and have it materialize onto a plane with various cubes and spheres in scene, whose movement are being manipulated by client-side emissary code.
VR Worlds is a concept for building, essentially, an VR/AR (XR) Operating system, which allows any number of worlds to operate together and run in modern scalable containerized servers. Anyone can field their own worlds and so make their own rules rather than some giant top down architecture.
Subscribe to:
Post Comments (Atom)
Random Thoughts, Some Progress
Lots of work at work, so not as much time for projects. Smattering of thoughts: Godot doesn't really seem ready for prime-time with c...
-
So, the original idea for the _payload directory in the Emissary was to allow the initial state of meshes and whatever other assets might be...
-
Interesting article on asymmetric cryptography... Don't Use RSA So, looks like I will be using Elliptic Curves with Curve 25519 . ...
-
So, I wasn't really thinking that the V8 environments in the browser would be truly compatible with node or chrome. That leads to issue...
No comments:
Post a Comment