similar to: LPRng security

On Tue, Nov 09, 1999 at 11:39:39AM +0100, Mariusz Marcinkiewicz wrote: > After reading lcamtuf's posts I decided write this one. Few months ago one > of my friends - digit - found bug in linux nfsd daemon. I made example > sploit about IV 1999. Now in distributions is new nfsd and nowhere was > information about security weaknes of old version! Well, one gets used to people

I've got egg on my face... There is a nasty security hole in the User-space NFS servers. If you are running an NFS server, please upgrade as soon as possible to the latest release, nfs-server-2.2beta35.tar.gz, which can be found at ftp://linux.mathematik.tu-darmstadt.de/pub/linux/people/okir All previous releases are vulnerable. <Taking off his okir hat and putting on his caldera

-----BEGIN PGP SIGNED MESSAGE----- ld.so Vulnerability A buffer overflow problem was reported on bugtraq affecting the ELF and a.out program loaders on Linux. This problem can possibly be exploited by malicious users to obtain root access. On Linux, programs linked against shared libraries execute some code contained in /lib/ld.so (for a.out binaries) or /lib/ld-linux.so (for ELF

Hi there, some of the recent holes discussed on this list, and David Holland''s suggestion for a utmp manager daemon got me thinking. I ended up coding a sample program that demonstrates how a `resource manager'' can be used to allow applications access to certain resources while not giving them any privileges. The sample program is a primitve modem manager that hands out open

Summary: you can exploit a single-byte buffer overrun to gain root privs. When, half a day after releasing version 2.2beta37 of the Linux nfs server, I received a message from Larry Doolittle telling me that it was still vulnerable to the root exploit posted to bugtraq, I was ready to quit hacking and start as a carpenter... Tempting as that was, I didn''t, and started looking for the

Hi all, Have got Winbind working again successfully on another box, but this time the printer won't work, it worked fine last time. The printer installs fine, and it lets me print to it, but nothing comes out on the printer, no sign of anything being sent to it. I think it's a permissions problem or something...but I've not much clue when it comes to printing on *nix how it actually

I know this question has been answered here a while back, but I have not been able to find the mailing with the posts on it. -----==========----- I have a redhat server that I am using as a file/print server for student use. I am using samba to help the users with Windows. The problem I have is that when using printing a user can submit a print job, and it prints fine, but cannot see the

Hello, Excuse me for my English. I use an impression (not yet;) and file server samba 2.2.5 on a red hat 7.2. I try to print starting from a station under Windows 2000 but I obtain the error "the handle is invalid". I installed the drivers for my impimante on the W2000 station but I would like to also know if the drivers of the printer are necessary for the W2000 workstation AND

-----BEGIN PGP SIGNED MESSAGE----- $Id: lpr-vulnerability-0.6-linux,v 1.2 1996/11/25 22:39:20 alex Exp $ Linux Security FAQ Update lpr Vulnerability Mon Nov 25 16:56:59 EST 1996 Copyright (C) 1995,1996 Alexander O. Yuriev (alex@bach.cis.temple.edu) CIS Laboratories

I have a redhat 9 server I would like to migrate (install Centos on a new machine, and move the necessary files) to Centos 5. On the RH9 machine, I use LPRng for printing. This was mainly choosen because it makes it easy to control access to the printers using /etc/lpd.perms, something I never figured out how to do in cups. All printer queues are raw printers, the printer driver in Windows takes

> From lprng@astart2.astart.com Fri Aug 11 14:51:22 2000 > Date: Fri, 11 Aug 2000 13:38:04 -0700 (PDT) > From: John Johnson <ioann_j@yahoo.com> > Subject: LPRng: Printing to Samba 2.0.7 from Windows 2000 > To: lprng@lprng.com, freebsd-questions@FreeBSD.ORG, samba@samba.org > > Hi, > > I've recently installed LPRng 3.6.22, ifhp 3.3.19, and > Samba 2.0.7 on my

First of all, thanks to everyone who has helped me out so far resolving my samba problems! The latest has to do with LPRng and directory permissions. LPRng requires 0600 permissions on the spool directory, owner daemon group daemon. Whenever a user tries to print through SAMBA, they do not have write access to the spool directory, as teh job comes in user/group of the person who printed. Any

How do I use LPRNG and Samba to setup printing to a network printer? Here is my smb.conf...... # Global parameters [global] workgroup = DOMAIN server string = rh1 encrypt passwords = Yes max log size = 0 time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 domain admin group = root add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u logon script

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: New util-linux packages available to fix /bin/login pam problem Advisory ID: RHSA-2001:132-03 Issue date: 2001-10-11 Updated on: 2001-10-16 Product: Red Hat Linux Keywords: login pam pam_limits Cross references:

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: New util-linux packages available to fix /bin/login pam problem Advisory ID: RHSA-2001:132-04 Issue date: 2001-10-11 Updated on: 2001-10-16 Product: Red Hat Linux Keywords: login pam pam_limits Cross references:

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New Samba packages for Red Hat Linux 4.2, 5.2, 6.0 Advisory ID: RHSA-1999:022-01 Issue date: 1999-07-22 Updated on: Keywords: samba smbd nmbd security Cross references: --------------------------------------------------------------------- 1. Topic: Samba 2.0.5a has

Hello all - I've got an unusual problem that keeps popping up since samba 2.0, all the way through 2.0.5a. I'm running LPRng on my Linux box with Samba. Both startup fine. Fileserving with samba is fine, but whenever I try to print from any of my clients (Win 9x, NT, doesn't matter) the print job just sits in the SAMBA spool directory. Looking through the LPD logs LPR never gets

Hello all...I was having incredible difficulty in setting up my HP Color LaserJet 4500 to be shared on a Caldera 2.3 Linux server with access to it from Windows 2000 machines. I've been working about a week now (sadly enough) and I think I've made some progress mainly from information in newsgroups and online documentation. Here's what I have so far: I can print from the linux

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New samba packages for Red Hat Linux 4.2, 5.2, 6.0 Advisory ID: RHSA-1999:022-02 Issue date: 1999-07-22 Updated on: 1999-07-23 Keywords: samba smbd nmbd security Cross references: --------------------------------------------------------------------- Revision History:

<It seems that the print command is trying to find the printer at location 'localhost'. Since this is a network printer it is not at localhost is it?> Yeah, the error messages made no sense to me either! Well, like I said earlier: < The IP address of this printer is 10.1.1.192. I call this printer nero, and have it listed in my /etc/hosts file> Here is a copy of part of my