<<^>> SynchroKnot: Beyond Light Years.

Transform any server, workstation, desktop or embedded device

into a decentralized cloud or data center [data decenter]

in minutes with SynchroKnot Software.

- Complete Alternative for VMware, OpenStack, Hyper-V, Routers, Switches & Storage [SAN/NAS] -

Transforming traditional Cloud and Data Center to Data Decenter
with ONE server, workstation, desktop or embedded device.

Connect each server/workstation/desktop/embedded device DIRECTLY TO EACH-OTHER.

█║▌║▌║ Data Center & Cloud Computing Today - VS - SynchroKnot ║█

█║ Data Center & Cloud Computing Today

├──> Must Purchase Disparate Hardware - servers, redundant switches & routers, storage [SAN/NAS] and load balancers.
├──> Must Purchase Virtualization Software + Licenses - VMware, OpenStack, Hyper-V, RHEV, Xen, VDI etc.
├──> Must Purchase Storage Software + Licenses.
├──> Must Purchase Licenses for Switches, Routers & Load Balancers [above and beyond the hardware].
├──> Must Manage Separate Hardware & Software Through Different Management Panels, User Interfaces and APIs.
├──> Must Maintain Separate Multi-Tiered Teams and Departments To Manage Complex Operations.
└──> Must Have A Large Space To House Expensive Hardware With High-Cost Real Estate & Cooling.

█║ SynchroKnot Advantage: Decentralized Data Center and Cloud Computing

├──> SynchroKnot Software Does Everything.
├──> No Separate Hardware Needed - Use Any Commodity X86_64 Desktop/Workstation/Server/Embedded Device and Connect Them To Eachother.
├──> No Need To Purchase Physical OR Virtual Switches and Routers OR Any Of Their Licenses [Eg. Cisco, Juniper etc].
├──> No Need To Purchase SAN/NAS/Distributed Block & File Storage [Eg. Netapp, EMC, Gluster, Ceph etc].
├──> No Separate Teams And Departments Needed.
├──> No Large Space Needed. SynchroKnot Setup Is Very Flexible. You Can Utilize Cubicles, Offices, Apartments, Basements, Fibre Optic Hubs etc.
├──> Transparently Scale and De-Scale [locally/globally] Your SynchroKnot Infrastructure On-Demand Without Disruption/Interruption.
└──> Be Your Own Cloud Provider. Sell Full or Under-Utilized Hardware Resources With Bitcoin Internally/Externally [New Feature Coming Soon].

█║ SynchroKnot: Economic Advantages

├──> Exponential Reduction In Total Cost.
├──> Exponential Reduction In Complexity.
├──> Exponential Reduction In Manpower.
├──> Exponential Increase In Performance.
├──> Exponential Increase In Security.
├──> Exponential Increase In Scalability & Over-all Control & Responsiveness.
├──> Eliminate All Vendor and Multi-Vendor Lock-ins, Interdependencies & Traps.
├──> Comprises 10+ Year Production Seasoned Open-Source Components.
└──> Significantly Increase Your Organization's Micro and Macro Economic Dynamics and Manpower Efficiency.

█║▌║▌║ SYNCHROKNOT: About ║█

SynchroKnot is the Originator & Leader of Converged Unification and Decentralization of the Cloud and Data Center Infrastructure and Manpower with its combined software, technology, architecture and methodology.

SynchroKnot is a distributed and decentralized organization with global jurisdiction via blockchain. The member[s] of SynchroKnot Spatial Systems Engineering are generally known to be dispersed across Spain, Russia, China and Japan with a growing community of intellectuals.

SynchroKnot copyrights and intellectual property are fully and solely owned across the global jurisdiction by its creator Mehul Sharma @ IEEE.

Join, Learn and Interact with SynchroKnot Spatial Systems Engineering on IEEE Workspace: Cloud Computing Decentralization by making a request from your IEEE account.

- Live Happy With SynchroKnot -

■ *Note: Due to continuous harassment of our engineers we have permanently blacklisted the region of North America [United States & Canada], United Kingdom and Ireland. Alongside, we will not be able to initially serve regions such as India. Feel free to check back for updates.

▌█ License




▌█ Generic Guide to Hardware Selection, Consulting and Pricing

▌█ Bug Fixes

▌█ Encryption - Micro How-to

█║▌║▌║ SYNCHROKNOT: Interact ║█

█║  Interact with SynchroKnot Spatial Systems Engineering  ║█
├── █║ EMAIL /
│   │
│   ├──  i n f o  | a-t | synchroknot |d0t| ch 
│   │
│   └──  i n f o  | a-t | synchroknot |d0t| in 
├── █║ SynchroKnot Public Key [x509 certificate - SMIME] /
│   │
│   └──   >> SynchroKnot Public Key to Encrypt Email/Communication if needed. << 

├── █║ Join, Learn and Interact with SynchroKnot Spatial Systems Engineering on IEEE Workspace: Cloud Computing Decentralization by making a request from your IEEE account.

█║▌║▌║ SYNCHROKNOT: Purchase Software Product Licenses ║█


■ Single Base License for upto 64 cores/threads :
[Status Update Coming Soon]

■ Purchase via Email [see "Contact" above] with:

Company ID:[your registered Company ID]

Base-License:[number of license[s] needed]

■ Pay to the Bitcoin Address provided in the confirmation reply.

■ Upon payment confirmation reply back with your public key [x509 certificate].

■ You will receive the license[s] and software.

■ Decrypt and use it. Simple as that!

Eg. openssl smime -decrypt -binary -in sknt.enc -out sknt -inkey privatekey.pem


▌ Send the details below from your Business Email. That's it!

▌ Email subject: Company ID.

1] Company Name:[Name of your Company]

2] State/Province:[Name of the State/Province of your Company]

3] Country:[Country where your Company is located]

You should receive your Company ID within 24 hours.

*Regions Served : All regions.

█║▌║▌║ SYNCHROKNOT: Software Product Features ║█

█║▌ Simple & Quick Installation On Any x86_64 Hardware With Debian 9 [Stretch].

▌ Each feature has a type [ Type : Built-in or Type : Power Module ].

▌ Type : Built-in is included in the base license.

▌ Type : Power Module is an additional module at an additional cost and is not included in the base license.

█║ SynchroKnot Infrastructure Engine - Enlivening the Heart of Enterprise 4.0/

█║ Spatial Virtual Infrastructure - High-Performance Desktop and Server Virtual Machines/

█║ Spatial Network Infrastructure/

█║ Spatial Security Infrastructure/

█║ Spatial Storage Infrastructure/

█║▌║▌║ SYNCHROKNOT: Demonstration and Instructional Media ║█

While the demonstration and instructional media gives a feel and insight of the flexibility and workability of different aspects of SynchroKnot, the only way to get a practical and theoretical understanding is to try and practice different case scenarios hands-on!

Note that most of the media seen here pertains to the older non-commercial version of SynchroKnot. We have received exhilarating and positive feedback about the ambiance and workability of the new SynchroKnot software [currently undepicted in the demonstration videos].

Be sure to read through the Documentation.

█║ SynchroKnot Decentralized Blockchain Identity Management

■ Demonstrates an authorized user logging into the Spatial Cluster on a Spatial Fabric Array. [This demonstration does not use level 2 security via Active Directory / LDAP].
■ The user's Blockchain Private Key is only used to sign a Spatial Nonce Fingerprint [invisible to the user] in the browser and not sent to the server.
■ On successful authentication the user is immediately taken to the SynchroKnot Infrastructure Engine.

█║ SynchroKnot Level 2 Security - Decentralized Blockchain Identity Management + Active Directory / LDAP

■ Demonstrates an authorized user logging into the Spatial Cluster on a Spatial Fabric Array with Level 2 Security enabled. The new commercial version of SynchroKnot software is depicted.
■ For the purpose of demonstration, the user first logs in without the password and is prompted to enter the password as Level 2 Security is enabled. Then the user enters a wrong password which is rejected by the designated Active Directory / LDAP server(s). On the third attempt the user succesfully logs into the SynchroKnot Infrastructure Engine.
■ In this demonstration, for the purposes of testing, the Level 2 Security Power Module tries to authenticate against the first 3 LDAP servers designated to the user and fails, and then successfully authenticates the user against the 4th LDAP server. Speed is clearly visible, in spite of multiple, complex security and cryptographic operations being performed by SynchroKnot.

█║ Decentralized Virtual Machines : Multifarious ways to Create

■ Auto Create a Virtual Machine from a Spacesuit [ template ] -- uses Decentralized Resource Radar.
■ Auto Create a Virtual Machine from a Spacesuit on a Spatial Fabric Array with high or low performance -- uses Decentralized Resource Radar.
■ Auto Create a Virtual Machine from a Spacesuit on a Spatial Fabric Array from a refined group using Microcosm / Macrocosm / Intercosm or their combination. Further automatically choose a Spatial Fabric Array with high or low performance -- uses Decentralized Resource Radar.
■ Manually Create Virtual Machine from Spacesuit on a Spatial Fabric Array.
■ Auto Create Virtual Machine from an existing Virtual Machine -- uses Decentralized Resource Radar.
■ Manually Create Virtual Machine from an existing Virtual Machine on a specific Spatial Fabric Array.
■ Auto Create a Spacesuit from an existing Virtual Machine -- uses Decentralized Resource Radar.
■ Manually Create a Spacesuit from an existing Virtual Machine on a specific Spatial Fabric Array.
■ Create from Spacesuits or Virtual Machines while they are running [ switched on ] without disruption.

█║ Virtual Machine : Real-time Information, Monitoring & Statistics and Web Console

█║ Decentralized Automatic and Manual Virtual Machine Relocation

■ Auto Relocate virtual machines with their storage without knowing where the virtual machine you intend to relocate resides on the Spatial Cluster and without knowing who the receiver will be. Further, the receiver does not know who the sender will be. Just the name with the relocate command or click of the Auto Relocate button. Everything is auto ascertained and executed by the decentralized resource radar, without reading a central or distributed database or resource.
■ Manually relocate to a specific Spatial Fabric Array by simply giving its IP address.
■ Auto relocate also possible [ not shown in the video ] to a refined group of Spatial Fabric Arrays with the help of Microcosm, Macrocosm and Intercosm [ individually or their combination ].
■ Auto relocate also possible [ not shown in the video ] to high or low performance Spatial Fabric Arrays by simply adding performance:[high / low]. Further, use it with Microcosm, Macrocosm and Intercosm [ individually or their combination ].

█║ Decentralized Virtual Machine Operations - Start, Stop, Unplug, Pause, Unpause, Delete .....

■ All virtual machine operations can be performed with a click of a button or with the use of intelligent auto-fill triggers.

■ When using the intelligent auto-fill triggers there is no need to give the lastname [ ie Blockchain ID ] of the virtual machine. Only in certain cases the lastname is required due to the decentralized nature of the technology, and in most of those cases there are mechanisms in the infrastructure engine where one can append the virtual machine lastname to different keys with just a click of a button, resulting in operational ease and speed!

█║ Virtual Machine Replica - Writable Snapshots that don't relocate with the virtual machines, reducing the burden of tugging along snapshots, yet still available to be reverted to the original or created into new virtual machines.

█║ Spatial Satellite Tree Protocol - One of the many SynchroKnot components enabling an industry-wide global paradigm shift.

Part 1 : Shows a total of 24 nodes in one large loop [ Ring Topology ] with Spatial Satellite Tree Protocol enabled and multiple switches being brought down and up every 10 seconds. Mininet is used for this demonstration. One can observe the results of the pings etc.

In actual use case scenarios, with our unique cabling technique in a 5 X 5 2-D Torus topology, one may generally not have more than one hop! 24 nodes are used for purposes of extreme testing in difficult case scenarios [ sometimes not siding with the logical mind ].

■ In the video, an older script [ring-topologyx16-test] was used to bring switches down and up, but while recording this demo the number of total nodes were increased to 24 impromptu for fun to increase the level of difficulty. In this demo, the root bridge is auto selected and is not s16. In the next demo we will manually make s16 the root bridge and fail it.

■ Simple machine with 2 cores [4 threads] Intel Core i7-6500U Processor with 8 GB RAM. Alongside, a few running virtual machines not a part of this demo were used in the background to consume CPU and memory resources, leaving fewer CPU cycles and memory for Satellite Tree Protocol and the 24 nodes with Mininet. [This demonstration video was also recorded on the same machine and thus used additional CPU cycles and memory.]

■ Side Note : Spanning Tree Protocol and Rapid Spanning Tree Protocol generally respond to failures by recovering in about 40 to 300 seconds or more depending upon the timers and topology [ RSTP may recover faster by just a few seconds ]. This is with the regular vendor / standards suggested timers found in most switches in standard setups today. One can increase the network diameter [ i.e number of switches between two endpoints ] to a maximum of about 18. This however will substantially increase the recovery time, alongside most likely put the timers of switches out of sync. Your mileage may vary. Do your own research.

Caution : If you try a similar setup with standard physical Ethernet switches [Cisco, Juniper etc] then you are solely responsible if you brick your appliance(es).

█║ Spatial Satellite Tree Protocol - Root Bridge Failure, Failover and Failback.

■ Part 2 : Continuation of Part 1. Shows Satellite Tree Protocol - Root Bridge Failure, Failover and Failback and multiple switches being brought down and up every 10 seconds.
■ In this demo, the root bridge is manually set to s16 and then brought down first! More details in the video.

█║ Spatial Satellite Tree Protocol - Root Bridge Failure, Failover and Failback with FLOOD PING!

■ Part 3 : Continuation of Part 2. Shows Satellite Tree Protocol - Root Bridge Failure, Failover and Failback and multiple switches being brought down and up every 10 seconds with FLOOD PING instead of ping. Same set up as above with a total of 24 nodes in one large loop [ Ring Topology ] and simple hardware with 2 cores - 4 threads Intel Core i7-6500U Processor with 8 GB RAM.

Note: You may also notice results of prior flood ping tests before the current one gets underway. We would like to assume that 0% packet loss with 24 switches is a bit much for our logical mind to digest and would love to blame the ping utility with a faulty flood ping option :) ..... of course with double/triple/quadruple shots of your favorite beverage [Eg. coffee, lemonade etc] you may develop an insight that differs.

■ Exercise the same caution as mentioned above.

█║ Disperser - Load Balancer - Create, Enable, Disable and Remove.

■ Basic operations with private IP addresses depicted [ add a public IP address if needed ].

■ Demo showing TCP and UDP auto load balancing with no separate configuration for TCP or UDP ports. Sending traffic to the front-end Disperser IP address load balances to its respective port on the back-end.

█║ Virtual Machine Modification - Multiple Multi-Order Edits to Multiple Components and Services Seamlessly All in a Single Line.

■ This demo shows a simple form of multiple edits [ which can be in any order ] all on one line being performed by the Intelligent Modification Logic & Engine in the background to the virtual machine's Spacesuit. The configuration and sub-configurations of components and services are handled transparently. This video shows an example where the Space Buoy configuration and service is automatically modified and brought up along with the other modifications after checking against conflicts, among other things.

■ The second video shows using the web console of the virtual machine [ Linux - Openwrt ] and restarting the network to see if the IP address and the default Gateway IP address that was just invoked via the Space Buoy is assigned correctly.

█║ Excerpts - Decentralized Realtime Precision Parallel Search with the Parallel Regex Engine

■ This simple demo shows a precision parallel search for virtual machines individually and in combination with Microcosm, Macrocosm and Intercosm for geographical location specificity. Extreme fine-grained searches are possible in real-time. Decentralized responses are not generated by reading in-memory databases or caching, but rather computed when requested!!!

[ This section will be updated with more videos demonstrating advanced fine-grained searches emulated across globally dispersed Spatial Fabric Arrays. ]

Below are the triggers used with Excerpts in the demo video:

trigger:excerpts intercosm: macrocosm: microcosm: spatial-fabric-array: synchroknot:*
trigger:excerpts intercosm: macrocosm: microcosm: spatial-fabric-array: synchroknot:apache
trigger:excerpts intercosm: macrocosm: microcosm: spatial-fabric-array: synchroknot:nginx
trigger:excerpts intercosm: macrocosm: microcosm: spatial-fabric-array: synchroknot:apache,nginx
trigger:excerpts intercosm: macrocosm:boston microcosm:row10,rack1 spatial-fabric-array: synchroknot:apache,nginx
trigger:excerpts intercosm:washington-dc macrocosm:ashburn microcosm:rack9 spatial-fabric-array: synchroknot:apache,nginx

█║ Realtime Logs with Log Panorama and Spatial Fabric Array Information

■ List of Spatial Fabric Arrays and their concise information.

■ Logs of different operations performed by users in realtime

■ Searching of keywords in the received logs.

█║ Space Buoy - Decentralized DHCP : Secure Dynamic Static IP, Netmask, Broadcast, Gateway, DNS, MTU and much more.

This demo shows the Space Buoy in action which comes with the new commercial version of SynchroKnot. Without touching the virtual machine one can assign ANY Name, IP Address [Public/Private IPv4 IP Address], Netmask, Broadcast, Default Gateway, MTU [Maximum Transfer Unit], NTP, DNS, Domain Name, Domain Search, Log Server, NETBIOS [Name Servers, Datagram Distribution and Node-Type], SMTP server, POP3 server, plus also, Enable IP Forwarding, Set TCP Keepalive, Set Multiple Classless Static Routes and more.

█║ Space Buoy - Decentralized DHCP : Setting Private and Public Dynamic Static IPs with different Netmask, Broadcast and Gateway.

This demo shows the Space Buoy being used on a Spatial Fabric Satellite with fairly low resources [cpu and memory] with the object being to see how the DHCP client inside the virtual machine with 512M of memory is able to succesfully sustain the changes to different public and private IP addresses with varying netmasks and broadcasts. [The private & public IP addresses shown in the video are randomly selected for testing.]

Note : Those familiar with the DHCP server and client functionality might have noticed that no specific private or public IP address is assigned to the DHCP server in the demo! [nor has it been assigned previously]. This feature saves IP addresses and configuration & maintenance hassles.

█║ Space Buoy and DHCPCAST : Secure Dynamic Static IP with Decentralized DHCP and IP address from specific DHCP Server

This demo shows the following:

■ setting of a dynamic static IP address and default gateway IP address via the Space Buoy, and then checking and confirming it using the virtual machine's web console.

■ pointing the virtual machine's network interface to a specific DHCP server by its MAC address, and then checking and confirming via the web console if the virtual machine received its IP address and default gateway IP address from that DHCP server.

█║ FASTR : Intelligent Fast Asynchronous Triggered Replication of Virtual Machines

This demo shows how simple it is to setup FASTR, and how fast it actually is. Especially considering that it even detects and triggers intelligently on just a few bytes being written to the filesystem inside the virtual machine!!!!

The video shows the following:

■ Enabling and starting FASTR for a virtual machine called app-containers [ running different containers like LXC, Docker, Kubernetes etc ]. app-containers resides on Spatial Fabric Array and is replicating to app-containers-fastr on Spatial Fabric Array on another machine connected via Gigabit Ethernet on VLAN 9.

■ Logging into app-containers via the web console and writing to the filesystem by echoing simple text to a file and doing a sync.

■ Running the fastr-checksum script immediately after doing a filesystem sync inside the virtual machine. The fastr-checksum script does an shasum on app-containers virtual disk locally, and pulls the shasum of the virtual disk of app-containers-fastr from

■ Observing if the checksums match. This proves that the changes are being replicated correctly onto the remote side, and everything is perfectly in sync.

█║ Spatial Fabric Satellite Setup and Invoke

This demonstration shows how to set up and invoke the Spatial Fabric Satellite on any commodity x86_64 hardware with Debian 9.

█║ Create Spatial Cluster for Tenants with Multiple Stacked Vlans

Demonstrating creation of a Spatial Cluster for tenants on a Spatial Fabric Satellite with Multiple Stacked Vlans [Single Vlan 1000, Double Stacked Vlan 1000.1000 and Triple Stacked Vlan 1000.1000.1000]. Additional information not a part of the video : The tenants are identified with their Blockchain ID [and confirmed with their signature] for global decentralized multi-service provider deployment, access, connectivity and VPN, among a whole lot of other aspects.

█║ Start Spatial Cluster

Start the previously created Spatial Cluster.

█║ Set up Spatial Fabric Satellite - Create and Start Spatial Cluster - Unabridged

Unabridged. All in one flow for fun.

Setting up a Spatial Fabric Satellite and creating a Spatial Cluster is a one time task. Spatial Cluster is started once after the operating system boots.

█║ Android Desktop as Virtual Desktop Infrastructure [VDI]

Fun with Android Desktop acting as VDI. Good performance with no special adjustments to the web console! [leaving enough room for the performance to be further improved]. Both touch screen and mouse from the track pad were used [though one can't tell the difference in the video]. Reduce your VDI costs [as it is free]. Benefit from the built-in terminal, VPN and numerous apps. This is just a basic demo to get one started. [Keep in mind that this video was recorded with average frame rate quality].

█║ Automatic Distance Vectoring with Spatial Fabric Arrays + SynchroKnot User Information Display

The new version of SynchroKnot comes with built-in automatic distance vectoring for auto adjustment of local and global latencies experienced when the Spatial Fabric Arrays communicate over variable distances. These latencies are mainly caused by long distance links and the load [available CPU cycles] on the destination Spatial Fabric Satellite(s).

This demonstration shows the speed-up achieved on the SynchroKnot Infrastructure Engine Web Interface by reducing the internal distance vector time of the Spatial Fabric Array by the tenant. Every tenant of every Spatial Fabric Satellite can adjust their distance vector semantics. It is recommended not to adjust this value unless you know exactly what you are doing. Also featured is a peek into the SynchroKnot [user] information, which may not have been shown in other videos.


This impromptu Arpless Interstellar power module demonstration shows 2 virtual machines named webserver [w] and deb [d] in interstellar dac0001 enabled with Arpless This means, in addition to being protected by Arpless, they are already protected by Interstellar at two separate levels of security enabled at layer 2, namely mac address spoofing protection and communication protection, only allowing interaction between virtual machines with their matching interstellar id(s), interstellar resonance id(s) and interstellar oui(s).

In this demo, traffic from W is specifically heading to with mac address da:c0:00:11:ee:ee. D is compromised and is used to divert traffic that is heading to with mac address da:c0:00:11:ee:ee on to itself using various methods. In real world scenarios, could be anything like a gateway, router, load balancer, webserver, database, ldap/active directory, network/distributed filesystem server, email server, voip server etc.

The result is that all the attempts are unsuccessful. Neither does W's ARP cache change nor does its traffic get diverted to D.

Further, as a last resort, the user gets into W and succesfully poisons the arp cache of W to point to D. The result is that traffic diversion is unsuccessful. Also, the ability to reach D directly from within W is unsuccessful!!!!

Keep in mind, this demonstration assumes one has basic to advanced hands-on knowledge of network and operating system security and packet wrangling. The point of this demonstration is to show one the most vulnerable actual use case scenarios, and not pseudo arp cache poisoning like shown in the following next demo where all machines within a network that can communicate with eachother without Arpless Interstellar, and poisoning the arp cache, simply diverts the traffic from one to the other. The next demo also confirms that there is no bug in the operating system that prevents the traffic from being diverted when its arp cache is poisoned [tested on debian 9 - stretch]. This means that the traffic would have been easily diverted without Arpless Interstellar.

Breakdown of the highlights of the demonstration video:

1) In W check for arp entries, and then ping which is turned off. Arpless responds with the mac address. Arpless would have also replied even if was turned on. For the purposes of the demo it is easier and clearer to show the Arpless functionality.

2) ping W to D and D to W to check the connectivity and arp cache.

3) Check if mac address spoofing is working. Ping from D to W. Change the mac address on W and then ping D and see if the pings are still working. Change back to the original mac address of W and check ping. This shows the mac address spoofing protection via the interstellar is enabled on both W and D [though we did not repeat the same steps for D in this demo].

4) On D, change IP address to while keeping its original mac address. Ping from both sides and check their arp caches. Notice in the demo, that there was no arp entry for which was likely flushed, due to the back and forth changing of mac addresses, but when W pings it only hears back da:c0:00:11:ee:ee and not the mac address of D.

5) Since the previous step did not work on D, change the mac address of eth0 to da:c0:00:11:ee:ee, so D now has the IP and mac address of the original destination. [Wonder what would happen in an actual case scenario without Arpless Interstellar? .....don't know..... :)]

6) As the previous step was also unsuccessful, as a last resort, get into W and poison the ARP cache to point to D. On D, keep the IP and change the mac address to its original so that mac address spoofing protection done by interstellar does not block us. This should be it. So far this seems like a no-brainer, and can't wait for that ping to get through finally!!!

7) See what happens.

█║ Blockchain SSH Public Key Infrastructure Management

This quick demo shows fast passwordless SSH login and SCP with SynchroKnot Blockchain SSH Power Module. [Notice that tab completion works with SCP.]

To get it working [not shown in the video], in the target virtual machine simply modify the sshd_config and run the setup script [one time operation], and then map the Linux [or other operating system] username [ID] to the Blockchain ID of the SynchroKnot. That's it.

The video shows the username debian [on the vm deb] is interlock-mapped to the Blockchain ID 1PeDaGo6Uj9HWdVQs8zJAYeQ1478xrpwLE and Spacesuit of 1PeDaGo6Uj9HWdVQs8zJAYeQ1478xrpwLE shows the key sdac-pki-id with the value debian. This is essential for successful login access to the virtual machine. Only the SynchroKnot root user can perform the interlock-mapping of the user's identity.

Users manage their own public key(s) [ Base64 encoded & up to 10 keys ] in their Spacesuit on upto 5 different Spatial Fabric Arrays [geographically dispersed to protect against network and infrastructure failures].

Only the authorized SynchroKnot [user] can add or remove his/her public key(s). Even the SynchroKnot root user cannot perform this operation. This feature prevents anyone else from mistakenly/illegitimately denying access.

Note: In this demo the SynchroKnot user [not the linux user] happens to be a SynchroKnot root user. One can create users that are plain SynchroKnot users without SynchroKnot-root capabilities.

█║ AuthControl : Distributed Fault-Tolerant Authentication Management & Identification Control System

This is a very basic impromptu demonstration of AuthControl. Here both of the virtual machines are enabled with AuthControl and show the following:

■ Login via Graphical Interface

■ Login via Non-Graphical Interface

■ Run a command with SU as another user

■ Run a command with SUDO as another user

■ Login to a remote system via SSH

■ Mount a remote filesystem via SSHFS

■ Use File Manager to create a Network Place using SFTP

All these different types of logins use AuthControl with standard Linux users and password + 5 digit pin. Here the password used for all logins is hello12345 and the basic HTTPS traffic is captured on the Spatial Fabric Satellite using TCPDUMP to show realtime interaction with the SynchroKnot AuthControl Power Module when the password is entered in the virtual machines for the purposes of authentication.

Note: This demo was recorded on a severely resource-constrained system. It is up to you to determine the performance :)

Creative Commons License
SynchroKnot [ website - content - technology - architecture - methodology ] by SynchroKnot is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Based on a work at Spatial Systems Engineering at SynchroKnot : synchroknot.in synchroknot.com synchroknot.ch.