Set a password for an Azure public-IP












0















I would like to add security (e.g. a login with a password) for the public-ip for my Azure VM. Because else everybody could e.g. deploy smart contracts via the cakeshop links or turn off and on the Ethereum nodes.



Does anybody know how to do it?










share|improve this question



























    0















    I would like to add security (e.g. a login with a password) for the public-ip for my Azure VM. Because else everybody could e.g. deploy smart contracts via the cakeshop links or turn off and on the Ethereum nodes.



    Does anybody know how to do it?










    share|improve this question

























      0












      0








      0








      I would like to add security (e.g. a login with a password) for the public-ip for my Azure VM. Because else everybody could e.g. deploy smart contracts via the cakeshop links or turn off and on the Ethereum nodes.



      Does anybody know how to do it?










      share|improve this question














      I would like to add security (e.g. a login with a password) for the public-ip for my Azure VM. Because else everybody could e.g. deploy smart contracts via the cakeshop links or turn off and on the Ethereum nodes.



      Does anybody know how to do it?







      azure virtual-machine ethereum azure-public-ip






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 17 '18 at 14:46









      saitamsaitam

      887829




      887829
























          2 Answers
          2






          active

          oldest

          votes


















          0














          It seems that you cannot set a password for the public IP. But you can set the password for the VM. For the security of the VM, you can use the Azure Network Security Group to filter the traffic. For more details, see Filter network traffic with a network security group.



          For more security to the VM, you can try the Identity of Azure AD. Take a look at this Configure managed identities for Azure resources on a VM. Hope this will help you.






          share|improve this answer
























          • Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

            – saitam
            Nov 18 '18 at 9:11













          • But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

            – Charles Xu
            Nov 18 '18 at 9:16













          • I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

            – saitam
            Nov 18 '18 at 11:25





















          0














          There is no such thing as a password for a public IP, a public IP is just a resource assigning IP's to a network interface, nothing more.



          If you are hosting an application in Azure it is up to you to make sure this is secure. Ideally, this would be done through authentication at the application layer, to prevent users from being able to do anything in the application without authenticating. If your application does not provide this then you may want to take a closer look at your application and whether it is fit for purpose.



          If application level authentication is not possible then you could look at adding authentication at the application server level, be this Apache, IIS, Tomcat etc. You would need to look at the appropriate documentation for your application server.






          share|improve this answer
























          • I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

            – saitam
            Nov 18 '18 at 11:31











          • I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

            – Sam Cogan
            Nov 18 '18 at 11:33











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53352284%2fset-a-password-for-an-azure-public-ip%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          It seems that you cannot set a password for the public IP. But you can set the password for the VM. For the security of the VM, you can use the Azure Network Security Group to filter the traffic. For more details, see Filter network traffic with a network security group.



          For more security to the VM, you can try the Identity of Azure AD. Take a look at this Configure managed identities for Azure resources on a VM. Hope this will help you.






          share|improve this answer
























          • Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

            – saitam
            Nov 18 '18 at 9:11













          • But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

            – Charles Xu
            Nov 18 '18 at 9:16













          • I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

            – saitam
            Nov 18 '18 at 11:25


















          0














          It seems that you cannot set a password for the public IP. But you can set the password for the VM. For the security of the VM, you can use the Azure Network Security Group to filter the traffic. For more details, see Filter network traffic with a network security group.



          For more security to the VM, you can try the Identity of Azure AD. Take a look at this Configure managed identities for Azure resources on a VM. Hope this will help you.






          share|improve this answer
























          • Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

            – saitam
            Nov 18 '18 at 9:11













          • But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

            – Charles Xu
            Nov 18 '18 at 9:16













          • I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

            – saitam
            Nov 18 '18 at 11:25
















          0












          0








          0







          It seems that you cannot set a password for the public IP. But you can set the password for the VM. For the security of the VM, you can use the Azure Network Security Group to filter the traffic. For more details, see Filter network traffic with a network security group.



          For more security to the VM, you can try the Identity of Azure AD. Take a look at this Configure managed identities for Azure resources on a VM. Hope this will help you.






          share|improve this answer













          It seems that you cannot set a password for the public IP. But you can set the password for the VM. For the security of the VM, you can use the Azure Network Security Group to filter the traffic. For more details, see Filter network traffic with a network security group.



          For more security to the VM, you can try the Identity of Azure AD. Take a look at this Configure managed identities for Azure resources on a VM. Hope this will help you.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 17 '18 at 15:11









          Charles XuCharles Xu

          3,7581210




          3,7581210













          • Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

            – saitam
            Nov 18 '18 at 9:11













          • But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

            – Charles Xu
            Nov 18 '18 at 9:16













          • I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

            – saitam
            Nov 18 '18 at 11:25





















          • Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

            – saitam
            Nov 18 '18 at 9:11













          • But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

            – Charles Xu
            Nov 18 '18 at 9:16













          • I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

            – saitam
            Nov 18 '18 at 11:25



















          Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

          – saitam
          Nov 18 '18 at 9:11







          Assigning vm identities brings nothing if the public ip exposes all the possibilities to change core configurations on your nodes to everybody over http and even offers a user friendly UI to do it. This can't be true if there is no way to close this UI. It's almost the same as if I post my Azure user+passwd, so everybody can shut down, start up and deploy smart contracts on my Quorum nodes

          – saitam
          Nov 18 '18 at 9:11















          But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

          – Charles Xu
          Nov 18 '18 at 9:16







          But it's impossible to set the password to the password. Others can do nothing if they do not have the permission of the VM even if they have the public IP. So you can use another way to keep the VM safe, not just for focus on the public IP.

          – Charles Xu
          Nov 18 '18 at 9:16















          I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

          – saitam
          Nov 18 '18 at 11:25







          I have now logged out of portal.azure.com and then went to the public-ip and there I have a UI where I have a field node control and I can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. How can others do nothing if they can by using the above mentioned things e.g. Stop the complete Block Chain Network via the offered UI?

          – saitam
          Nov 18 '18 at 11:25















          0














          There is no such thing as a password for a public IP, a public IP is just a resource assigning IP's to a network interface, nothing more.



          If you are hosting an application in Azure it is up to you to make sure this is secure. Ideally, this would be done through authentication at the application layer, to prevent users from being able to do anything in the application without authenticating. If your application does not provide this then you may want to take a closer look at your application and whether it is fit for purpose.



          If application level authentication is not possible then you could look at adding authentication at the application server level, be this Apache, IIS, Tomcat etc. You would need to look at the appropriate documentation for your application server.






          share|improve this answer
























          • I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

            – saitam
            Nov 18 '18 at 11:31











          • I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

            – Sam Cogan
            Nov 18 '18 at 11:33
















          0














          There is no such thing as a password for a public IP, a public IP is just a resource assigning IP's to a network interface, nothing more.



          If you are hosting an application in Azure it is up to you to make sure this is secure. Ideally, this would be done through authentication at the application layer, to prevent users from being able to do anything in the application without authenticating. If your application does not provide this then you may want to take a closer look at your application and whether it is fit for purpose.



          If application level authentication is not possible then you could look at adding authentication at the application server level, be this Apache, IIS, Tomcat etc. You would need to look at the appropriate documentation for your application server.






          share|improve this answer
























          • I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

            – saitam
            Nov 18 '18 at 11:31











          • I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

            – Sam Cogan
            Nov 18 '18 at 11:33














          0












          0








          0







          There is no such thing as a password for a public IP, a public IP is just a resource assigning IP's to a network interface, nothing more.



          If you are hosting an application in Azure it is up to you to make sure this is secure. Ideally, this would be done through authentication at the application layer, to prevent users from being able to do anything in the application without authenticating. If your application does not provide this then you may want to take a closer look at your application and whether it is fit for purpose.



          If application level authentication is not possible then you could look at adding authentication at the application server level, be this Apache, IIS, Tomcat etc. You would need to look at the appropriate documentation for your application server.






          share|improve this answer













          There is no such thing as a password for a public IP, a public IP is just a resource assigning IP's to a network interface, nothing more.



          If you are hosting an application in Azure it is up to you to make sure this is secure. Ideally, this would be done through authentication at the application layer, to prevent users from being able to do anything in the application without authenticating. If your application does not provide this then you may want to take a closer look at your application and whether it is fit for purpose.



          If application level authentication is not possible then you could look at adding authentication at the application server level, be this Apache, IIS, Tomcat etc. You would need to look at the appropriate documentation for your application server.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 18 '18 at 11:20









          Sam CoganSam Cogan

          1,87262863




          1,87262863













          • I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

            – saitam
            Nov 18 '18 at 11:31











          • I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

            – Sam Cogan
            Nov 18 '18 at 11:33



















          • I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

            – saitam
            Nov 18 '18 at 11:31











          • I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

            – Sam Cogan
            Nov 18 '18 at 11:33

















          I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

          – saitam
          Nov 18 '18 at 11:31





          I am using Quorum offered by Azure. After deploying it, there is a public-ip, which leads everybody to a UI, where everybody can Restart Node, Stop Node, Start Node, Create New Chain and also can deploy a smart contract. So your suggestion would be to shut down the cakeshop UIs offered by Microsoft Azure?

          – saitam
          Nov 18 '18 at 11:31













          I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

          – Sam Cogan
          Nov 18 '18 at 11:33





          I have no experience with Quorum, but looking at it, this is not a service offered by Microsoft, it is a marketplace offering from a third part that runs in a VM on Azure. Given that you have same options mentioned above, enable application security if Quorum offers it (which it really should) or do it at the VM level

          – Sam Cogan
          Nov 18 '18 at 11:33


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53352284%2fset-a-password-for-an-azure-public-ip%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to pass form data using jquery Ajax to insert data in database?

          National Museum of Racing and Hall of Fame

          Guess what letter conforming each word