On 20/07/17 13:55, Alexander Ploumistos wrote:
> On Thu, Jul 20, 2017 at 2:21 PM, David Sommerseth wrote:
>> I rather prefer to have this change in Fedora _now_ in a _planned_
>> release where this can be tested out before the final F27 is released.
>
> I modified the unit file on a F26 VPS and I
On Thu, Jul 20, 2017 at 2:21 PM, David Sommerseth wrote:
> I rather prefer to have this change in Fedora _now_ in a _planned_
> release where this can be tested out before the final F27 is released.
I modified the unit file on a F26 VPS and I didn't have any problems
connecting with F24, F25, F26
On 20/07/17 09:46, Farkas Levente wrote:
> On 07/20/2017 02:09 AM, David Sommerseth wrote:
>> On 18/07/17 22:55, Farkas Levente wrote:
>>> On 07/18/2017 10:03 PM, David Sommerseth wrote:
On 18/07/17 17:50, Farkas Levente wrote:
> On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
>> This w
On 07/20/2017 02:09 AM, David Sommerseth wrote:
> On 18/07/17 22:55, Farkas Levente wrote:
>> On 07/18/2017 10:03 PM, David Sommerseth wrote:
>>> On 18/07/17 17:50, Farkas Levente wrote:
On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
> This will result in the following:
> * OpenVPN 2.4
David Sommerseth wrote:
> Also considering that we're just in the very early planning phase of
> F-27 and F-26 have just been released. So F-27 is at least 6 months
> ahead of us.
That's what one would reasonably assume, but sadly, they decided to cut the
schedule of F27 down to 3-4 months to co
On 18/07/17 22:55, Farkas Levente wrote:
> On 07/18/2017 10:03 PM, David Sommerseth wrote:
>> On 18/07/17 17:50, Farkas Levente wrote:
>>> On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
This will result in the following:
* OpenVPN 2.4 based clients will automatically upgrade to AES-256-GC
On 07/18/2017 10:03 PM, David Sommerseth wrote:
> On 18/07/17 17:50, Farkas Levente wrote:
>> On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
>>> This will result in the following:
>>> * OpenVPN 2.4 based clients will automatically upgrade to AES-256-GCM,
>>> regardless if they have --cipher in thei
On 18/07/17 17:50, Farkas Levente wrote:
> On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
>> This will result in the following:
>> * OpenVPN 2.4 based clients will automatically upgrade to AES-256-GCM,
>> regardless if they have --cipher in their configuration file or not.
>> For OpenVPN v2.4 confi
On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
> This will result in the following:
> * OpenVPN 2.4 based clients will automatically upgrade to AES-256-GCM,
> regardless if they have --cipher in their configuration file or not.
> For OpenVPN v2.4 configurations not wanting this cipher upgrade, the
= Proposed Self Contained Change: New default cipher in OpenVPN =
https://fedoraproject.org/wiki/Changes/New_default_cipher_in_OpenVPN
Change owner(s):
* David Sommerseth
Since the discovery of the SWEET32 flaw [1], ciphers using
cipher-blocks smaller than 128-bits are considered vulnerable and
10 matches
Mail list logo