[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] Libgcrypt warning: MD5 used - FIPS mode inactivated
- Subject: [ale] Libgcrypt warning: MD5 used - FIPS mode inactivated
- From: adrya.stembridge at gmail.com (Adrya Stembridge)
- Date: Thu, 13 Aug 2015 14:22:33 -0400
- In-reply-to: <CAEo=5PyM_1b5MGpxu4F1Df+L+Y_tzqMMjbjf8=Wx3N9ekLZ6dw@mail.gmail.com>
- References: <CAFCFmQmXEL72LgMO3tfEk-r48vWMxP25fzmKK3T_eQeeXsLb6Q@mail.gmail.com> <CAEo=5PyM_1b5MGpxu4F1Df+L+Y_tzqMMjbjf8=Wx3N9ekLZ6dw@mail.gmail.com>
On Thu, Aug 13, 2015 at 12:25 PM, Jim Kinney <jim.kinney at gmail.com> wrote:
> The rhel instructions look like the system keys will default to weaker
> non-FIPS unless fips=1 is a kernel param at at system installation. So *converting
> an existing system won't work*. So weak keys with libgcrypt will call for
> fallback to non-fips but then fails since it's a denied operations mode.
I went through the same steps of activating FIPS on my dev instance, and do
not have the libgcrypt error, and am able to tsql to my SQL Server machine.
Confirmed FIPS is active and working using the steps written in my
initial post to the list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20150813/2a3cbe4c/attachment.html>