Hi,
On 08-12-17 13:34, Jim Carroll wrote:
> I'm curious about the openvpn-devel process related to patch acceptance. Does
> the fact that the conversation has ended mean the patch is scheduled to be
> added -- or does it instead mean there is no interest and the patch is being
> denied?
It mea
I'm curious about the openvpn-devel process related to patch acceptance. Does
the fact that the conversation has ended mean the patch is scheduled to be
added -- or does it instead mean there is no interest and the patch is being
denied?
Thanks
Jim
begin 666 smime.p7s
M,( &"2J&2(;W#0$'`J" ,(
> So I don't think the version is as strict as you say. But it might be
> other
> distributions have gone through the compliance certification on a
> different
> version.
This is true. Red Hat has gone through the compliance certification on 1.0.2k
and their security policy is public
https://cs
On 03/12/17 16:10, Jim Carroll wrote:
[...snip...]
> You asked:
>
> >> +* OpenSSL 1.0.2m
> >> +* openssl-fips-2.0.2
>
> > I think the points above are expected to be ">="?
> > Or are these versions strictly required?
>
> These versions are strictly required. While
Hi Antonio,
I've resubmitted our patch(s) for FIPS support. While re-reading your message,
I see you asked a question I neglected to answer. In options.h, we declared
an integer option 'fips_mode', and you asked:
"why not bool?"
The reason is extendibility for planned changes in OpenS
Hi Antonio,
Thanks for reviewing. If you donât mind, I'm going to answer your
comments and questions a bit out of order.
First, you suggested a series of coding-style changes and the removal of
extra whitespace. I have no comment about these. I'll make all the changes
you described and resubmi
Hi,
On 25/11/17 04:23, j...@carroll.com wrote:
> From: JimC
>
> Modified the autoconf, automake and code to support building OpenVPN with
> OpenSSL FIPS Object Module v2.0 validated encryption.
>
> * Adds: --enable-fips-mode switch to configure.ac
> * Adds: --enable-fips-mode co
Thanks. I wanted to make sure it got through.
> -Original Message-
> From: Gert Doering [mailto:g...@greenie.muc.de]
> Sent: Monday, November 27, 2017 12:47 PM
> To: Jim Carroll
> Cc: openvpn-devel@lists.sourceforge.net
> Subject: Re: [Openvpn-devel] [PATCH] Adde
Hi,
On Mon, Nov 27, 2017 at 12:15:27PM -0500, Jim Carroll wrote:
> Just checking in to confirm our revised path made it though this time. And
> wanted to see if there is any feedback?
Patch made it just fine (thanks for re-sending) and patchworks picked
it up...
https://patchwork.openvpn.net/pat
;
> Cc: 'openvpn-devel@lists.sourceforge.net'
> Subject: RE: [Openvpn-devel] [PATCH] Added OpenSSL FIPS 2.0 support to
> OpenVPN
begin 666 smime.p7s
M,( &"2J&2(;W#0$'`J" ,( "`0$Q"S )!@4K#@,"&@4`,( &"2J&2(;W#0$'
M`0``H((.$3"
From: JimC
Modified the autoconf, automake and code to support building OpenVPN with
OpenSSL FIPS Object Module v2.0 validated encryption.
* Adds: --enable-fips-mode switch to configure.ac
* Adds: --enable-fips-mode command line switch to openvpn
---
INSTALL
Sigh...Outlook is always such a mess. Sorry, I'll resend.
Jim
begin 666 smime.p7s
M,( &"2J&2(;W#0$'`J" ,( "`0$Q"S )!@4K#@,"&@4`,( &"2J&2(;W#0$'
M`0``H((.$3""!#8P@@,>H ,"`0("`0$P#08)*H9(AO<-`0$%!0`P;S$+, D&
M`U4$!A,"4T4Q%# 2!@-5! H3"T%D9%1R=7-T($%",28P) 8#500+$QU!9&14
M'1E%PTP,# U,S Q,#0X,SA:%PT
Hi,
On Fri, Nov 24, 2017 at 12:09:13PM -0500, Jim Carroll wrote:
> Modified the autoconf, automake and code to support building OpenVPN with
>
> OpenSSL FIPS Object Module v2.0 validated encryption.
>
>
>
> * Adds: --enable-fips-mode switch to configure.ac
>
> * Adds: --enabl
Modified the autoconf, automake and code to support building OpenVPN with
OpenSSL FIPS Object Module v2.0 validated encryption.
* Adds: --enable-fips-mode switch to configure.ac
* Adds: --enable-fips-mode command line switch to openvpn
---
INSTALL | 72
+
14 matches
Mail list logo
