July-10th-2018, 07:23 PM
Hello,
today we have released the version V1.1.3.0RC3 of netPI firmware, that allows you to upload (own) certificates of trusted CA's in netPI's Security/PKI management page.
With this step it is possible now for everybody to load images no longer from Docker Hub registry only, but from own registry servers reporting certificates signed by this own trusted CA as well, once you uploaded the trusted root certificate of this CA to netPI.
Best example I described today is letting an ordinary Raspberry Pi be your registry server in your accessible network: https://www.netiot.com/de/forum/?tx_typo...df33e7f874
This is the first step to support/host personal trusted registry servers in accordance with the offical docker documentation here: https://docs.docker.com/v17.09/registry/deploying/. Using a self signed certificate is good enough method for securing your Docker Registry.
today we have released the version V1.1.3.0RC3 of netPI firmware, that allows you to upload (own) certificates of trusted CA's in netPI's Security/PKI management page.
With this step it is possible now for everybody to load images no longer from Docker Hub registry only, but from own registry servers reporting certificates signed by this own trusted CA as well, once you uploaded the trusted root certificate of this CA to netPI.
Best example I described today is letting an ordinary Raspberry Pi be your registry server in your accessible network: https://www.netiot.com/de/forum/?tx_typo...df33e7f874
This is the first step to support/host personal trusted registry servers in accordance with the offical docker documentation here: https://docs.docker.com/v17.09/registry/deploying/. Using a self signed certificate is good enough method for securing your Docker Registry.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)