On 4/29/20 5:07 PM, Mark Reynolds wrote:
We've been talking about this for quite some time...
A majority of all the old legacy perl and shell scripts have now been
ported to the new CLI tools. Starting sometime in Fedora 33 we will
stop shipping the legacy tools sub-package as part of 389
We've been talking about this for quite some time...
A majority of all the old legacy perl and shell scripts have now been
ported to the new CLI tools. Starting sometime in Fedora 33 we will
stop shipping the legacy tools sub-package as part of 389 Directory
Server. If you have any tools or
This is a known problem. We moved the default minimum to TLS 1.2 (from
1.0), but it's not working correctly and it will not allow you to set
1.0 at all. We will fix it shortly...
On 4/29/20 10:25 AM, Alberto Viana wrote:
Hi Guys,
My packages:
Hi Guys,
My packages:
389-ds-base1.4.2.8-20200414gitfae920fc8.el8.x86_64
openssl-1.1.1c-2.el8.x86_64
I'm trying to set tls-protocol-min to TLS 1.0 but it's not working, I used
dsconf and ldapmodify like this:
dn: cn=encryption,cn=config
changetype: modify
replace: sslVersionMin
sslVersionMin:
William,
Here's:
Frame9:
https://gist.github.com/albertocrj/87bf4a010bf2f7e1f97ef3ee72ee44df
Frame7:
https://gist.github.com/albertocrj/840f15e5df10cad0e2977cd030abdba4
Frame6:
https://gist.github.com/albertocrj/befb7144b86bc4af86b9a2e0be0293a1
Thank you
Alberto Viana
On Wed, Apr 22, 2020
On 4/28/2020 10:39 PM, William Brown wrote:
I suspect we don't support ECDSA yet, and that's what's causing the
issue. See:
https://pagure.io/389-ds-base/issue/50010
We can talk about it as a project and try to prioritise it, because I think it
would be important to have. Sorry aboutthat :(
