DSL Ideas and Suggestions :: EUREKA!!!!



I spoke too soon.  No idea why, but those two libs are still not being found in DSL.
I found the cause of the trouble, but not a solution yet.  This is from the ld.so manpage:
The shared libraries needed by the program are searched for in various places:
...
   Using the environment variable LD_LIBRARY_PATH. Except if the executable is a setuid/setgid binary, in which case it is ignored.

the screen binary is setuid.
Ah yes, I have read about that a few times ..  
I think it was mentioned in the link I posted..
Hmm, wonder why setgid/uid ?

So.. what happens if you remove the sticky gid/uid?
Is that needed for running in a gnome or kde environment?

Usually NOT needed, and many times considered a securty risk.

If you don't have any luck, I'll get screen tomorrow,
and browse thru it with you..

What happens if you simply run the app as sudo?
Sticky bits be damned...

73
ke4nt
Found a little more info:
Quote
   The screen program needs root permissions from the setuid-root bit for
   two reasons: multi-attached sessions are only possible with root
   privileges, and writing terminal allocation information to /var/run/utmp
   (the who(1) and finger(1) commands). If the screen command is not running
   with special privileges, all functionality except these two features will
   continue to work, but the local root compromise will not be possible.

These features don't seem to be too important for a DSL system, so I've removed the UID....still have to test it out.  It still requires libelf, which i find odd.  The screen package I have installed in suse is a single minor version difference, and it does not require libelf.  Also since ELF seems to be a very large part of Linux systems I'm curious why none of my other extensions want it.

Fordi: sorry for the hijack.  When I started typing it seemed to fit into this thread perfectly...but evolved into a different issue.
well....good and bad news...

After looking through Makefile and config.h I got it to compile without the extra libs, and now it seems to work.

Unfortunately it seems to work only in an X terminal, which makes the whole thing rather pointless.  I don't know if it's because of the way DSL was built, or if it's something I can fix myself, but I tried both with and without setuid and I get the message "can't open /dev/tty1".  This occurs with my extension as well as with a precompiled version including the extra libs.  Comparing /dev/tty* in DSL with /dev/tty* in suse I can't see any difference in the files themselves, so I'm at a wall with no visible doors or windows...not understanding much about how terminals work I think I'll have to put this project aside until I learn a bit more.

I won't be posting about this in this thread anymore....again, Fordi, sorry about taking your thread in the wrong direction.
Next Page...
original here.