Ubuntu 16.04, WPA Enterprise TLS on WiFi: unable to browse private key
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
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:
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
add a comment |Â
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:
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
add a comment |Â
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:
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
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:
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
16.04 wireless network-manager wpa-supplicant
edited Feb 28 at 15:50
asked Feb 24 at 5:30
user1823664
1306
1306
add a comment |Â
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
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.
edited Apr 6 at 7:27
answered Apr 6 at 7:21
![](https://i.stack.imgur.com/fGIqH.jpg?s=32&g=1)
![](https://i.stack.imgur.com/fGIqH.jpg?s=32&g=1)
partu18
262
262
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password