how do you create an app profile for ufw?












27















Ufw has a command that lists out profiles to which you can further explore their profile definitions



$ ufw app list


And



$ ufw app PROFILE {app profile title}


I was wondering how you can create a profile for an undefined program, like virtual box and have that profile run the same definitions I have given iptables for my Ubuntu distro.





Not only am I trying to use Ubuntus firewall to service my virtual machine. I am also sincerely curious as how to create a profile for an application that doesn't come with one.










share|improve this question





























    27















    Ufw has a command that lists out profiles to which you can further explore their profile definitions



    $ ufw app list


    And



    $ ufw app PROFILE {app profile title}


    I was wondering how you can create a profile for an undefined program, like virtual box and have that profile run the same definitions I have given iptables for my Ubuntu distro.





    Not only am I trying to use Ubuntus firewall to service my virtual machine. I am also sincerely curious as how to create a profile for an application that doesn't come with one.










    share|improve this question



























      27












      27








      27


      10






      Ufw has a command that lists out profiles to which you can further explore their profile definitions



      $ ufw app list


      And



      $ ufw app PROFILE {app profile title}


      I was wondering how you can create a profile for an undefined program, like virtual box and have that profile run the same definitions I have given iptables for my Ubuntu distro.





      Not only am I trying to use Ubuntus firewall to service my virtual machine. I am also sincerely curious as how to create a profile for an application that doesn't come with one.










      share|improve this question
















      Ufw has a command that lists out profiles to which you can further explore their profile definitions



      $ ufw app list


      And



      $ ufw app PROFILE {app profile title}


      I was wondering how you can create a profile for an undefined program, like virtual box and have that profile run the same definitions I have given iptables for my Ubuntu distro.





      Not only am I trying to use Ubuntus firewall to service my virtual machine. I am also sincerely curious as how to create a profile for an application that doesn't come with one.







      firewall iptables ufw






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 18 '15 at 18:05









      Andrea Corbellini

      12k24465




      12k24465










      asked Jan 22 '14 at 5:53









      MiphixMiphix

      4381619




      4381619






















          2 Answers
          2






          active

          oldest

          votes


















          29














          To answer the real question, about how to create your own application file, you only need to know that it is using windows INI file format (yuck).



          [appname]
          title=1-liner here
          description=a longer line here
          ports=1,2,3,4,5,6,7,8,9,10,30/tcp|50/udp|53


          The ports line can specify multiple ports, with /udp or /tcp, to limit the protocol, otherwise it defaults to both. You have to split the protocol sections up with |.



          So, for a real-life set of examples I made:



          [puppet]
          title=puppet configuration manager
          description=Puppet Open Source from http://www.puppetlabs.com/
          ports=80,443,8140/tcp

          [AMANDA]
          title=AMANDA Backup
          description=AMANDA the Advanced Maryland Automatic Network Disk Archiver
          ports=10080


          You can list multiple versions of the app in a single file, like this one from apache:



          ===start of apache2.2-common file===
          [Apache]
          title=Web Server
          description=Apache v2 is the next generation of the omnipresent Apache web server.
          ports=80/tcp

          [Apache Secure]
          title=Web Server (HTTPS)
          description=Apache v2 is the next generation of the omnipresent Apache web server.
          ports=443/tcp

          [Apache Full]
          title=Web Server (HTTP,HTTPS)
          description=Apache v2 is the next generation of the omnipresent Apache web server.
          ports=80,443/tcp

          ===end of file===


          Once you have defined your application file, put it in /etc/ufw/applications.d, then tell ufw to reload the application definitions with



          ufw app update appname
          ufw app info appname


          Use it with something like:



          ufw allow from 192.168.1.10 to any app amanda
          ufw allow amanda


          assuming 192.168.1.10 is the IP of your amanda server.






          share|improve this answer


























          • your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

            – Hilikus
            Jul 7 '15 at 5:24











          • My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

            – user207998
            Aug 14 '15 at 16:51











          • I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

            – intcreator
            Mar 8 '18 at 22:50











          • Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

            – user207998
            Mar 24 '18 at 16:52





















          10














          It's actually all there in the manpage under the "Application Integration" section.



          The basic syntax is:



          ufw allow <app_name>


          Or you can use the extended syntax to be more specific:



          ufw allow from <some_address> to any app <app_name>


          The manpage specifically says not to specify a port number:




          You should not specify the protocol with either syntax, and with the
          extended syntax, use app in place of the port clause.




          This probably means it will let <app_name> use whatever port it wants to..



          Other useful commands:



          ufw app info <app_name>


          Which lists the information on <app_name>'s profile.



          ufw app update <app_name>  


          Which updates <app_name>'s profile. You can use all to update all application profiles.



          You can use the:



          ufw app update --add-new <app_name>  


          command to add a new profile for <app_name> and update it, following the rules you set out with ufw app default <policy>.



          App profiles are stored in /etc/ufw/applications.d and sometimes /etc/services.



          For more information see man ufw.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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%2faskubuntu.com%2fquestions%2f409013%2fhow-do-you-create-an-app-profile-for-ufw%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









            29














            To answer the real question, about how to create your own application file, you only need to know that it is using windows INI file format (yuck).



            [appname]
            title=1-liner here
            description=a longer line here
            ports=1,2,3,4,5,6,7,8,9,10,30/tcp|50/udp|53


            The ports line can specify multiple ports, with /udp or /tcp, to limit the protocol, otherwise it defaults to both. You have to split the protocol sections up with |.



            So, for a real-life set of examples I made:



            [puppet]
            title=puppet configuration manager
            description=Puppet Open Source from http://www.puppetlabs.com/
            ports=80,443,8140/tcp

            [AMANDA]
            title=AMANDA Backup
            description=AMANDA the Advanced Maryland Automatic Network Disk Archiver
            ports=10080


            You can list multiple versions of the app in a single file, like this one from apache:



            ===start of apache2.2-common file===
            [Apache]
            title=Web Server
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80/tcp

            [Apache Secure]
            title=Web Server (HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=443/tcp

            [Apache Full]
            title=Web Server (HTTP,HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80,443/tcp

            ===end of file===


            Once you have defined your application file, put it in /etc/ufw/applications.d, then tell ufw to reload the application definitions with



            ufw app update appname
            ufw app info appname


            Use it with something like:



            ufw allow from 192.168.1.10 to any app amanda
            ufw allow amanda


            assuming 192.168.1.10 is the IP of your amanda server.






            share|improve this answer


























            • your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

              – Hilikus
              Jul 7 '15 at 5:24











            • My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

              – user207998
              Aug 14 '15 at 16:51











            • I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

              – intcreator
              Mar 8 '18 at 22:50











            • Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

              – user207998
              Mar 24 '18 at 16:52


















            29














            To answer the real question, about how to create your own application file, you only need to know that it is using windows INI file format (yuck).



            [appname]
            title=1-liner here
            description=a longer line here
            ports=1,2,3,4,5,6,7,8,9,10,30/tcp|50/udp|53


            The ports line can specify multiple ports, with /udp or /tcp, to limit the protocol, otherwise it defaults to both. You have to split the protocol sections up with |.



            So, for a real-life set of examples I made:



            [puppet]
            title=puppet configuration manager
            description=Puppet Open Source from http://www.puppetlabs.com/
            ports=80,443,8140/tcp

            [AMANDA]
            title=AMANDA Backup
            description=AMANDA the Advanced Maryland Automatic Network Disk Archiver
            ports=10080


            You can list multiple versions of the app in a single file, like this one from apache:



            ===start of apache2.2-common file===
            [Apache]
            title=Web Server
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80/tcp

            [Apache Secure]
            title=Web Server (HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=443/tcp

            [Apache Full]
            title=Web Server (HTTP,HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80,443/tcp

            ===end of file===


            Once you have defined your application file, put it in /etc/ufw/applications.d, then tell ufw to reload the application definitions with



            ufw app update appname
            ufw app info appname


            Use it with something like:



            ufw allow from 192.168.1.10 to any app amanda
            ufw allow amanda


            assuming 192.168.1.10 is the IP of your amanda server.






            share|improve this answer


























            • your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

              – Hilikus
              Jul 7 '15 at 5:24











            • My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

              – user207998
              Aug 14 '15 at 16:51











            • I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

              – intcreator
              Mar 8 '18 at 22:50











            • Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

              – user207998
              Mar 24 '18 at 16:52
















            29












            29








            29







            To answer the real question, about how to create your own application file, you only need to know that it is using windows INI file format (yuck).



            [appname]
            title=1-liner here
            description=a longer line here
            ports=1,2,3,4,5,6,7,8,9,10,30/tcp|50/udp|53


            The ports line can specify multiple ports, with /udp or /tcp, to limit the protocol, otherwise it defaults to both. You have to split the protocol sections up with |.



            So, for a real-life set of examples I made:



            [puppet]
            title=puppet configuration manager
            description=Puppet Open Source from http://www.puppetlabs.com/
            ports=80,443,8140/tcp

            [AMANDA]
            title=AMANDA Backup
            description=AMANDA the Advanced Maryland Automatic Network Disk Archiver
            ports=10080


            You can list multiple versions of the app in a single file, like this one from apache:



            ===start of apache2.2-common file===
            [Apache]
            title=Web Server
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80/tcp

            [Apache Secure]
            title=Web Server (HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=443/tcp

            [Apache Full]
            title=Web Server (HTTP,HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80,443/tcp

            ===end of file===


            Once you have defined your application file, put it in /etc/ufw/applications.d, then tell ufw to reload the application definitions with



            ufw app update appname
            ufw app info appname


            Use it with something like:



            ufw allow from 192.168.1.10 to any app amanda
            ufw allow amanda


            assuming 192.168.1.10 is the IP of your amanda server.






            share|improve this answer















            To answer the real question, about how to create your own application file, you only need to know that it is using windows INI file format (yuck).



            [appname]
            title=1-liner here
            description=a longer line here
            ports=1,2,3,4,5,6,7,8,9,10,30/tcp|50/udp|53


            The ports line can specify multiple ports, with /udp or /tcp, to limit the protocol, otherwise it defaults to both. You have to split the protocol sections up with |.



            So, for a real-life set of examples I made:



            [puppet]
            title=puppet configuration manager
            description=Puppet Open Source from http://www.puppetlabs.com/
            ports=80,443,8140/tcp

            [AMANDA]
            title=AMANDA Backup
            description=AMANDA the Advanced Maryland Automatic Network Disk Archiver
            ports=10080


            You can list multiple versions of the app in a single file, like this one from apache:



            ===start of apache2.2-common file===
            [Apache]
            title=Web Server
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80/tcp

            [Apache Secure]
            title=Web Server (HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=443/tcp

            [Apache Full]
            title=Web Server (HTTP,HTTPS)
            description=Apache v2 is the next generation of the omnipresent Apache web server.
            ports=80,443/tcp

            ===end of file===


            Once you have defined your application file, put it in /etc/ufw/applications.d, then tell ufw to reload the application definitions with



            ufw app update appname
            ufw app info appname


            Use it with something like:



            ufw allow from 192.168.1.10 to any app amanda
            ufw allow amanda


            assuming 192.168.1.10 is the IP of your amanda server.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jan 8 at 16:05









            guntbert

            9,132133169




            9,132133169










            answered Jun 26 '14 at 22:07









            user207998user207998

            51644




            51644













            • your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

              – Hilikus
              Jul 7 '15 at 5:24











            • My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

              – user207998
              Aug 14 '15 at 16:51











            • I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

              – intcreator
              Mar 8 '18 at 22:50











            • Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

              – user207998
              Mar 24 '18 at 16:52





















            • your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

              – Hilikus
              Jul 7 '15 at 5:24











            • My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

              – user207998
              Aug 14 '15 at 16:51











            • I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

              – intcreator
              Mar 8 '18 at 22:50











            • Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

              – user207998
              Mar 24 '18 at 16:52



















            your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

            – Hilikus
            Jul 7 '15 at 5:24





            your syntax for combining udp and tcp is wrong. It should be xx/tcp|yy/udp. In other words, the separation between protocols should be a pipe, not a comma like in your example

            – Hilikus
            Jul 7 '15 at 5:24













            My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

            – user207998
            Aug 14 '15 at 16:51





            My example wasn't trying to combine them, it is a simple list of this-port-on-udp, some-other-port-on-tcp.

            – user207998
            Aug 14 '15 at 16:51













            I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

            – intcreator
            Mar 8 '18 at 22:50





            I just tried using netstat to find the application name...is that right? It worked for me at least. Is it case sensitive? I'm not really sure what the relationship is between the "appname" in the application file vs. the title vs. the process name, etc.

            – intcreator
            Mar 8 '18 at 22:50













            Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

            – user207998
            Mar 24 '18 at 16:52







            Netstat just lists the process name connected to a particular port. This doesn't necessarily match the name of the application. For example, the postfix application launches a variety of processes, including the 'master' process that opens port 25. I name the ufw app config file based on, say, the package name, ie 'Postfix' or 'AMANDA'. Within the config file there are one or more app definitions that represent ports opened by that package. There can be multiples, see the 'postfix' package as an example. There the app names vary based on how postfix was configured.

            – user207998
            Mar 24 '18 at 16:52















            10














            It's actually all there in the manpage under the "Application Integration" section.



            The basic syntax is:



            ufw allow <app_name>


            Or you can use the extended syntax to be more specific:



            ufw allow from <some_address> to any app <app_name>


            The manpage specifically says not to specify a port number:




            You should not specify the protocol with either syntax, and with the
            extended syntax, use app in place of the port clause.




            This probably means it will let <app_name> use whatever port it wants to..



            Other useful commands:



            ufw app info <app_name>


            Which lists the information on <app_name>'s profile.



            ufw app update <app_name>  


            Which updates <app_name>'s profile. You can use all to update all application profiles.



            You can use the:



            ufw app update --add-new <app_name>  


            command to add a new profile for <app_name> and update it, following the rules you set out with ufw app default <policy>.



            App profiles are stored in /etc/ufw/applications.d and sometimes /etc/services.



            For more information see man ufw.






            share|improve this answer






























              10














              It's actually all there in the manpage under the "Application Integration" section.



              The basic syntax is:



              ufw allow <app_name>


              Or you can use the extended syntax to be more specific:



              ufw allow from <some_address> to any app <app_name>


              The manpage specifically says not to specify a port number:




              You should not specify the protocol with either syntax, and with the
              extended syntax, use app in place of the port clause.




              This probably means it will let <app_name> use whatever port it wants to..



              Other useful commands:



              ufw app info <app_name>


              Which lists the information on <app_name>'s profile.



              ufw app update <app_name>  


              Which updates <app_name>'s profile. You can use all to update all application profiles.



              You can use the:



              ufw app update --add-new <app_name>  


              command to add a new profile for <app_name> and update it, following the rules you set out with ufw app default <policy>.



              App profiles are stored in /etc/ufw/applications.d and sometimes /etc/services.



              For more information see man ufw.






              share|improve this answer




























                10












                10








                10







                It's actually all there in the manpage under the "Application Integration" section.



                The basic syntax is:



                ufw allow <app_name>


                Or you can use the extended syntax to be more specific:



                ufw allow from <some_address> to any app <app_name>


                The manpage specifically says not to specify a port number:




                You should not specify the protocol with either syntax, and with the
                extended syntax, use app in place of the port clause.




                This probably means it will let <app_name> use whatever port it wants to..



                Other useful commands:



                ufw app info <app_name>


                Which lists the information on <app_name>'s profile.



                ufw app update <app_name>  


                Which updates <app_name>'s profile. You can use all to update all application profiles.



                You can use the:



                ufw app update --add-new <app_name>  


                command to add a new profile for <app_name> and update it, following the rules you set out with ufw app default <policy>.



                App profiles are stored in /etc/ufw/applications.d and sometimes /etc/services.



                For more information see man ufw.






                share|improve this answer















                It's actually all there in the manpage under the "Application Integration" section.



                The basic syntax is:



                ufw allow <app_name>


                Or you can use the extended syntax to be more specific:



                ufw allow from <some_address> to any app <app_name>


                The manpage specifically says not to specify a port number:




                You should not specify the protocol with either syntax, and with the
                extended syntax, use app in place of the port clause.




                This probably means it will let <app_name> use whatever port it wants to..



                Other useful commands:



                ufw app info <app_name>


                Which lists the information on <app_name>'s profile.



                ufw app update <app_name>  


                Which updates <app_name>'s profile. You can use all to update all application profiles.



                You can use the:



                ufw app update --add-new <app_name>  


                command to add a new profile for <app_name> and update it, following the rules you set out with ufw app default <policy>.



                App profiles are stored in /etc/ufw/applications.d and sometimes /etc/services.



                For more information see man ufw.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Feb 16 '15 at 17:43

























                answered Jan 22 '14 at 6:16









                SethSeth

                34.2k26110162




                34.2k26110162






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f409013%2fhow-do-you-create-an-app-profile-for-ufw%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 make a Squid Proxy server?

                    Is this a new Fibonacci Identity?

                    19世紀