Due to the newly added command filtering, you now need to run cdrecord as
root. Since cdrecord will drop root privileges before accessing the drive,
setuid root won't help.
This means you will have to run cdrecord *and* k3b as root!
IMHO it is more secure to simply disable filtering, and run the software as non-root.
This patch restores the behaviour of previous kernels, security issues included:
[^] # Re: Problème cdrecord.prodvd
Posté par Serge Rossi (site web personnel) . En réponse à la dépêche Linux 2.6.8, suivi de près par Linux 2.6.8.1. Évalué à 4.
Donc tu aura surement vu la solution (pas encore essayé moi même) :
http://lkml.org/lkml/2004/8/16/104(...)
Due to the newly added command filtering, you now need to run cdrecord as
root. Since cdrecord will drop root privileges before accessing the drive,
setuid root won't help.
This means you will have to run cdrecord *and* k3b as root!
IMHO it is more secure to simply disable filtering, and run the software as non-root.
This patch restores the behaviour of previous kernels, security issues included:
--- linux-2.6.8/drivers/block/scsi_ioctl.c~ 2004年08月16日 14:16:57.000000000 +0200
+++ linux-2.6.8/drivers/block/scsi_ioctl.c 2004年08月16日 14:36:22.562908552 +0200
@@ -196 +196 @@
- if (verify_command(file, cmd))
+/* if (verify_command(file, cmd))
@@ -198 +198 @@
-
+*/