Ubuntu 16.04, WPA Enterprise TLS on WiFi: unable to browse private key

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












On Ubuntu 16.04, for setting up a WiFi access under WPA Enterprise TLS, generated a PEM RSA private key as follows:



$ cd ~/.wifi_certificates
$ keyPassPhrase="$(pwgen -snc1 16)"
$ echo "key=$keyPassPhrase" > key_passphrase
$ chmod og-r key_passphrase
$ clientName=`uname -n` # themc
$ openssl genrsa -aes256 -passout pass:"$keyPassPhrase" -out $clientName.key 2048
$ file $clientName.key
themc.key: PEM RSA private key


Eventually, attempted to provide themc.key file to the WiFi GUI -- but as seen in the screenshot below, the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file:



the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file



Although screenshot shows Identity, User certificate and CA certificate fields as empty, ran into same issue even when all these fields had suitable values.



Also tried to just enter the value themc.key in the file /etc/NetworkManager/system-connections/<connection> but, when attempting to establish the connection, get a pop-up about themc.key not being acceptable.



Creating a wpa_supplicant.conf file with the same certificates and key as used for NetworkManager and providing that wpa_supplicant.conf file to wpa_supplicant results in a successful connection.



Questions: Why doesn't the GUI accept themc.key as a PEM private key even though the file command classifies themc.key as a PEM RSA private key? Why is NetworkManager not happy with themc.key but wpa_supplicant is?










share|improve this question



























    up vote
    0
    down vote

    favorite












    On Ubuntu 16.04, for setting up a WiFi access under WPA Enterprise TLS, generated a PEM RSA private key as follows:



    $ cd ~/.wifi_certificates
    $ keyPassPhrase="$(pwgen -snc1 16)"
    $ echo "key=$keyPassPhrase" > key_passphrase
    $ chmod og-r key_passphrase
    $ clientName=`uname -n` # themc
    $ openssl genrsa -aes256 -passout pass:"$keyPassPhrase" -out $clientName.key 2048
    $ file $clientName.key
    themc.key: PEM RSA private key


    Eventually, attempted to provide themc.key file to the WiFi GUI -- but as seen in the screenshot below, the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file:



    the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file



    Although screenshot shows Identity, User certificate and CA certificate fields as empty, ran into same issue even when all these fields had suitable values.



    Also tried to just enter the value themc.key in the file /etc/NetworkManager/system-connections/<connection> but, when attempting to establish the connection, get a pop-up about themc.key not being acceptable.



    Creating a wpa_supplicant.conf file with the same certificates and key as used for NetworkManager and providing that wpa_supplicant.conf file to wpa_supplicant results in a successful connection.



    Questions: Why doesn't the GUI accept themc.key as a PEM private key even though the file command classifies themc.key as a PEM RSA private key? Why is NetworkManager not happy with themc.key but wpa_supplicant is?










    share|improve this question

























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      On Ubuntu 16.04, for setting up a WiFi access under WPA Enterprise TLS, generated a PEM RSA private key as follows:



      $ cd ~/.wifi_certificates
      $ keyPassPhrase="$(pwgen -snc1 16)"
      $ echo "key=$keyPassPhrase" > key_passphrase
      $ chmod og-r key_passphrase
      $ clientName=`uname -n` # themc
      $ openssl genrsa -aes256 -passout pass:"$keyPassPhrase" -out $clientName.key 2048
      $ file $clientName.key
      themc.key: PEM RSA private key


      Eventually, attempted to provide themc.key file to the WiFi GUI -- but as seen in the screenshot below, the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file:



      the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file



      Although screenshot shows Identity, User certificate and CA certificate fields as empty, ran into same issue even when all these fields had suitable values.



      Also tried to just enter the value themc.key in the file /etc/NetworkManager/system-connections/<connection> but, when attempting to establish the connection, get a pop-up about themc.key not being acceptable.



      Creating a wpa_supplicant.conf file with the same certificates and key as used for NetworkManager and providing that wpa_supplicant.conf file to wpa_supplicant results in a successful connection.



      Questions: Why doesn't the GUI accept themc.key as a PEM private key even though the file command classifies themc.key as a PEM RSA private key? Why is NetworkManager not happy with themc.key but wpa_supplicant is?










      share|improve this question















      On Ubuntu 16.04, for setting up a WiFi access under WPA Enterprise TLS, generated a PEM RSA private key as follows:



      $ cd ~/.wifi_certificates
      $ keyPassPhrase="$(pwgen -snc1 16)"
      $ echo "key=$keyPassPhrase" > key_passphrase
      $ chmod og-r key_passphrase
      $ clientName=`uname -n` # themc
      $ openssl genrsa -aes256 -passout pass:"$keyPassPhrase" -out $clientName.key 2048
      $ file $clientName.key
      themc.key: PEM RSA private key


      Eventually, attempted to provide themc.key file to the WiFi GUI -- but as seen in the screenshot below, the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file:



      the GUI's directory-browser will not allow selecting themc.key as a PEM Private Key file



      Although screenshot shows Identity, User certificate and CA certificate fields as empty, ran into same issue even when all these fields had suitable values.



      Also tried to just enter the value themc.key in the file /etc/NetworkManager/system-connections/<connection> but, when attempting to establish the connection, get a pop-up about themc.key not being acceptable.



      Creating a wpa_supplicant.conf file with the same certificates and key as used for NetworkManager and providing that wpa_supplicant.conf file to wpa_supplicant results in a successful connection.



      Questions: Why doesn't the GUI accept themc.key as a PEM private key even though the file command classifies themc.key as a PEM RSA private key? Why is NetworkManager not happy with themc.key but wpa_supplicant is?







      16.04 wireless network-manager wpa-supplicant






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 28 at 15:50

























      asked Feb 24 at 5:30









      user1823664

      1306




      1306




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          I had the same problem and I found a workaround to it. Not sure if you still need this answer but maybe someone else runs into the same issue.



          Once you open the file explorer to browse for your private key, press CTRL+L (to open the location bar) and input the absolute path to your key manually.



          Seems to be a kind of bug only for the first time you want to browse it due to if you try after you filled the field with manually, you'll be able to successfully browse the .pem and all the other formats.






          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',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            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%2f1009230%2fubuntu-16-04-wpa-enterprise-tls-on-wifi-unable-to-browse-private-key%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote



            accepted










            I had the same problem and I found a workaround to it. Not sure if you still need this answer but maybe someone else runs into the same issue.



            Once you open the file explorer to browse for your private key, press CTRL+L (to open the location bar) and input the absolute path to your key manually.



            Seems to be a kind of bug only for the first time you want to browse it due to if you try after you filled the field with manually, you'll be able to successfully browse the .pem and all the other formats.






            share|improve this answer


























              up vote
              1
              down vote



              accepted










              I had the same problem and I found a workaround to it. Not sure if you still need this answer but maybe someone else runs into the same issue.



              Once you open the file explorer to browse for your private key, press CTRL+L (to open the location bar) and input the absolute path to your key manually.



              Seems to be a kind of bug only for the first time you want to browse it due to if you try after you filled the field with manually, you'll be able to successfully browse the .pem and all the other formats.






              share|improve this answer
























                up vote
                1
                down vote



                accepted







                up vote
                1
                down vote



                accepted






                I had the same problem and I found a workaround to it. Not sure if you still need this answer but maybe someone else runs into the same issue.



                Once you open the file explorer to browse for your private key, press CTRL+L (to open the location bar) and input the absolute path to your key manually.



                Seems to be a kind of bug only for the first time you want to browse it due to if you try after you filled the field with manually, you'll be able to successfully browse the .pem and all the other formats.






                share|improve this answer














                I had the same problem and I found a workaround to it. Not sure if you still need this answer but maybe someone else runs into the same issue.



                Once you open the file explorer to browse for your private key, press CTRL+L (to open the location bar) and input the absolute path to your key manually.



                Seems to be a kind of bug only for the first time you want to browse it due to if you try after you filled the field with manually, you'll be able to successfully browse the .pem and all the other formats.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 6 at 7:27

























                answered Apr 6 at 7:21









                partu18

                262




                262



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009230%2fubuntu-16-04-wpa-enterprise-tls-on-wifi-unable-to-browse-private-key%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491