Bug 21761 - Fehlerhafte Verwendung von printf in /etc/lsb-base-logging.sh
Fehlerhafte Verwendung von printf in /etc/lsb-base-logging.sh
Status: CLOSED INVALID
Product: UCS
Classification: Unclassified
Component: Bootsplash
UCS 2.4
Other Linux
: P5 normal (vote)
: UCS 3.1
Assigned To: Philipp Hahn
Stefan Gohmann
: interim-1
Depends on:
Blocks: 21501
  Show dependency treegraph
 
Reported: 2011-03-09 09:29 CET by Philipp Hahn
Modified: 2012-12-12 21:10 CET (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:
hahn: Patch_Available+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2011-03-09 09:29:01 CET
Wenn es ein C-Programm wäre, würde ich jetzt laut "Format String Vulnerability" schreien, aber so produziert es nur eine hässliche Fehlermeldung bei der Verwendung von "log_action_cont_message 100%", da hier "..." angehängt wird, was zu einem ungültigen "%." wird.

--- /etc/lsb-base-logging.sh.bak        2011-03-09 09:21:18.000000000 +0100
+++ /etc/lsb-base-logging.sh    2011-03-09 08:33:01.000000000 +0100
@@ -78,7 +78,7 @@ log_daemon_msg () {
         # and we won't be able to reliably know where the colourful
         # asterisk ought to go.
 
-        printf " * $*       "
+        printf "%s" " * $*       "
         # Enough trailing spaces for ` [fail]' to fit in; if the message
         # is too long it wraps here rather than later, which is what we
         # want.

Da usplash Upstream-tot ist, wird das dort wohl auch niemanden mehr interessieren... Zeit für Splashy, Plymouth, Xsplash, oder was auch immer gerade in Mode ist.
Comment 1 Philipp Hahn univentionstaff 2012-08-04 01:22:40 CEST
In UCS-3.1 nicht mehr relevant.
Comment 2 Stefan Gohmann univentionstaff 2012-09-11 15:58:44 CEST
Ja, das ist nicht mehr vorhanden.
Comment 3 Stefan Gohmann univentionstaff 2012-12-12 21:10:51 CET
UCS 3.1-0 has been released: 
 http://forum.univention.de/viewtopic.php?f=54&t=2125

If this error occurs again, please use "Clone This Bug".