Re: Should FIPS_mode() and FIPS_mode_set() be updated, deprecated, or completely removed..

2020-03-04 Thread Tomas Mraz
On Wed, 2020-03-04 at 10:18 +, Matt Caswell wrote: > > On 04/03/2020 08:15, Tomas Mraz wrote: > > The current implementation in the PR - unconditionally returning > > error > > - is completely useless. It would make some (not much) sense if we > > aimed for ABI compatibility with 3.0 however

Re: Should FIPS_mode() and FIPS_mode_set() be updated, deprecated, or completely removed..

2020-03-04 Thread Matt Caswell
On 04/03/2020 08:15, Tomas Mraz wrote: > The current implementation in the PR - unconditionally returning error > - is completely useless. It would make some (not much) sense if we > aimed for ABI compatibility with 3.0 however that is definitely not the > case so the only reasonable thing is

Re: Should FIPS_mode() and FIPS_mode_set() be updated, deprecated, or completely removed..

2020-03-04 Thread Tomas Mraz
On Wed, 2020-03-04 at 13:47 +1000, SHANE LONTIS wrote: > FIPS_mode() and FIPS_mode_set() are functions that were used by the > old FOM. > > In OpenSSL_111 they were stripped down to do almost nothing > i.e:- > > int FIPS_mode(void) > { > /* This version of the library does not

Should FIPS_mode() and FIPS_mode_set() be updated, deprecated, or completely removed..

2020-03-03 Thread SHANE LONTIS
FIPS_mode() and FIPS_mode_set() are functions that were used by the old FOM. In OpenSSL_111 they were stripped down to do almost nothing i.e:- int FIPS_mode(void) { /* This version of the library does not support FIPS mode. */ return 0; } int FIPS_mode_set(int