summaryrefslogtreecommitdiffstats
path: root/inc
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2010-03-04 16:19:31 +0100
committerDenys Vlasenko <vda.linux@googlemail.com>2010-03-04 16:19:31 +0100
commitafb30fe1502e9c45b722da3b5c09e292d589aa7f (patch)
tree8f0429ccc50987a34e73899c0a724ff6e0205c93 /inc
parent892b7fde75cafca50a18dcb8620ddc22b2e74688 (diff)
downloadabrt-afb30fe1502e9c45b722da3b5c09e292d589aa7f.tar.gz
abrt-afb30fe1502e9c45b722da3b5c09e292d589aa7f.tar.xz
abrt-afb30fe1502e9c45b722da3b5c09e292d589aa7f.zip
*: UID:UUID -> crash_id conversion
This fixes at least three instances where we did not check whether user is even allowed to report or delete a crash. Also fixes a few cases when root might inadvertently act on (e.g. delete) mote than one crash. Renamed FILENAME_UID to CD_UID - makes more sense this way. Added COL_INFORMALL and CD_INFORMALL. Nuked UID == -1 hacks. Renamed getReport() to start_job on Python side. Dropped a few unused parameters from server -> client dbus signals. Fixed CLI's way of reverencing crashes (see updated help text). Run-tested (GUI and CLI). Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> Acked-by: Nikola Pajkovsky <npajkovs@redhat.com>
Diffstat (limited to 'inc')
-rw-r--r--inc/CrashTypes.h10
1 files changed, 8 insertions, 2 deletions
diff --git a/inc/CrashTypes.h b/inc/CrashTypes.h
index af106cff..77a2ff27 100644
--- a/inc/CrashTypes.h
+++ b/inc/CrashTypes.h
@@ -25,7 +25,6 @@
#define FILENAME_ARCHITECTURE "architecture"
#define FILENAME_KERNEL "kernel"
#define FILENAME_TIME "time"
-#define FILENAME_UID "uid"
#define FILENAME_PACKAGE "package"
#define FILENAME_COMPONENT "component"
#define FILENAME_DESCRIPTION "description"
@@ -42,8 +41,15 @@
#define FILENAME_MEMORYMAP "memorymap"
#define FILENAME_KERNELOOPS "kerneloops"
-#define CD_DUPHASH "DUPHASH"
+// Apart from CD_UID, which is also stored as a file in dump directory,
+// these items only exist in db. (CD_UID is also a file because
+// dump directory is created before its DB entry, and DB has to learn
+// CD_UID from _somewhere_ in order to be able to store it in DB record,
+// right?)
+#define CD_UID "uid" /* lowercase: compat with older versions */
#define CD_UUID "UUID"
+#define CD_INFORMALL "InformAll"
+#define CD_DUPHASH "DUPHASH"
#define CD_DUMPDIR "DumpDir"
#define CD_COUNT "Count"
#define CD_REPORTED "Reported"