Bug 24493 - Installer muss Profil-Dateien auf korrekte UTF-8 Kodierung prüfen
Installer muss Profil-Dateien auf korrekte UTF-8 Kodierung prüfen
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCS Installer
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.x
Assigned To: Installer maintainers
:
Depends on: 18006 23750
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-09 18:53 CET by Janek Walkenhorst
Modified: 2017-08-08 07:08 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Walkenhorst univentionstaff 2011-11-09 18:53:36 CET
Der Installer muss die Profil-Dateien auf korrekte UTF-8 Kodierung prüfen, damit keine nicht-UTF-8-Werte in die UCR geschrieben werden können.

+++ This bug was initially created as a clone of Bug #23750 +++

Der Installer muss die UCR-Variablen mit UTF-8 kodierten Werten füllen,
unabhängig von der locale der Konsole/Tastatur, um den UCR-Strict-Mode zu
erfüllen (Bug #18006).
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:40:43 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 2 Stefan Gohmann univentionstaff 2017-08-08 07:08:43 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.