>(as for "possibly not the FIPS provider", that's exactly right. That
one *will* be a loadable module and nothing else, and will only be
validated as such... meaning that noone can stop you from hacking
around and have it linked in statically, but that would make it
invalid
On 15/02/2019 12:23, Matt Caswell wrote:
On 15/02/2019 03:55, Jakob Bohm via openssl-users wrote:
These comments are on the version of the specification released on
Monday 2019-02-11 at https://www.openssl.org/docs/OpenSSL300Design.html
General notes on this release:
- The release was not
On Fri, 2019-02-15 at 11:23 +, Matt Caswell wrote:
>
> On 15/02/2019 03:55, Jakob Bohm via openssl-users wrote:
> > yout - but this is useful input.
>
> >
> > FIPS-specific issues:
> >
> > - The checksum of the FIPS DLL should be compiled into the FIPS-
> > capable OpenSSL library, since
On 15/02/2019 03:55, Jakob Bohm via openssl-users wrote:
> These comments are on the version of the specification released on
> Monday 2019-02-11 at https://www.openssl.org/docs/OpenSSL300Design.html
>
> General notes on this release:
>
> - The release was not announced on the openssl-users
Note: these are my personal answers. I'm sure (and hope) that other
in our team will chip in (and possibly disagree with me)
On Fri, 15 Feb 2019 04:55:38 +0100,
Jakob Bohm wrote:
>
> These comments are on the version of the specification released on
> Monday 2019-02-11 at
These comments are on the version of the specification released on
Monday 2019-02-11 at https://www.openssl.org/docs/OpenSSL300Design.html
General notes on this release:
- The release was not announced on the openssl-users and
openssl-announce mailing lists. A related blog post was
announced
