Recent updates to network-manager-gnome 1.2.0-0ubuntu0.16.04.3 corrected
the issue for me. Previous release also had issues with wpasupplicant and
eap-tls with RADIUS. This also seems to be fixed with
wpasupplicant 2.4-0ubuntu6.

--

Steve MacDougall

Sr. Systems/Network Administrator

647.258.3704 Direct

289.924.1086 Mobile

[email protected]
[image: BluePay, Inc.] <http://www.bluepay.com/>
[image: Twitter] <https://twitter.com/BluePay> [image: Linkedin]
<https://www.linkedin.com/company/bluepay-inc-> [image: Facebook]
<http://www.facebook.com/bluepayprocessing> [image: Google+]
<https://plus.google.com/+bluepay/posts> [image: YouTube]
<https://www.youtube.com/channel/UCIiHef9skKlAQUhejcFtUUg> [image: BluePay
Blog] <http://www.bluepay.com/blog>




On 8 July 2016 at 10:56, Michael Wingender <[email protected]>
wrote:

> I think I hit this bug also, but I can not confirm that is not working
> with an DES3 encrypted key file.
> I have generated encrypted key files with DES, DES3, AES128, AES192,
> AES256, CAMELLIA128, CAMELLIA192, CAMELLIA256 and SEED. WPA2 Enterprise
> configuration is working with DES, DES3 and AES128. All other key files are
> not accepted.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573720
>
> Title:
>   Unencrypted private keys are insecure error reported even when key is
>   encrypted
>
> Status in NetworkManager:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   Triaged
>
> Bug description:
>   When I enter an EAP-TLS wifi config, I get the error:
>
>   "Unencrypted private keys are insecure
>   The selected private key does not appear to be protected by a password.
> This could allow your security credentials to be compromised.  Please
> select a password-protected private key.
>
>   (You can password-protect your private key with openssl)"
>
>   I have verified that my key is, in fact, encrypted, and I have tried
>   using both des3 and aes256. I have also verified the password used to
>   encrypt the key.
>
>   For a while, it wouldn't even let me save the config. I managed to
>   save it eventually, but now when I try to connect to the saved
>   connection, I get the same error.
>
>   I am on Ubuntu mate 16.04
>
>   network-manager 1.1.93
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: network-manager 1.1.93-0ubuntu4
>   ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
>   Uname: Linux 4.4.0-21-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: MATE
>   Date: Fri Apr 22 13:25:16 2016
>   InstallationDate: Installed on 2015-08-19 (246 days ago)
>   InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64
> (20150422.1)
>   IpRoute:
>    default via 192.168.151.254 dev eth1  proto static  metric 100
>    169.254.0.0/16 dev eth1  scope link  metric 1000
>    192.168.151.0/24 dev eth1  proto kernel  scope link  src
> 192.168.151.95  metric 100
>   NetworkManager.state:
>    [main]
>    NetworkingEnabled=true
>    WirelessEnabled=true
>    WWANEnabled=true
>    WimaxEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
>   nmcli-dev:
>    DEVICE  TYPE      STATE         DBUS-PATH
>     CONNECTION          CON-UUID                              CON-PATH
>    eth1    ethernet  connected
>  /org/freedesktop/NetworkManager/Devices/2  Wired connection 1
> ed50d4f9-c810-4be0-b06c-8acd58015c50
> /org/freedesktop/NetworkManager/ActiveConnection/0
>    wlan0   wifi      disconnected
> /org/freedesktop/NetworkManager/Devices/1  --                  --
>                           --
>    eth0    ethernet  unavailable
>  /org/freedesktop/NetworkManager/Devices/3  --                  --
>                           --
>    lo      loopback  unmanaged
>  /org/freedesktop/NetworkManager/Devices/0  --                  --
>                           --
>   nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit
> code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1573720/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1573720

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE      STATE         DBUS-PATH                                  
CONNECTION          CON-UUID                              CON-PATH              
                             
   eth1    ethernet  connected     /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi      disconnected  /org/freedesktop/NetworkManager/Devices/1  
--                  --                                    --                    
                             
   eth0    ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--                  --                                    --                    
                             
   lo      loopback  unmanaged     /org/freedesktop/NetworkManager/Devices/0  
--                  --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1573720/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to