On 10/30/2014 07:36 PM, Martin Basti wrote:
On 30/10/14 19:18, Michael Lasevich wrote:
Makes sense. What is the solution here?
I have the latest 389-ds installed but still getting
allowWeakCipher error - how to I get around that?
-M
Sorry I don't know, I CCied Ludwig, he is DS guru.
I
Thank you!!! That was exactly it.
* Removed the nsEncryptionConfig entry from 99user.ldif
* Re-run the ipa-ldap-update --upgrade
* Then ipa-dns-install and things are looking much better - both
servers are now back up and running.
What is the lesson here (besides have good backups)?
Should we
On 24/10/14 05:17, Michael Lasevich wrote:
While upgrading from 4.0.1. to 4.1 on fedora 20 got following on one
of the two boxes:
Upgrade failed with attribute allowWeakCipher not allowed
IPA upgrade failed.
Unexpected error
DuplicateEntry: This entry already exists
Named errors are caused
Makes sense. What is the solution here?
I have the latest 389-ds installed but still getting allowWeakCipher
error - how to I get around that?
-M
On 10/30/14, 11:12 AM, Martin Basti wrote:
On 24/10/14 05:17, Michael Lasevich wrote:
While upgrading from 4.0.1. to 4.1 on fedora 20 got
On 30/10/14 19:18, Michael Lasevich wrote:
Makes sense. What is the solution here?
I have the latest 389-ds installed but still getting allowWeakCipher
error - how to I get around that?
-M
Sorry I don't know, I CCied Ludwig, he is DS guru.
Martin^2
On 10/30/14, 11:12 AM, Martin Basti
On 10/24/2014 05:17 AM, Michael Lasevich wrote:
While upgrading from 4.0.1. to 4.1 on fedora 20 got following on one of the two
boxes:
Upgrade failed with attribute allowWeakCipher not allowed
IPA upgrade failed.
Unexpected error
DuplicateEntry: This entry already exists
It seems the ipa no
