Ik heb mijn hoofd zitten breken ove

Ik heb mijn hoofd zitten breken over het feit waarom je reeds in het verleden geen CA_..._2048 key hebt.
Ik vermoed dat dit komt omdat er ooit na een Core Server patch, in de install instructies stond, om nog een bijkomende script
te runnen, dewelke deze _2048 key aanmaakte.
Als dit nooit gedaan werd, dan is het logisch date r nooit een _2048 key was.
Ok, ik heb hier zitten opzoeken hoe we manueel deze key kunnen aanmaken.
In bijlage vindt u de OA12 User Guide. Blader even naar pagina 64 "Configuring the Security Component Variables" section.
Dit beschrijft alle stappen die u moet volgen om naar een nieuwe key length te gaan.
Ik stel voor dat je de stappen beschreven op pagina 64 en 65 doet, end an even bekijkt of de "ovcert -list" er wel goed
uitziet.
Daarna kan je poberen de ovcs service opnieuw op te starten met "ovc -start".
Werkt dit ?
Als alles dan goed gaat, kan je eens op een node een "ovcert -updatetrusted" doen om te zien of ook de _2048 key wordt geupdate
(ovcert -list).
Alvast bedankt voor uw feedback.

結果 (英語) 1:

I have my mind breaking over the fact why you already had in the past no CA_ ... _2048 key.I suspect that this is because there ever after a Core Server patch, in the install instructions, to another scriptto running, which created this _2048 key.If this was never done, then the logical date r _2048 key was never a.OK, I have sitting here looking up how we can create this key manually.Please find attached the OA12 User Guide. Browse to page 64 "Configuring the Security Component variables" section.This describes all the steps you need to follow to get to a new key length.I suggest you do the steps described on page 64 and 65, end an even or the "ovcert-list" there be finelooks like.Then you can restart the ovcs poberen service with "ovc-start".Does this work?If everything goes well, you can agree on a node a "ovcert-updatetrusted" to see if the _2048 key will be updated(ovcert-list).Thank you for your feedback.

結果 (英語) 2:

I've been breaking my head about why you do not already have CA _..._ 2048 Key in the past.
I suspect this is because there once stood after a Core Server patch in the install instructions, not an additional script
to run, which create them _2048 key.
If this was not done, then it is logical date r was never a _2048 key.
Okay, I'm sitting here looking how we manually can create this key.
Enclosed you will find the OA12 User Guide. Flip to page 64 "Configuring the Security Component Variables" section.
This describes all the steps you must follow to move to a new key length.
I suggest that you outline the steps occurs on page 64 and 65, end an equally viewing or "ovcert -list" there good
looks.
then you can poberen restart the service with OVCs' OVC-start. "
does this work?
If everything goes well, you can agree on a node a" ovcert -updatetrusted "do to find out whether the _2048 key is updated
(ovcert -list).
Thank you for your feedback.

結果 (英語) 3:

i got my head break about why you have in the past no ca _... _ 2048 key.i suspect that this is because ever after a core server patch in the install instructions, to another scriptto run it, this _ 2048 key created.if this was never done, it is logical date was never a _ 2048 key.ok, i have to sit here and see how we can make this key manually.in appendix, you will find the oa12 user guide. turn to page 64 "configuring the security component variables" section.this describes the steps that you must follow to go to a new key length.i suggest you take the steps described on page 64 and 65, or look at the end of "ovcert list" welllook.then you can ovcs trying to re start the service with "ovc start".this work?if everything goes well, you can look at a node a "ovcert - updatetrusted" to see if the _ 2048 key is updated(ovcert list).thank you for your feedback.