Re: [OpenXPKI-users] Without AES256
Hi 1: Is it possible when I create a TLS certificate via WebGui that it is automatically saved locally in a folder? 2: Which variable would I have to change so that the password becomes statistical for certificate_signing_request_v2? Martin Bartosch via OpenXPKI-users schrieb am Di. 5. März 2024 um 14:48: > Hi, > > > Is there also a possibility when I create certificates that the > certificates are stored directly on the server on which openxpki is running? > > Your question is not specific enough to let us understand what you > actually want to achieve, and for this reason the answer is a qualified > "yes". > > Cheers > > Martin > > > > ___ > OpenXPKI-users mailing list > OpenXPKI-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openxpki-users > ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
Re: [OpenXPKI-users] Without AES256
Hi, > Is there also a possibility when I create certificates that the certificates > are stored directly on the server on which openxpki is running? Your question is not specific enough to let us understand what you actually want to achieve, and for this reason the answer is a qualified "yes". Cheers Martin ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
Re: [OpenXPKI-users] Without AES256
Ahh okay I have found thanks! Is there also a possibility when I create certificates that the certificates are stored directly on the server on which openxpki is running? Martin Bartosch via OpenXPKI-users schrieb am Di. 5. März 2024 um 14:30: > Hi, > > > Could you tell me in which workflow I cloud define the fixed password? > > Well, that's the workflow you are using for requesting the certificate, > most likely certificate_signing_request_v2 > > In this workflow you will find an activity which is conveniently called > generate_key... > > Cheers > > Martin > > > ___ > OpenXPKI-users mailing list > OpenXPKI-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openxpki-users > ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
Re: [OpenXPKI-users] Without AES256
Hi, > Could you tell me in which workflow I cloud define the fixed password? Well, that's the workflow you are using for requesting the certificate, most likely certificate_signing_request_v2 In this workflow you will find an activity which is conveniently called generate_key... Cheers Martin ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
Re: [OpenXPKI-users] Without AES256
Oke Thanks for the info Could you tell me in which workflow I cloud define the fixed password? Oliver Welter schrieb am Mo. 4. März 2024 um 16:29: > Hi Ali, > > I guess you refer to a CSR workflow with server side key generation? No > this is not possible - the generate key method does not allow a key > generation without a password for security reasons. You need to change the > workflow and handle the password (either storing it or using a fixed value) > and use it later to do an unencrypted export. > > Oliver > On 04.03.24 08:09, Ali Danakiran wrote: > > Hey, > > Would it be possible to edit the default.yaml to create a key without an > "aes256" passphrase? > > > ___ > OpenXPKI-users mailing > listOpenXPKI-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/openxpki-users > > -- > Protect your environment - close windows and adopt a penguin! > > ___ > OpenXPKI-users mailing list > OpenXPKI-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openxpki-users > ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
Re: [OpenXPKI-users] Without AES256
Hi Ali, I guess you refer to a CSR workflow with server side key generation? No this is not possible - the generate key method does not allow a key generation without a password for security reasons. You need to change the workflow and handle the password (either storing it or using a fixed value) and use it later to do an unencrypted export. Oliver On 04.03.24 08:09, Ali Danakiran wrote: Hey, Would it be possible to edit the default.yaml to create a key without an "aes256" passphrase? ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users -- Protect your environment - close windows and adopt a penguin! ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
[OpenXPKI-users] Without AES256
Hey, Would it be possible to edit the default.yaml to create a key without an "aes256" passphrase? ___ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
