Bug 23099 - univention-certificate should also create a public key file
univention-certificate should also create a public key file
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: SSL
UCS 4.4
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Julius Hinrichs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-27 11:07 CEST by Jan Christoph Ebersbach
Modified: 2020-07-06 08:45 CEST (History)
7 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:
requate: Patch_Available+


Attachments
Patch to always create an additional public key file when calling "univention-certificate new -name ..." (526 bytes, patch)
2016-10-04 12:34 CEST, Julius Hinrichs
Details | Diff
Minor improvement (510 bytes, patch)
2016-10-04 12:39 CEST, Julius Hinrichs
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Christoph Ebersbach univentionstaff 2011-07-27 11:07:28 CEST
Bei der Erzeugung eines neuen Schlüssels wird momentan keine Public-Key-Datei erzeugt. Dies macht es dem Administrator unnötig schwer, wenn er zur Authentifizierung Public-Keys z.B. an Diensten hinterlegen möchte.

U.a. benötigt der Zarafa-Server zur Authentifizierung von Systemen/Diensten den jeweiligen Public-Key.

Mit folgenden Befehlen kann der Public-Key für bestehendes Zertifikat erzeugt werden:
cd /etc/univention/ssl/HOST/
openssl rsa -inform PEM -outform PEM -in private.key -pubout -out public.key

univention-certificate sollte so angepasst werden, dass der Public-Key bei der Erzeugung mit generiert wird.
Comment 1 Jan Christoph Ebersbach univentionstaff 2012-01-18 10:52:31 CET
Das Problem besteht auch mit UCS 3.0 noch. Die Public-Key-Datei ist unter anderem für die Anbindung des Black Berry Servers an Zarafa notwendig.
Comment 2 Jan Christoph Ebersbach univentionstaff 2012-01-18 10:53:04 CET
Ähnlich gelagerter Bug: Bug #21198
Comment 3 Stephan Hendl 2013-02-22 07:38:00 CET
Wie im Bug beschrieben wären das doch nur ein paar wenige zusätzliche Zeilen Code in /usr/share/univention-ssl/make-certificates.sh. Wann wird es verfügbar sein? Auch wir benötigen es für Zarafa.
Comment 4 Julius Hinrichs univentionstaff 2016-10-04 12:34:04 CEST
Created attachment 8062 [details]
Patch to always create an additional public key file when calling "univention-certificate new -name ..."
Comment 5 Julius Hinrichs univentionstaff 2016-10-04 12:39:25 CEST
Created attachment 8063 [details]
Minor improvement
Comment 6 Stefan Gohmann univentionstaff 2017-06-16 20:37:32 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 7 Stephan Hendl 2017-06-19 09:48:34 CEST
Please change the version to either 4.1 or 4.2 since the feature still required.
Comment 8 Ingo Steuwer univentionstaff 2020-07-03 20:54:13 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
Comment 9 Stephan Hendl 2020-07-06 08:42:26 CEST
As this is "not a big deal" and a patch is already available would you mind reopening the bug and provide this enhancement?
Comment 10 Christian Völker univentionstaff 2020-07-06 08:45:51 CEST
Still needed and low hanging fruit.