Hello, why there is no k3bsetup in k3b package??? I know that it is in packman... But suse's k3b shown cdrecord warning after start... m.
Hello,
why there is no k3bsetup in k3b package??? I know that it is in packman... But suse's k3b shown cdrecord warning after start...
m. Setup seems to jump up and run the first time you launch k3b, so
On Monday 11 December 2006 08:24, Michal Hlavac wrote: perhaps it was no longer needed? -- _____________________________________ John Andersen
Dňa Po 11. December 2006 21:23 John Andersen napísal:
On Monday 11 December 2006 08:24, Michal Hlavac wrote:
Hello,
why there is no k3bsetup in k3b package??? I know that it is in packman... But suse's k3b shown cdrecord warning after start...
m.
Setup seems to jump up and run the first time you launch k3b, so perhaps it was no longer needed?
I don't think so... You need to run k3bsetup as root. And what about access rights and burn group setup?? m.
On Monday 11 December 2006 13:12, Michal Hlavac wrote:
Dňa Po 11. December 2006 21:23 John Andersen napísal:
On Monday 11 December 2006 08:24, Michal Hlavac wrote:
Hello,
why there is no k3bsetup in k3b package??? I know that it is in packman... But suse's k3b shown cdrecord warning after start...
m.
Setup seems to jump up and run the first time you launch k3b, so perhaps it was no longer needed?
I don't think so... You need to run k3bsetup as root. And what about access rights and burn group setup??
Well, all I can say is when I fired up k3b for the first time on SUSE 10.1 it fired up k3b-setup and it in turn asked for root password. I don't know where it came from but it exist in /opt/kde3/bin/k3bsetup and on the Settings menu of K3b there is a k3bsetup option. -- _____________________________________ John Andersen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-11 at 15:44 -0900, John Andersen wrote:
Well, all I can say is when I fired up k3b for the first time on SUSE 10.1 it fired up k3b-setup and it in turn asked for root password.
I don't know where it came from but it exist in /opt/kde3/bin/k3bsetup and on the Settings menu of K3b there is a k3bsetup option.
What??? There is no /opt/kde3/bin/k3bsetup in SuSE 10.1. If you have it, you got it from another source than Suse. Could you do a: rpm -q -f /opt/kde3/bin/k3bsetup please? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFff2htTMYHG2NR9URAnqcAJ419fxTfQwSI1uamGr8qs4ZLJ4vsQCdHfxm 7XMpqBzaWUO6O2OM6VQGVIA= =XeI/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 11 December 2006 15:53, Carlos E. R. wrote:
The Monday 2006-12-11 at 15:44 -0900, John Andersen wrote:
Well, all I can say is when I fired up k3b for the first time on SUSE 10.1 it fired up k3b-setup and it in turn asked for root password.
I don't know where it came from but it exist in /opt/kde3/bin/k3bsetup and on the Settings menu of K3b there is a k3bsetup option.
What???
There is no /opt/kde3/bin/k3bsetup in SuSE 10.1. If you have it, you got it from another source than Suse. Could you do a:
rpm -q -f /opt/kde3/bin/k3bsetup
please?
-- Cheers, Carlos E. R.
jsa@pen:~> rpm -q -f /opt/kde3/bin/k3bsetup k3b-0.12.17-100.pm.0 jsa@pen:~> -- _____________________________________ John Andersen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-11 at 15:56 -0900, John Andersen wrote:
jsa@pen:~> rpm -q -f /opt/kde3/bin/k3bsetup k3b-0.12.17-100.pm.0 jsa@pen:~>
Ah. That's not the "official" suse rpm, it is another one. The current one for 10.1 is "k3b-0.12.14-12". That's why you have k3bsetup and we have not. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFfhFutTMYHG2NR9URAvcDAJ946iaakKiSB6TuI2Bg1u0KlV+6YACeKLbg gyZbS3m4JwFJzlbmREzaYsw= =yKMH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-12-12 at 03:18 +0100, I wrote:
The Monday 2006-12-11 at 15:56 -0900, John Andersen wrote:
jsa@pen:~> rpm -q -f /opt/kde3/bin/k3bsetup k3b-0.12.17-100.pm.0 jsa@pen:~>
Ah. That's not the "official" suse rpm, it is another one. The current one for 10.1 is "k3b-0.12.14-12". That's why you have k3bsetup and we have not.
I forgot. You can confirm who made that rpm using "rpm -q -i k3b" (vendor and Packager section). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFfhTQtTMYHG2NR9URAsyNAJ9Gzk77XPHhgM6ToFjB782JFKhsjwCeKdEv cpvsXv7rf5f6z8v1TU03bvc= =eznJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Tuesday 2006-12-12 at 03:18 +0100, I wrote:
The Monday 2006-12-11 at 15:56 -0900, John Andersen wrote:
jsa@pen:~> rpm -q -f /opt/kde3/bin/k3bsetup k3b-0.12.17-100.pm.0 jsa@pen:~> Ah. That's not the "official" suse rpm, it is another one. The current one for 10.1 is "k3b-0.12.14-12". That's why you have k3bsetup and we have not.
I forgot. You can confirm who made that rpm using "rpm -q -i k3b" (vendor and Packager section).
All the .pm. stuff is from packman. Regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-12-12 at 09:03 +0100, Jos van Kan wrote:
All the .pm. stuff is from packman.
I thought it might, but I wasn't sure. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFfpH9tTMYHG2NR9URAtCwAJ9Wm2cpgYIisLleC8rYyNter6xVCACgjOPD C+q1k/Kc4JOf7abSl6ma5io= =cDLx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michal Hlavac wrote:
Dňa Po 11. December 2006 21:23 John Andersen napísal:
On Monday 11 December 2006 08:24, Michal Hlavac wrote:
Hello,
why there is no k3bsetup in k3b package??? I know that it is in packman... But suse's k3b shown cdrecord warning after start...
m.
Setup seems to jump up and run the first time you launch k3b, so perhaps it was no longer needed?
I don't think so... You need to run k3bsetup as root. And what about access rights and burn group setup??
There is no burn group in SUSE, at least not in 10.0. Access rights are given during console login by setting file ACLs. This is done by resmgr, see /usr/share/doc/packages/resmgr/. Do a getfacl /dev/sr0 (or whatever your CD-Writer-Device is) to see the ACLs. The only remaining question is if there shouldn't be write access to the corresponding generic SCSI device as well, or if that isn't needed. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
There is no burn group in SUSE, at least not in 10.0. Access rights are given during console login by setting file ACLs. This is done by resmgr, see /usr/share/doc/packages/resmgr/.
Do a getfacl /dev/sr0 (or whatever your CD-Writer-Device is) to see the ACLs.
The only remaining question is if there shouldn't be write access to the corresponding generic SCSI device as well, or if that isn't needed.
hello Joachim, when I start k3b (suse 10.2) it says this: cdrecord will be run without root privileges It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr. Solution: Use K3bSetup to solve this problem. m.
Michal Hlavac wrote:
There is no burn group in SUSE, at least not in 10.0. Access rights are given during console login by setting file ACLs. This is done by resmgr, see /usr/share/doc/packages/resmgr/.
Do a getfacl /dev/sr0 (or whatever your CD-Writer-Device is) to see the ACLs.
The only remaining question is if there shouldn't be write access to the corresponding generic SCSI device as well, or if that isn't needed.
when I start k3b (suse 10.2) it says this: cdrecord will be run without root privileges It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr. Solution: Use K3bSetup to solve this problem.
Interesting information. k3bsetup sets cdrecord setuid-root, doesn't it? How do you prevent that it is set back to 755, according to /etc/permissions, when SuSEconfig is run the next time? (This is done by the module /sbin/conf.d/SuSEconfig.permissions and controlled by /etc/sysconfig/security.) If cdrecord needs to run with root privileges, it should be installed so from the start and not changed by k3bsetup, IMHO. The latter won't survive for long in a standard SUSE setup, the setuid bit will disappear after the next sysadmin activity that causes SuSEconfig to run. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joachim Schrod wrote:
Michal Hlavac wrote:
when I start k3b (suse 10.2) it says this: cdrecord will be run without root privileges It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr. Solution: Use K3bSetup to solve this problem.
But I know it does work as is, even with the message.
k3bsetup sets cdrecord setuid-root, doesn't it? How do you prevent that it is set back to 755, according to /etc/permissions, when SuSEconfig is run the next time? (This is done by the module /sbin/conf.d/SuSEconfig.permissions and controlled by /etc/sysconfig/security.)
If cdrecord needs to run with root privileges, it should be installed so from the start and not changed by k3bsetup, IMHO. The latter won't survive for long in a standard SUSE setup, the setuid bit will disappear after the next sysadmin activity that causes SuSEconfig to run. You are correct, but not only that, but AFAIR, after kernel 2.6.8, it must NOT be SUID root, because of a security change made in the kernel at that time. I know I used to set those permissions the SuSE way, in /etc/permissions.local, but found after 2.6.8 it would not work as root. I'm not sure of the present state of all that, I've lost track, but I know I have NOT needed to change the permissions of cdrecord for a long time, and as long as resmgr is working, it DOES work as is, no messing needed.
-- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) a écrit :
root. I'm not sure of the present state of all that, I've lost track, but I know I have NOT needed to change the permissions of cdrecord for a long time, and as long as resmgr is working, it DOES work as is, no messing needed.
and don't forget apparmor may go in the middle as it monitors what an application can do and can't... jdd -- http://www.dodin.net http://dodin.org/mediawiki/index.php/GPS_Lowrance_GO -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dňa Ut 12. December 2006 15:10 jdd napísal:
Joe Morris (NTM) a écrit :
root. I'm not sure of the present state of all that, I've lost track, but I know I have NOT needed to change the permissions of cdrecord for a long time, and as long as resmgr is working, it DOES work as is, no messing needed.
and don't forget apparmor may go in the middle as it monitors what an application can do and can't...
ok, but is there some solution for this issue?? thanks, m.
Joe Morris (NTM) wrote:
You are correct, but not only that, but AFAIR, after kernel 2.6.8, it must NOT be SUID root, because of a security change made in the kernel at that time. I know I used to set those permissions the SuSE way, in /etc/permissions.local, but found after 2.6.8 it would not work as root. I'm not sure of the present state of all that, I've lost track, but I know I have NOT needed to change the permissions of cdrecord for a long time, and as long as resmgr is working, it DOES work as is, no messing needed.
Hi Joe. Does that mean, that ALT F2 and SUID K3B is not allowed anymore ?. A merry Christmas and a Happy New Year 2007 for You and Your family. -- Med venlig hilsen / Best regards Erik Jakobsen eja@urbakken.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erik Jakobsen wrote:
Does that mean, that ALT F2 and SUID K3B is not allowed anymore ?.
Assuming you mean ALT-F2 to run a command, and the command is kdesu k3b to run it as root, I don't know. I haven't tried that in years. It has worked as a user now for a long time.
A merry Christmas and a Happy New Year 2007 for You and Your family.
Thanks, and to yours. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
Erik Jakobsen wrote:
Does that mean, that ALT F2 and SUID K3B is not allowed anymore ?.
Assuming you mean ALT-F2 to run a command, and the command is kdesu k3b to run it as root, I don't know. I haven't tried that in years. It has worked as a user now for a long time.
A merry Christmas and a Happy New Year 2007 for You and Your family.
Thanks, and to yours.
I mean that, but will try it without the kdesu. Thanks for the good wishes. -- Med venlig hilsen / Best regards Erik Jakobsen eja@urbakken.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Carlos E. R. -
Erik Jakobsen -
jdd -
Joachim Schrod -
Joe Morris (NTM) -
John Andersen -
Jos van Kan -
Michal Hlavac