Hi,
I'm afraid the man page on the conf file is not particularly clear. I'm
looking at mitigating CVE-2016-2183 (SWEET32), and am not sure how to disable
the DES and 3DES suites in the conf file.
Can someone give me a hand?
---
Scott Neugroschl | XYPRO Technology Corporation
4100 Guardian St
On 23 September 2016 at 17:13, Scott Neugroschl wrote:
> Hi,
>
>
>
> I’m afraid the man page on the conf file is not particularly clear. I’m
> looking at mitigating CVE-2016-2183 (SWEET32), and am not sure how to
> disable the DES and 3DES suites in the conf file.
>
> Can someone give me a hand
Mr. Neugroschl's quest for a simple solution does bring up -- in my
user-oriented opinion -- a very good follow-on question: "/Why cannot a config
file be utilized by openssl to simply give access based on an allow/deny
mechanism that would give users system-wide control in a single place?"./
> Mr. Neugroschl's quest for a simple solution does bring up -- in my
> user-oriented opinion -- a very good follow-on question: "Why cannot a config
> file be utilized by openssl to simply give access based on an allow/deny
> mechanism that would give users system-wide control in a single plac
> On Sep 24, 2016, at 7:16 PM, Salz, Rich wrote:
>
>>
>> Mr. Neugroschl's quest for a simple solution does bring up -- in my
>> user-oriented opinion -- a very good follow-on question: "Why cannot a
>> config file be utilized by openssl to simply give access based on an
>> allow/deny mechani
