OK, reason I did so is because this bug appears to have been neglected for
~18 months, since 2013-08-26. More and more people are reporting similar
issues online, although not necessary via the Ubuntu bug tracker. I will
try to push upstream...thanks
On Wed, Mar 18, 2015 at 6:40 PM Alberto Salvia Novella <
<email address hidden>> wrote:
> Please:
> - Report to <https://bugzilla.gnome.org/>
> - Paste the new report URL here.
> - Set this bug status back to confirmed.
>
> Thank you.
>
> ** Changed in: network-manager-openvpn (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: asked-to-upstream
>
> ** Tags added: lucid precise trusty utopic vivid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1217094
>
> Title:
> Strong HMAC authentication (SHA256, SHA512) that is supported by
> OpenVPN cannot be selected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager-openvpn/+bug/
> 1217094/+subscriptions
>
OK, reason I did so is because this bug appears to have been neglected for
~18 months, since 2013-08-26. More and more people are reporting similar
issues online, although not necessary via the Ubuntu bug tracker. I will
try to push upstream...thanks
On Wed, Mar 18, 2015 at 6:40 PM Alberto Salvia Novella <
<email address hidden>> wrote:
> Please: /bugzilla. gnome.org/> manager- openvpn (Ubuntu) /bugs.launchpad .net/bugs/ 1217094 /bugs.launchpad .net/network- manager- openvpn/ +bug/ +subscriptions
> - Report to <https:/
> - Paste the new report URL here.
> - Set this bug status back to confirmed.
>
> Thank you.
>
> ** Changed in: network-
> Status: Confirmed => Incomplete
>
> ** Tags added: asked-to-upstream
>
> ** Tags added: lucid precise trusty utopic vivid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Strong HMAC authentication (SHA256, SHA512) that is supported by
> OpenVPN cannot be selected
>
> To manage notifications about this bug go to:
> https:/
> 1217094/
>