cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
moin, for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me. comments? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done.

Re: cons.saver not suid root

2005-06-08 Thread Jakub Jelinek
On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: moin, for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me. comments? cons.saver should not be setuid root, it should be

Re: cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 04:40:14PM +0200, Jakub Jelinek wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me.

Re: cons.saver not suid root

2005-06-08 Thread Leonard den Ottolander
Hi Jakub, Oswald, On Wed, 2005-06-08 at 16:40, Jakub Jelinek wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. cons.saver should not be setuid root, it

Re: cons.saver not suid root

2005-06-08 Thread Leonard den Ottolander
and the accompanying user than suid-ing cons.saver root. That's just ugly. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 05:13:00PM +0200, Leonard den Ottolander wrote: On Wed, 2005-06-08 at 17:03, Oswald Buddenhagen wrote: and punish the upstream users, including ourselves? interesting. This issue can be easily fixed with package builds. suppose i prefer configure make stow ...

Re: cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 05:23:42PM +0200, Egmont Koblinger wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: --- Makefile.am.orig2005-06-08 16:30:58.0 +0200 +++ Makefile.am 2005-06-08 16:29:13.0 +0200 @@ -75,6 +75,8 @@ if USE_EDIT

Re: cons.saver not suid root

2005-06-08 Thread Koblinger Egmont
On Wed, Jun 08, 2005 at 04:49:11PM +0200, Oswald Buddenhagen wrote: we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. How about not creating a user or group, but observing the installed system? IMHO if all the vcsa devices are owned

Re: cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 05:42:07PM +0200, Koblinger Egmont wrote: On Wed, Jun 08, 2005 at 04:49:11PM +0200, Oswald Buddenhagen wrote: we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. How about not creating a user or group, but

Re: cons.saver not suid root

2005-06-08 Thread Oswald Buddenhagen
On Wed, Jun 08, 2005 at 05:43:05PM +0200, Leonard den Ottolander wrote: On Wed, 2005-06-08 at 17:23, Oswald Buddenhagen wrote: suppose i prefer configure make stow ... Patch is your friend. Or just chown and chmod afterwards. you needn't to educate _me_. now that i identified the problem

Re: cons.saver not suid root

2005-06-08 Thread Koblinger Egmont
On Wed, Jun 08, 2005 at 06:06:03PM +0200, Tomasz Koczko wrote: BTW: in case Linux now I don' see cons.saver usage. $ strace -o out mc; grep cons.saver out with few times ctrl-o during strace show nothing (?). Q: is in case Linux cons.saver is still neccessary ? Yes. In case mc's

Re: cons.saver not suid root

2005-06-08 Thread Leonard den Ottolander
Hi Jakub, On Wed, 2005-06-08 at 16:40, Jakub Jelinek wrote: cons.saver should not be setuid root, it should be setuid to whatever user owns /dev/vcsa* devices. Ideally there is a vcsa user that just owns these devices and cons.saver. Could you maybe go into the details if and if how a