search for: sbit

I'm not happy with ssh being setuid root. I know that the long-term goal is to have a seperate host-key-management process, but that is a ways off. Until then, I'd like to propose the following: - Allow ssh to read alternate key files. This would allow the ssh client to use keyfiles different from the ones sshd uses. I know that this can be done now by changing the ones sshd uses,

Hi, According to ChangeLog someone "(bal)" removed -{enable/disable}-suid-ssh from configure (dating from 2002/06/07). Don't know the reason, probably this has something to do with PrivilegeSeparation. Consequence is: Users with UID != 0 are no longer able to allocate privileged ports, sshd answers "Rhosts Authentication disabled, originating port will not be

...eServer 2.3 no vulnerable packages included and OpenLinux eBuilder OpenLinux eDesktop 2.4 kISDN 3. Solution Workaround: If you do not need kISDN, deinstall it by issuing as root: rpm -e kisdn If you need kISDN on a multiuser workstation: Disable the suid-root sbit by doing as root: chmod u-s /opt/kde/bin/kisdn You can still use kisdn by issuing in a terminal window: $ su -p Password: <your root password> # kisdn & Also check your system for any other KDE application you have installed from third party sources an...

...they are added to the smbpasswd file without a password and requested to change it asap. But unfortunately, it seems to be impossible to change a null password to something else :-( The last couple of releases have changed some things in this area. I went through the - smbpasswd no longer needs sbit (i.e. goes through smbd) - XXXXXX....:XXXXX... -> "NO PASSWORDXXX....:XXXX....." in passwd file - null passwords = yes in smb.conf changes, but to no avail. I'm seeing this problem both at work under Solaris 2.5.1 and at home under FreeBSD 2.2.6, both built using the std makef...

Hi, I run Samba 2.0.5a on Linux 2.2.12 (Slackware). My clients get an error regularly (Windows95) "Network path not found" and then they lose their connection completely. The server logs the following: [1999/09/07 17:30:01, 1] smbd/service.c:make_connection(521) sbit12 (137.56.40.139) connect to service sbitdata as user sbit (uid=1000, gid=100) (pid 134) [1999/09/07 17:33:10, 0] lib/util_sock.c:read_socket_data(507) read_socket_data: recv failure for 4. Error = Connection reset by peer [1999/09/07 17:33:10, 1] smbd/service.c:close_cnum(557) sbit12 (0.0.0.0)...

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New majordomo packages available Advisory ID: RHSA-2000:005-05 Issue date: 2000-01-20 Updated on: 2000-05-31 Product: Red Hat Powertools Keywords: majordomo Cross references: N/A

...run Samba 2.0.5a on Linux 2.2.12 (Slackware). > >My clients get an error regularly (Windows95) "Network path not found" >and then they lose their connection completely. > >The server logs the following: >[1999/09/07 17:30:01, 1] smbd/service.c:make_connection(521) > sbit12 (137.56.40.139) connect to service sbitdata as user sbit (uid=1000, gid=100) (pid 134) >[1999/09/07 17:33:10, 0] lib/util_sock.c:read_socket_data(507) > read_socket_data: recv failure for 4. Error = Connection reset by peer >[1999/09/07 17:33:10, 1] smbd/service.c:close_cnum(557) >...