Ruminating on Mutual Authentication

In mutual authentication, both the server as well as the client have digital certificates and authenticate each other. If both the server and client are using CA signed certificates, then everything would work OOTB and there would be no need to import any certificates. This is because, both the server and client default trust stores would have the root certificates of most CAs.

But during testing and in lower environments, teams often use self-signed certificates. To enable mutual authentication using self-signed certificates, we have 2 options. 

• Peer-2-Peer: Create a client certificate for each agent. Import this cert into the trust store of the server. 
• Root cert derived client certifications:  Create a client root certificate and using this root certificate, create/derive client certs for each agent. Then you just have to import the client root certificate into the server trust store ( and not of all the agents).    

 The following links are a good read for implementing the above. 

https://docs.oracle.com/cd/E19879-01/819-3669/bnbyi/index.html

https://gist.github.com/granella/01ba0944865d99227cf080e97f4b3cb6

https://sites.google.com/site/ddmwsst/create-your-own-certificate-and-ca

https://docs.couchbase.com/server/current/manage/manage-security/configure-client-certificates.html

https://docs.microsoft.com/en-us/previous-versions/msp-n-p/ff650751(v=pandp.10)?redirectedfrom=MSDN

Ruminating on Azure RTOS

Microsoft acquired ThreadX from Express Logic and re-branded it as Azure RTOS. ThreadX was already a popular RTOS that is being used by more than 6.5B devices worldwide.

** Gartner predicts that by 2021, one million new IoT devices will come online every hour of every day. In 2019, there were approx 27B IoT devices.

Besides ThreadX, Azure RTOS has also packaged other modules such as GuiX, FileX, NetX, USBX, etc. 

The below link points to an interesting conversation with Bill Lamie - founder of ThreadX. 

https://youtu.be/TGWg7yQATqQ

Jotting down some interesting points below. 

• The most important characteristic of an RTOS is size. RTOS size is typically in KB, whereas general purpose OS is in MB or GB. Because of this size, RTOS can be used in the smallest of devices...even battery powered ones - e.g. fitness wearables, medical implants, etc. So essentially RTOS is great for constrained/smaller devices. 
• RTOS is "real-time" because the OS responds to real time events in a deterministic time frame. An RTOS guarantees that certain actions can happen on IoT devices within defined time limits - a feature called as determinism. 
• The size of Azure RTOS can scale down all the way to 2KB. A cloud connected RTOS would take 50KB.
• Azure RTOS also brings in best-of-class security with multiple security certifications. 
• The complete source code of Azure RTOS is open-source and available on GitHub at https://github.com/azure-rtos

Before the acquisition of Express Logic, Microsoft had an offering called Azure Sphere OS that was positioned as an OS for edge devices. Azure Sphere is more secure and is Linux kernel based, but cannot run on highly constrained devices. Also it has a Linux kernel and is not an RTOS and hence cannot provide deterministic execution. 

Though Microsoft is currently stating that Azure RTOS and Azure Sphere are complementary, only time will tell which OS the industry adopts. 

Open DataSets

The following sites offer many free data-sets that can be used to train our AI models and learn new stuff on AIML. Happy coding !

• https://www.openml.org/search?type=data
• https://archive.ics.uci.edu/ml/index.php
• https://www.reddit.com/r/datasets/
• http://academictorrents.com/browse.php
• https://www.opendatanetwork.com/
• https://www.data.gov/
• https://github.com/BuzzFeedNews/everything#standalone-datasets
• https://github.com/fivethirtyeight/data
• https://data.world/community/open-community/
• https://www.kaggle.com/datasets